mpegtsmux at high bitrates

[Chuck Crisler]

I have noticed a significant CPU cost for MP2T myself, though I run at
*MUCH* lower bitrates. There is also the issue that MPEG2 TS breaks the
bitstream into ridiculously small packets (188 bytes of data), which also
imposes some burden.


On Wed, Oct 9, 2013 at 10:15 AM, cfadeley <chrisfadeley at gmail.com> wrote:

> Has anyone else experience issues with the mpegtsmux plugin at high
> bitrates?
> Seems like any point higher than 3mb/s causes frames to be dropped by the
> ts
> muxer.
>
> I am streaming out to rtp using gst-rtsp-server.
>
> When compressing an image to a bitrate of 5mb/s I can do the following:
> encoder --> rtph264pay --> server
> and I will have the expected framerate produced all the way through the
> pipeline (30fps).
>
> But if I add a ts to the system:
> encoder -->mpegtsmux -->rtpmp2tpay -->server
> I get a much lower framerate of around 20fps.
>
> Again this only happens at higher bitrates and I can confirm it is not the
> encoder since I can watch the framerate out of the encoder.  This results
> in
> the issue either at the mpegtsmux or the rtp payloder.  And I doubt it is
> the later since it is so simple.
>
> I can also see that at higher bitrates the mpegtsmux plugin has a much
> higher CPU usage.  And i would not be surprised if this causes the drops in
> frames due to the mpegtsmux failing to keep up.
>
> I am just curious if anyone else is aware of this issue and/or if it is
> only
> on my side of things.
>
>
>
> --
> View this message in context:
> http://gstreamer-devel.966125.n4.nabble.com/mpegtsmux-at-high-bitrates-tp4662473.html
> Sent from the GStreamer-devel mailing list archive at Nabble.com.
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20131009/f00f1fee/attachment-0001.html>