After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 656270 - queue2 missing signals
queue2 missing signals
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
git master
Other Linux
: Normal normal
: git master
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-08-10 11:07 UTC by Levente Farkas
Modified: 2011-08-10 14:42 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Levente Farkas 2011-08-10 11:07:31 UTC
hi,
as it's recommended to use all elements the "2" version (as the old owns are dropped in 0.11) it'd be useful to add to queue2 the signals was in queue:
underrun, running, overrun, pushing or at least the underrun and overrun since it's an important information for the application.
thanks.
Comment 1 Sebastian Dröge (slomo) 2011-08-10 11:16:32 UTC
queue2 uses buffering messages for this
Comment 2 Levente Farkas 2011-08-10 11:36:17 UTC
ohh my fault:-(
and how can wee get the same affect as "leaky" in queue?
Comment 3 Stefan Sauer (gstreamer, gtkdoc dev) 2011-08-10 11:53:54 UTC
(In reply to comment #2)
> ohh my fault:-(
> and how can wee get the same affect as "leaky" in queue?

You can't really. Depending on your use-case the "valve" element might come handy.
Comment 4 Levente Farkas 2011-08-10 12:00:05 UTC
this means i've to write a rather complicated control based on buffering messages and valve control. what's more in case of a fast pipeline (25fps video) it can be late to drop frames.

anyway i can'r find any useful docs about the "buffering messages" used by queue2. what's more gst_message_new_buffering () said:
"When percent is < 100 the application should PAUSE a PLAYING pipeline. " 
which is not we want...
Comment 5 Stefan Sauer (gstreamer, gtkdoc dev) 2011-08-10 14:42:00 UTC
Just keep using queue then. I don't see queue2 replacing queue, both have different feature sets. Its clearly not optimal to have 2 of them, coming up with distinct names would help.