GNOME Bugzilla – Bug 387160
[qtdemux] posts buffering message which can cause hangs
Last modified: 2006-12-18 17:12:25 UTC
When operating in streaming mode, qtdemux posts BUFFERING messages on the bus if the stream headers are behind the movie data, to notify the user that something is happening while it reads the entire movie data into memory. These BUFFERING messages can confuse applications like gst-launch or totem (which might change pipeline state based on them), causing 'hangs'. qtdemux shouldn't post BUFFERING messages for this purpose. Attached patch changes qtdemux to post element messages called "progress" instead that applications can catch separately if they want to.
Created attachment 78568 [details] [review] patch, changes qtdemux to post an ELEMENT message instead of a BUFFERING message
2006-12-18 Tim-Philipp Müller <tim at centricular dot net> * gst/qtdemux/qtdemux.c: (gst_qtdemux_post_progress), (gst_qtdemux_chain): Don't post BUFFERING messages in streaming mode if the stream headers are behind the movie data, but post a "progress" element message instead as a temporary solution so that apps don't get confused by buffering messages from different sources (#387160).