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 627164 - mad hangs when segment seek is issued
mad hangs when segment seek is issued
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-plugins-ugly
0.10.30
Other Windows
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-08-17 14:47 UTC by Vladimir Eremeev
Modified: 2013-08-20 14:02 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
code (6.97 KB, application/octet-stream)
2010-08-17 14:47 UTC, Vladimir Eremeev
Details

Description Vladimir Eremeev 2010-08-17 14:47:32 UTC
Created attachment 168088 [details]
code

The attached code decodes a MPEG2-PS file and saves its parts to a new MPEG2-PS file.

It builds a pipeline consisting from uridecodebin, audioconvert, mad ffenc_mpeg2video, twolame, mpegpsmux and filesink.

It also temporarily sets the rank for the flump3dec to none, so that uridecodebin doesn't take it for decoding.

Then the code sets the pipeline to paused.
When state-changed message from the pipeline arrives, it issues the segment seek and sets the pipeline to playing.

On segment-done message the new segment seek is issued, or, if this is a last segment played, g_main_loop_quit is called.

The code also starts a timer using g_time_out_add, which queries the playing position and outputs some statistics.

The problem is that the second segment-done message never arrives on windows, and that timer constantly reports the same playing position.

The same code (except file paths) plays fine on Linux.
Comment 1 Glen Peterson 2011-10-31 15:22:02 UTC
Are you sure it works fine on Linux -even 64-bit?  What about this:
https://bugzilla.gnome.org/show_bug.cgi?id=645895
Affects Banshee, but also Rhythmbox (but not Audacity).  Could gstreamer be the underlying cause?
Comment 2 Sebastian Dröge (slomo) 2013-08-20 13:46:21 UTC
Is this still a problem with GStreamer 1.0? Could you get a backtrace of all threads when it hangs with a recent 1.0 GStreamer version?
Comment 3 Tim-Philipp Müller 2013-08-20 14:02:24 UTC
mad doesn't handle seeking any longer in 1.0, and even in 0.10 mpegaudioparse has been handling that forever, so I'd say let's just close this.

Please re-open if this is still an issue with 1.0 and you have an updated test case, thanks.