info: avoid redefinition of symbols when debugging is off
The refactoring of gst_debug_add_log_function() now causes build failure when
debug-logging is turned off. Just move it to the conditional part of the header.
The refactoring of gst_debug_add_log_function() now causes build failure when
debug-logging is turned off. Just move it to the conditional part of the header.
tests: fix compiler warning in new miniobject test
gst/gstminiobject.c: In function ‘test_dup_null_mini_object’:
gst/gstminiobject.c:459:7: warning: assignment from incompatible pointer type
gst/gstminiobject.c: In function ‘test_dup_null_mini_object’:
gst/gstminiobject.c:459:7: warning: assignment from incompatible pointer type
miniobject: Fix dup_mini_object function to handle NULL gvalues
g_value_dup_object handles gvalues that contain NULL pointers,
gst_value_dup_mini_object should do the same.
https://bugzilla.gnome.org/show_bug.cgi?id=649195
g_value_dup_object handles gvalues that contain NULL pointers,
gst_value_dup_mini_object should do the same.
https://bugzilla.gnome.org/show_bug.cgi?id=649195
docs: it its %TRUE (constant)
As spotted by Tim.
As spotted by Tim.
docs: fix copy'n'paste doc header mistake
docs: add two trivial doc blobs
docs: add missing parameter docs
docs: add docs for GstDPPacketizer
docs: improve the syntax for the capsintersectmode docs
docs: fixup broken xref
docs: add new api to -section.txt
docs: fix gtk-doc syntax
docs: don't duplicate info that we take from element-details
docs: remove non existing symbol
docs: we don't need to document private members in opaque structs
0.10.32.4 pre-release
pluginfeature: include plugin.h in header where we use a GstPlugin pointer
Should fix issue with gstreamermm build where <gst/gstindex.h> is included
directly instead of gst/gst.h.
Should fix issue with gstreamermm build where <gst/gstindex.h> is included
directly instead of gst/gst.h.
0.10.32.3 pre-release
Revert lockfree GstBus for the release
Drop in old GstBus code for the release to play it safe, since
regressions that are apparently hard to track down and reproduce
have been reported (on windows/OSX mostly) against the lockfree
version, and more time is needed to fix them.
This reverts commit 03391a897001d35d1d290f27dd12e98a8b729fb4.
This reverts commit 43cdbc17e6f944cdf02aeed78d1d5f6bde5190c9.
This reverts commit 80eb160e0f62350271f061daa5f289d9d4277cf4.
This reverts commit c41b0ade28790ffdb0e484b41cd7929c4e145dec.
This reverts commit 874d60e5899dd5b89854679d1a4ad016a58ba4e0.
This reverts commit 79370d4b1781af9c9a65f2d1e3498124d8c4c413.
This reverts commit 2cb3e5235196eb71fb25e0a4a4b8749d6d0a8453.
This reverts commit bd1c40011434c1efaa696dc98ef855ef9cce9b28.
This reverts commit 4bf8f1524f6e3374b3f3bc57322337723d06b928.
This reverts commit 14d7db1b527b05f029819057aef5c123ac7e013d.
https://bugzilla.gnome.org/show_bug.cgi?id=647493
Drop in old GstBus code for the release to play it safe, since
regressions that are apparently hard to track down and reproduce
have been reported (on windows/OSX mostly) against the lockfree
version, and more time is needed to fix them.
This reverts commit 03391a897001d35d1d290f27dd12e98a8b729fb4.
This reverts commit 43cdbc17e6f944cdf02aeed78d1d5f6bde5190c9.
This reverts commit 80eb160e0f62350271f061daa5f289d9d4277cf4.
This reverts commit c41b0ade28790ffdb0e484b41cd7929c4e145dec.
This reverts commit 874d60e5899dd5b89854679d1a4ad016a58ba4e0.
This reverts commit 79370d4b1781af9c9a65f2d1e3498124d8c4c413.
This reverts commit 2cb3e5235196eb71fb25e0a4a4b8749d6d0a8453.
This reverts commit bd1c40011434c1efaa696dc98ef855ef9cce9b28.
This reverts commit 4bf8f1524f6e3374b3f3bc57322337723d06b928.
This reverts commit 14d7db1b527b05f029819057aef5c123ac7e013d.
https://bugzilla.gnome.org/show_bug.cgi?id=647493
minor inline documentation fix
tests: clean up properly in the bin test_link_structure_change unit test
Don't forget to set the pipeline back to NULL state, which makes
valgrind happy again.
Don't forget to set the pipeline back to NULL state, which makes
valgrind happy again.
registry: when removing a cached-but-no-longer-existing plugin, only remove features that belong to it
When a plugin file no longer exists, e.g. because it's been removed or
renamed, don't remove all features in the registry based on the *name*
of the plugin they belong to, but only remove those who actually belong
to that particular plugin (object/pointer).
This fixes issues of plugin features disappearing when a plugin .so file
is renamed.
https://bugzilla.gnome.org/show_bug.cgi?id=604094
When a plugin file no longer exists, e.g. because it's been removed or
renamed, don't remove all features in the registry based on the *name*
of the plugin they belong to, but only remove those who actually belong
to that particular plugin (object/pointer).
This fixes issues of plugin features disappearing when a plugin .so file
is renamed.
https://bugzilla.gnome.org/show_bug.cgi?id=604094
pluginfeature: store pointer to plugin in addition to the plugin name
So we can reliably remove plugin features for a specific plugin later.
https://bugzilla.gnome.org/show_bug.cgi?id=604094
So we can reliably remove plugin features for a specific plugin later.
https://bugzilla.gnome.org/show_bug.cgi?id=604094
registry: use TRACE log level to log files that don't look like plugins
Cuts down the noise in uninstalled setups.
Cuts down the noise in uninstalled setups.
basetransform: fix negotiation regression
Fixup patch for 83597767b169dd6c39a07b6144a650c1f098825a
Use a separate variable for knowing if a pad alloc has been made
instead of checking for the flow return that might not be the
result of the pad alloc
https://bugzilla.gnome.org/show_bug.cgi?id=648220
Fixup patch for 83597767b169dd6c39a07b6144a650c1f098825a
Use a separate variable for knowing if a pad alloc has been made
instead of checking for the flow return that might not be the
result of the pad alloc
https://bugzilla.gnome.org/show_bug.cgi?id=648220
tests: add simple pipeline-in-pipeline unit test
https://bugzilla.gnome.org/show_bug.cgi?id=648297
https://bugzilla.gnome.org/show_bug.cgi?id=648297
bus: also allow popping a message without timeout if no poll available
... which happens in particular flushing a bus, possibly as part
of a state change, e.g. when having a pipeline in a pipeline
and then changing state back to NULL. The interior pipeline
will/might then flush the bus, which is a child bus from the
parent which does not have a poll anymore these days.
https://bugzilla.gnome.org/show_bug.cgi?id=648297
... which happens in particular flushing a bus, possibly as part
of a state change, e.g. when having a pipeline in a pipeline
and then changing state back to NULL. The interior pipeline
will/might then flush the bus, which is a child bus from the
parent which does not have a poll anymore these days.
https://bugzilla.gnome.org/show_bug.cgi?id=648297
pad: unlock before freeing the cache to avoid deadlock
https://bugzilla.gnome.org/show_bug.cgi?id=648199
https://bugzilla.gnome.org/show_bug.cgi?id=648199
basetransform: don't unref trans until the function is done using it
trans->priv->force_alloc = FALSE would crash if the ref held is the last
https://bugzilla.gnome.org/show_bug.cgi?id=648215
trans->priv->force_alloc = FALSE would crash if the ref held is the last
https://bugzilla.gnome.org/show_bug.cgi?id=648215
docs: add note/warning to gst_index_get_writer_id() docs about the OBJECT_LOCK
https://bugzilla.gnome.org/show_bug.cgi?id=646811
https://bugzilla.gnome.org/show_bug.cgi?id=646811
baseparse: don't deadlock when setting external index
Protect index with its own lock. gst_index_get_writer_id() may take
the object lock internally (the default resolver, GST_INDEX_RESOLVER_PATH,
will anyway), so if we're using that to protect the index as well,
we'll deadlock.
https://bugzilla.gnome.org/show_bug.cgi?id=646811
Protect index with its own lock. gst_index_get_writer_id() may take
the object lock internally (the default resolver, GST_INDEX_RESOLVER_PATH,
will anyway), so if we're using that to protect the index as well,
we'll deadlock.
https://bugzilla.gnome.org/show_bug.cgi?id=646811
baseparse: make fmtlist constant
query: const-ify formats arguments to gst_query_set_formatsv()
docs: remove reference to baseparse API that didn't make it
0.10.32.2 pre-release
po: update translations
gst-launch: remove newline from translatable string
gst: gobject-introspection scanner doesn't need to scan or update plugin info
gst: make sure gobject-introspection scanner calls gst_init()
https://bugzilla.gnome.org/show_bug.cgi?id=647922
https://bugzilla.gnome.org/show_bug.cgi?id=647922
libs: gobject-introspection scanner doesn't need to scan or update plugin info
Make sure the scanner doesn't load or introspect or check any plugins,
(especially not outside the build directory).
Make sure the scanner doesn't load or introspect or check any plugins,
(especially not outside the build directory).
libs: make sure gobject-introspection scanner calls gst_init()
https://bugzilla.gnome.org/show_bug.cgi?id=647922
https://bugzilla.gnome.org/show_bug.cgi?id=647922
win32: add new baseparse API to libgstbase.def
win32: Add exports for the GstParseContext and GstBufferListIterator types
pluginloader: only run gst-plugin-scanner with /usr/bin/arch wrapper on OS X >= 10.5
Based on patch by: Daniel Macks <dmacks@netspace.org>
Earlier versions of OSX don't support proper multiarch and
trying to use /usr/bin/arch -foo with those versions would
just break things.
https://bugzilla.gnome.org/show_bug.cgi?id=615357
Based on patch by: Daniel Macks <dmacks@netspace.org>
Earlier versions of OSX don't support proper multiarch and
trying to use /usr/bin/arch -foo with those versions would
just break things.
https://bugzilla.gnome.org/show_bug.cgi?id=615357
baseparse: expose gst_base_parse_frame_free() for completeness
API: gst_base_parse_frame_free()
API: gst_base_parse_frame_free()
baseparse: init frames on the stack with gst_base_parse_frame_init()
Frames must now be inited this way, can't just zero them
out and use them.
Frames must now be inited this way, can't just zero them
out and use them.
baseparse: more debug logging, minor clean-up
Trace frames, split out code to queue a frame for later.
Trace frames, split out code to queue a frame for later.
baseparse: change gst_base_parse_frame_init() to not take a GstBaseParse argument
baseparse: make GstBaseParseFrame handling more bindings-friendly
Change semantics of gst_base_parse_push_frame() and make it take
ownership of the whole frame, not just the frame contents. This
is more in line with how gst_pad_push() etc. work. Just transfering
the content, but not the container of something that's not really
known to be a container is hard to annotate properly and probably
won't work. We mark frames allocated on the stack now with a private
flag in gst_base_parse_frame_init(), so gst_base_parse_frame_free()
only frees the contents in that case but not the frame struct itself.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
API: gst_base_parse_frame_new()
Change semantics of gst_base_parse_push_frame() and make it take
ownership of the whole frame, not just the frame contents. This
is more in line with how gst_pad_push() etc. work. Just transfering
the content, but not the container of something that's not really
known to be a container is hard to annotate properly and probably
won't work. We mark frames allocated on the stack now with a private
flag in gst_base_parse_frame_init(), so gst_base_parse_frame_free()
only frees the contents in that case but not the frame struct itself.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
API: gst_base_parse_frame_new()
baseparse: register boxed type for GstBaseFrameParse
To make this usable for bindings.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
To make this usable for bindings.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
queue2: Add missing ) to the ring-buffer-max-size property description
baseparse: Remove unused but set variable
GCC 4.6.0 spits warnings about these.
GCC 4.6.0 spits warnings about these.
bufferlist: Add boxed type for GstBufferListIterator for gobject-introspection
parse: Add boxed type for GstParseContext for gobject-introspection
gst: Add some more gobject-introspection annotations
multiqueue: Don't leak the sinkpad name
multiqueue: Don't leak pads in the named pads unit test
utils: Fix caps leaks in gst_element_factory_can_accept_{any,all}_caps_in_direction()
parser: Allow element names to begin with digits
tests: Add test for greatest common divisor
elements: Fix pad callbacks so they handle when parent goes away
1) We need to lock and get a strong ref to the parent, if still there.
2) If it has gone away, we need to handle that gracefully.
This is necessary in order to safely modify a running pipeline. Has been
observed when a streaming thread is doing a buffer_alloc() while an
application thread sends an event on a pad further downstream, and from
within a pad probe (holding STREAM_LOCK) carries out the pipeline plumbing
while the streaming thread has its buffer_alloc() in progress.
1) We need to lock and get a strong ref to the parent, if still there.
2) If it has gone away, we need to handle that gracefully.
This is necessary in order to safely modify a running pipeline. Has been
observed when a streaming thread is doing a buffer_alloc() while an
application thread sends an event on a pad further downstream, and from
within a pad probe (holding STREAM_LOCK) carries out the pipeline plumbing
while the streaming thread has its buffer_alloc() in progress.
base: Fix pad callbacks so they handle when parent goes away
1) We need to lock and get a strong ref to the parent, if still there.
2) If it has gone away, we need to handle that gracefully.
This is necessary in order to safely modify a running pipeline. Has been
observed when a streaming thread is doing a buffer_alloc() while an
application thread sends an event on a pad further downstream, and from
within a pad probe (holding STREAM_LOCK) carries out the pipeline plumbing
while the streaming thread has its buffer_alloc() in progress.
1) We need to lock and get a strong ref to the parent, if still there.
2) If it has gone away, we need to handle that gracefully.
This is necessary in order to safely modify a running pipeline. Has been
observed when a streaming thread is doing a buffer_alloc() while an
application thread sends an event on a pad further downstream, and from
within a pad probe (holding STREAM_LOCK) carries out the pipeline plumbing
while the streaming thread has its buffer_alloc() in progress.
ghostpad: Fix pad callbacks so they handle when parent goes away
1) We need to lock and get a strong ref to the parent, if still there.
2) If it has gone away, we need to handle that gracefully.
This is necessary in order to safely modify a running pipeline. Has been
observed when a streaming thread is doing a buffer_alloc() while an
application thread sends an event on a pad further downstream, and from
within a pad probe (holding STREAM_LOCK) carries out the pipeline plumbing
while the streaming thread has its buffer_alloc() in progress.
1) We need to lock and get a strong ref to the parent, if still there.
2) If it has gone away, we need to handle that gracefully.
This is necessary in order to safely modify a running pipeline. Has been
observed when a streaming thread is doing a buffer_alloc() while an
application thread sends an event on a pad further downstream, and from
within a pad probe (holding STREAM_LOCK) carries out the pipeline plumbing
while the streaming thread has its buffer_alloc() in progress.
queue2: prevent calculation with GST_CLOCK_TIME_NONE in update_time_level()
tests: fix unusued-but-assigned-variable warnings with gcc 4.6
tests: disable test_many_bins unit test for now
It fails on the OSX bot (both with git and the last release), and
it doesn't really test anything useful, so may just as well disable
it for now.
It fails on the OSX bot (both with git and the last release), and
it doesn't really test anything useful, so may just as well disable
it for now.
pluginloader: fix compiler warnings
Cast string constants to make compiler happy.
Cast string constants to make compiler happy.
tests: allow more time for the test_many_bins pipeline to preroll
Hopefully makes this test work on the OSX build bot and other
not-so-powerful machines.
https://bugzilla.gnome.org/show_bug.cgi?id=646624
Hopefully makes this test work on the OSX build bot and other
not-so-powerful machines.
https://bugzilla.gnome.org/show_bug.cgi?id=646624
pluginloader: make sure gst-plugin-scanner is called with the right arch on OSX
On OSX, GStreamer might be built as a 'fat/universal' binary containing
both 32-bit and 64-bit code. We must take care that gst-plugin-scanner
is executed with the same architecture as the GStreamer core, otherwise
bad things may happen and core/scanner will not be able to communicate
properly.
Should fix issues with (32-bit) firefox using a 32-bit GStreamer core
which then spawns a 'universal' gst-plugin-scanner binary which gets
run in 64-bit mode, causing 100% cpu usage / busy loops or just hanging
firefox until killed.
https://bugzilla.gnome.org/show_bug.cgi?id=615357
On OSX, GStreamer might be built as a 'fat/universal' binary containing
both 32-bit and 64-bit code. We must take care that gst-plugin-scanner
is executed with the same architecture as the GStreamer core, otherwise
bad things may happen and core/scanner will not be able to communicate
properly.
Should fix issues with (32-bit) firefox using a 32-bit GStreamer core
which then spawns a 'universal' gst-plugin-scanner binary which gets
run in 64-bit mode, causing 100% cpu usage / busy loops or just hanging
firefox until killed.
https://bugzilla.gnome.org/show_bug.cgi?id=615357
pad: Allow tracking of buffers in GST_SCHEDULING debug output
As GST_SCHEDULING reports when buffers pass through pads due to
gst_pad_push calls, they are a good way of tracking the progress of
buffers through pipelines. As such, adding output of the buffer pointers
to these messages allows tracking of specific buffers, easing debugging.
As GST_SCHEDULING reports when buffers pass through pads due to
gst_pad_push calls, they are a good way of tracking the progress of
buffers through pipelines. As such, adding output of the buffer pointers
to these messages allows tracking of specific buffers, easing debugging.
android: make it ready for androgenizer
Remove the android/ top dir
Fixe the Makefile.am to be androgenized
To build gstreamer for android we are now using androgenizer which generates the needed Android.mk files.
Androgenizer can be found here: http://git.collabora.co.uk/?p=user/derek/androgenizer.git
Remove the android/ top dir
Fixe the Makefile.am to be androgenized
To build gstreamer for android we are now using androgenizer which generates the needed Android.mk files.
Androgenizer can be found here: http://git.collabora.co.uk/?p=user/derek/androgenizer.git
trace: don't put code with side effects into g_return_if_fail()
docs: minor fixes for baseparse docs
Class vfunc references still aren't right, no idea what
the correct markup for those is.
Class vfunc references still aren't right, no idea what
the correct markup for those is.
element: unref event in default_send_event in case element has no pads
Spotted by Haakon Sporsheim.
Spotted by Haakon Sporsheim.
baseparse: minor variable name clean-up
baseparse: rename _set_frame_props() to _set_frame_rate()
Seems like the best fit to what it does, and is shorter than
set_frame_properties() which might also have been confusing
because of GstBaseParseFrame.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
Seems like the best fit to what it does, and is shorter than
set_frame_properties() which might also have been confusing
because of GstBaseParseFrame.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
12 years agobaseparse: replace format flags with gst_base_parse_set_{passthrough,syncable,has_tim...
baseparse: replace format flags with gst_base_parse_set_{passthrough,syncable,has_timing_info}
This is more in line with e.g. GstBaseTransform's API, and makes for nicer
to read code. No getters for now since I don't see any use case for them,
the API is for subclasses, which usually know what format they're
dealing with already and hence know what they've set.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
This is more in line with e.g. GstBaseTransform's API, and makes for nicer
to read code. No getters for now since I don't see any use case for them,
the API is for subclasses, which usually know what format they're
dealing with already and hence know what they've set.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
12 years agobaseparse: make DRAIN and SYNC flags on baseparse, not the frame, and change to DRAIN...
baseparse: make DRAIN and SYNC flags on baseparse, not the frame, and change to DRAINING and LOST_SYNC
The first because it seems a better fit conceptually, the second
to express booleanness. Also change the accessor macros for subclasses
to GST_BASE_PARSE_DRAINING and GST_BASE_PARSE_LOST_SYNC.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
The first because it seems a better fit conceptually, the second
to express booleanness. Also change the accessor macros for subclasses
to GST_BASE_PARSE_DRAINING and GST_BASE_PARSE_LOST_SYNC.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
baseparse: add some padding to GstBaseParseFrame
Esp. since it's usually allocated on the stack.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
Esp. since it's usually allocated on the stack.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
baseparse: fix typo in docs for GST_BASE_PARSE_FORMAT_FLAG_PASSTHROUGH
https://bugzilla.gnome.org/show_bug.cgi?id=518857
https://bugzilla.gnome.org/show_bug.cgi?id=518857
baseparse: use GQueue instead of GList for queued frames
and make buffer metadata writable before setting caps on queued
buffer.
https://bugzilla.gnome.org/show_bug.cgi?id=646341
and make buffer metadata writable before setting caps on queued
buffer.
https://bugzilla.gnome.org/show_bug.cgi?id=646341
baseparse: add GST_BASE_PARSE_FLOW_QUEUED to queue buffers until caps are known
This is useful for parser like flacparse or h264parse which may need to process
some buffers before they can construct the final caps, in which case they may
want to delay pushing the initial buffers until the full and proper caps are
known.
https://bugzilla.gnome.org/show_bug.cgi?id=646341
This is useful for parser like flacparse or h264parse which may need to process
some buffers before they can construct the final caps, in which case they may
want to delay pushing the initial buffers until the full and proper caps are
known.
https://bugzilla.gnome.org/show_bug.cgi?id=646341
baseparse: add to docs and fix up gtk-doc markup a little
And add Since markers.
And add Since markers.
baseparse: replace set_seek() with _set_average_bitrate() and FLAG_SYNCABLE
This makes more sense conceptually, since the bitrate may be used
to estimate a seek position if there's no seek table or just for
duration reporting/estimation if we can't seek. Also, even if the
format is not syncable, we could still seek by pushing data from the
start and using the segment to make downstream clip.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
This makes more sense conceptually, since the bitrate may be used
to estimate a seek position if there's no seek table or just for
duration reporting/estimation if we can't seek. Also, even if the
format is not syncable, we could still seek by pushing data from the
start and using the segment to make downstream clip.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
baseparse: rename GstBaseFormat to GstBaseFormatFlags and fix up associated API
Also change gst_base_parse_set_format(parse,flags,switch_on) to
gst_base_parse_set_format_flags(parse,flags) which is more in line
with the rest of our API and how the function is used.
Also change gst_base_parse_set_format(parse,flags,switch_on) to
gst_base_parse_set_format_flags(parse,flags) which is more in line
with the rest of our API and how the function is used.
baseparse: don't expose GstAdapter in public header
None of the existing subclasses needs access to that, so there's
no reason to expose it for now.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
None of the existing subclasses needs access to that, so there's
no reason to expose it for now.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
baseparse: move various segment-related members into the private instance struct
If none of the existing subclasses uses these, there's probably no
need to expose them at the moment. Keep the segment itself exposed
though.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
If none of the existing subclasses uses these, there's probably no
need to expose them at the moment. Keep the segment itself exposed
though.
https://bugzilla.gnome.org/show_bug.cgi?id=518857
baseparse: remove unused GST_BASE_PARSE_{SINK,SRC}_NAME
https://bugzilla.gnome.org/show_bug.cgi?id=518857
https://bugzilla.gnome.org/show_bug.cgi?id=518857
baseparse: re-indent header
baseparse: fix up GType name and make _get_type() function thread-safe
Rename GType from GstBaseParseBad to GstBaseParse.
Rename GType from GstBaseParseBad to GstBaseParse.
libs: add GstBaseParse which was moved from -bad
baseparse: make_metadata_writable() fix
baseparse: rename GType from GstAudioBaseParseBad to GstBaseParseBad
We use it for video as well now.
We use it for video as well now.
baseparse: trim trailing whitespace
baseparse: use delta-unit flags instead of none
baseparse: update documentation for API changes
baseparse: Create baseparse library
baseparse: tune QUERY_SEEKING response
Even if we currently do not have a duration yet, assume seekable if
it looks like we'll likely be able to determine it later on
(which coincides with needed information to perform seeking).
Fixes #641047.
Even if we currently do not have a duration yet, assume seekable if
it looks like we'll likely be able to determine it later on
(which coincides with needed information to perform seeking).
Fixes #641047.
baseparse: Update min/max bitrate before first posting them
This avoids posting an initial min-bitrate of G_UINTMAX and max-bitrate
of 0.
https://bugzilla.gnome.org/show_bug.cgi?id=641857
This avoids posting an initial min-bitrate of G_UINTMAX and max-bitrate
of 0.
https://bugzilla.gnome.org/show_bug.cgi?id=641857