Age | Commit message (Collapse) | Author | Files | Lines |
|
This would have bad effects :)
|
|
* playbin3 does not support {current,n}-{audio,video,text}
properties, and they were replaced by GstStreams API.
So, GstStreams API and select-stream event should be used
for track change in case of playbin3.
see also https://bugzilla.gnome.org/show_bug.cgi?id=769079
* By using commend line option "--use-playbin3", gst-play will
use playbin3 regardless of "USE_PLAYBIN" env variable.
https://bugzilla.gnome.org/show_bug.cgi?id=775469
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=783722
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=783722
|
|
Print a gst-launch-1.0 line that could get to this device,
useful as we don't have other ways to see what it does exactly.
This may not work if the create element has configurations other than
properties.
https://bugzilla.gnome.org/show_bug.cgi?id=781152
|
|
Use new message notify API and print caps and taglists in a nicer
to read way, just like gst-launch-1.0 does nowadays, without
escaping everything three times.
|
|
This ensure that XInitThreads is called and so gl contexts are properly
initialized.
https://bugzilla.gnome.org/show_bug.cgi?id=776403
|
|
|
|
https://github.com/mesonbuild/meson
With contributions from:
Tim-Philipp Müller <tim@centricular.com>
Jussi Pakkanen <jpakkane@gmail.com> (original port)
Highlights of the features provided are:
* Faster builds on Linux (~40-50% faster)
* The ability to build with MSVC on Windows
* Generate Visual Studio project files
* Generate XCode project files
* Much faster builds on Windows (on-par with Linux)
* Seriously fast configure and building on embedded
... and many more. For more details see:
http://blog.nirbheek.in/2016/05/gstreamer-and-meson-new-hope.html
http://blog.nirbheek.in/2016/07/building-and-developing-gstreamer-using.html
Building with Meson should work on both Linux and Windows, but may
need a few more tweaks on other operating systems.
|
|
When cycling through tracks, add 'disable' to the set
of states.
|
|
gst_message_parse_device_{added,removed} is actually returning a new ref
on the device.
https://bugzilla.gnome.org/show_bug.cgi?id=768776
|
|
So we can use gst-play to track memory leaks.
https://bugzilla.gnome.org/show_bug.cgi?id=765216
|
|
|
|
< and > are composed with shift + something else on many keyboards
layouts, so don't work well when injecting them via windowing systems
which will send them as shift key press and separate other key, and
we the don't combine that to < or > properly. n/b are easier.
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=751901
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=751901
|
|
g_error is meant to be used for programmer errors (causes an abort),
not for expected runtime errors.
|
|
Some values are easier to read and make sense of in hex.
https://bugzilla.gnome.org//show_bug.cgi?id=759780
|
|
|
|
The removed GList link needs to be freed too, and
the G_OPTION_REMAINING arguments need to be freed.
|
|
The "fall through" comment was wrong. Removed.
https://bugzilla.gnome.org/show_bug.cgi?id=755440
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=755440
|
|
When g_option_context_parse fails, context and error variables are not getting free'd
which results in memory leaks. Free'ing the same.
And replacing g_error_free with g_clear_error, which checks if the error being passed
is not NULL and sets the variable to NULL on free'ing.
https://bugzilla.gnome.org/show_bug.cgi?id=753852
|
|
In case discover_uri returns NULL info, passing the info to discoverer APIs
result in critical assertion errors. Hence instead of passing NULL info along,
print the error and return.
https://bugzilla.gnome.org/show_bug.cgi?id=753701
|
|
When running gst-play against a directory name, and suffix the path with a
directory separator (e.g. tab completion), gst-play was printing two directory
separators in a row. g_build_filename fixes this, and additionally allows for
both '/' and '\' as separators on Windows.
|
|
When g_option_context_parse or gst_discoverer_new fails, then there will
be memory leaks for ctx and err variables. Free'ing the same.
https://bugzilla.gnome.org/show_bug.cgi?id=753701
|
|
In case of very short files we might end up seeking in
steps of a fraction of a second, which is silly and gives
the impression that seeking doesn't actually work. Make
minimum seek step a second instead.
|
|
CID 1311942
|
|
|
|
In gst-play, for GST_MESSAGE_ELEMENT bus message,
event is being allocated through
gst_navigation_message_parse_event, but not freed.
https://bugzilla.gnome.org/show_bug.cgi?id=752040
|
|
For positive seeking segment.stop value will be -1,
when we change rate to -1, then the stop value will be udpated
with the current position. And then again if we change rate to 1,
the segment.stop value does not get updated and remains as position
where we last changed rate to -1. Hence playback stops at that point.
In case of positive rates, call gst_element_new_seek with correct values
https://bugzilla.gnome.org/show_bug.cgi?id=751213
|
|
|
|
Printing 64 whitespaces to erase the "Paused" message (after \r) would make
it wrap to the next line on shorter terminals. Instead we only print the
amount of spaces needed. Also mark the "Paused" string for translation
while we're at it.
|
|
|
|
When adding a directory to the playlist, the order would be whatever
g_dir_read_name returned. Sorting these using natural sort order.
https://bugzilla.gnome.org/show_bug.cgi?id=750585
|
|
The second assignment of sret is never used. We can remove the first assignment
and use the value directly instead.
|
|
Instead of resetting rate to 1.0
|
|
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=749740
|
|
And change --interactive option to --no-interactive.
|
|
And don't feed multi-character key descriptors to the
event handler, it won't be what it expects.
|
|
Allows the user to control playback with the window in focus
https://bugzilla.gnome.org/show_bug.cgi?id=747245
|
|
This is not needed any longer.
|
|
‘return’ with no value, in function returning non-void
|
|
Make "t" activate trick modes and cycle through the various
modes.
|
|
Prevent gst-indent from messing up indentation, it
really doesn't like the G_GNUC_PRINTF thing here.
|
|
|
|
Use smaller steps for lower rates to allow more
fine-grained control. Handle jump across 0 properly
from both sides (just flip direction where we would
have gone down to 0 instead). Don't artificially
limit rates to +/- 10x. Print new rate.
https://bugzilla.gnome.org/show_bug.cgi?id=745174
|
|
https://bugzilla.gnome.org/show_bug.cgi?id=745174
|
|
It is fun to have this feature, also it is useful for testing decoders.
https://bugzilla.gnome.org/show_bug.cgi?id=745174
|