GNOME Bugzilla – Bug 795882
id3demux : Does not send segment-start and segment-done message
Last modified: 2018-11-03 15:29:45 UTC
I have developed an application to stream a file indefinitely by looping it. For looping, I do a segment seek and then catch the SEGMENT_DONE message. However, this approach works for Mp4 and not work for mp3. Digging deeper, I found id3mux does not send these messages One another issue here is the id3demux is optional for mp3 decoding. Decodebin does not autoplug id3demux for certain mp3 files but directly uses the mpegaudioparse. I'm not really sure which element is to send segment-start and segment-done messages in such a case
The seek handler is responsible for sending those messages on segment seeks. It can be id3demux or mpegaudioparse. As far as I can tell id3demux should post those messages (or rather,it's the parent gsttagdemux class that does). mpegaudioparse (via the baseparse parent class) posts message_done also. Can you grab logs with GST_DEBUG=2,*tag*:6,*parse*:6,*id3*:6,*MESSAGE*:6 ?
It will depend on the mode of operation. If the source is a filesrc, mpegaudioparse (and id3demux and filesrc) should operate in pull mode and mpegaudioparse should be driving the pipeline.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/gstreamer/gst-plugins-good/issues/471.