GNOME Bugzilla – Bug 159298
dark.441-16-s.wav from testsuite just 'lags' in totem
Last modified: 2004-12-22 21:47:04 UTC
(totem:25939): GStreamer-WARNING **: element internal_thread claimed state-change success,but state didn't change to PLAYING. State is PAUSED (NONE_PENDING pending), fix the element (totem:25939): GStreamer-WARNING **: element internal_thread claimed state-change success,but state didn't change to PLAYING. State is PAUSED (NONE_PENDING pending), fix the element
Still true with current CVS of everything
Reproduce for me with: [cschalle@cschalle small]$ gst-launch playbin uri=file:///home/cschalle/media/small/dark.441-16-s.wav RUNNING pipeline ... (process:31700): GStreamer-WARNING **: element internal_thread claimed state-change success,but state didn't change to PLAYING. State is PAUSED (NONE_PENDING pending), fix the element Waiting for the state change... got the state change. [cschalle@cschalle small]$ Works for Wim with same command line...
Created attachment 34587 [details] GST_DEBUG output from when it fails
Just did some testing here with Wim. When I play using playbin I do get the element internal error, which Wim says can't be fixed with current design. But the file actually plays so it might not be that much of an issue. In Totem however I get tons of: (totem:13851): GStreamer-WARNING **: pads don't accept old caps. We assume they did though And the sounds 'lags'. Wim don't think that is caused by the threading issue.
I had a closer look, and playbin does the same it also does for #154773 - it creates infinite amounts of wavparse elements. I guess wavparse needs fixing. *** This bug has been marked as a duplicate of 154773 ***