[gst-devel] H.264 streaming: choppy video + timestamp warnings

[Parisot, Adam]

Hi all,

I'm trying to develop a GStreamer-based application to receive and
display H.264 video from a network source.  The protocol is not
particularly important.  I've tried raw UDP with MPEG-TS encapsulation
as well as RTP with no encapsulation and I'm seeing the same performance
issue in both cases.

Video starts skipping badly shortly after initiating playback and I see
these warnings from GStreamer:

> 0:00:03.165877350 21089       0xb09010 WARN                basesink
gstbasesink.c:2686:gst_base_sink_is_too_late:<sink> warning: A lot of
buffers are being dropped.
> 0:00:03.165917755 21089       0xb09010 WARN                basesink
gstbasesink.c:2686:gst_base_sink_is_too_late:<sink> warning: There may
be a timestamping problem, or this computer is too slow.

I can stream point-to-point between two instances of VLC just fine, so I
don't think there's an inherent problem with the hardware or network.

My pipeline looks like this (for UDP + MPEG-TS):

> udpsrc port=8200 caps="video/mpegts" \
>   ! mpegtsdemux \
>   ! ffdec_h264 \
>   ! glimagesink

I have tried inserting a queue at various points in the pipeline and an
"h264parse" element before the decoder, but neither brings any
noticeable improvement.

Also, the GStreamer core and good/bad/ugly plugin sets are all at the
latest released revisions.

Can anyone offer any insight as to what might be causing this behavior?

-- 
Regards,
Adam


DISCLAIMER:
Unless indicated otherwise, the information contained in this message is privileged and confidential, and is intended only for the use of the addressee(s) named above and others who have been specifically authorized to receive it. If you are not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this message and/or attachments is strictly prohibited. The company accepts no liability for any damage caused by any virus transmitted by this email. Furthermore, the company does not warrant a proper and complete transmission of this information, nor does it accept liability for any delays. If you have received this message in error, please contact the sender and delete the message. Thank you.