GNOME Bugzilla – Bug 534154
[ffmux_mpegts] Mpeg TS muxer does not set timestamps
Last modified: 2011-09-12 17:56:42 UTC
Please describe the problem: When muxing mpeg ts the plugin eats 80% of CPU and outputs buffers too quickly (not on the clock). Steps to reproduce: 1. gst-launch videotestsrc ! ffmpegcolorspace ! ffenc_mpeg2video ! ffmux_mpegts ! fakesink 2. 3. Actual results: Cpu usage bounces to 80% and file gets sent too quickly Expected results: Cpu stays as low as possible under 5% Does this happen every time? Yes Other information:
For reference, the problem here is that the MPEG-TS muxer doesn't put any timestamps on the buffers of the outgoing stream - so fakesink has nothing it can use to synch with the clock and run at realtime. Also, fakesink has sync=false by default, so it would still run at full speed even if ffmux_mpegts was enhanced to forward timestamps. Another option would be to add timestamp output to mpegtsparse (I think Zaheer might have been planning to do so already), and then feed the output of ffmux_mpegts through the parser to get timestamps applied.
Is this still a probablem nowadays? mpegtsparse seems to set timestamps on buffers and the mpegtsmux element from gst-plugins-bad should probably be used instead of the ffmpeg muxers.
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!