[Help] streaming GoPro Hero 4

[Sebastian Dröge]

On Mi, 2016-06-22 at 21:10 -0400, Gal Nissim wrote:
> Dear Sebastian,
> 
> Since the GoPro Hero 4 is streaming with "ffplay", I guess the
> problem is not in the GoPro hardware but rather a bug in GStreamer. 
> 
> Here is an example of an apirance for "lost sync" in the log file
> ("lost sync" appeared repetitively):
> 
> 0:00:02.345848000 48195 0x7f9b01063280 LOG               mpegtsbase
> mpegtsbase.c:1207:mpegts_base_chain: PID 0x1011 Saw packet on a pid
> we don't handle
> 0:00:02.345857000 48195 0x7f9b01063280 DEBUG       mpegtspacketizer
> mpegtspacketizer.c:841:mpegts_packetizer_next_packet: lost sync
> 0:00:02.345864000 48195 0x7f9b01063280 LOG         mpegtspacketizer
> mpegtspacketizer.c:676:mpegts_packetizer_flush_bytes: flushing 3608
> bytes from 

Yes that's exactly what I'm saying ;)


You can try increasing the buffer size of the udpsrc for starters, that
might help with the problem.

In any case, you'll have to check if the problem is really packet loss
(from which ffmpeg might recover better for whatever reason, and we
should improve our demuxer then), or if reading from the UDP socket
happens too slow.

It would also help if you could make a dump of the stream available,
then someone could take a closer look at that. Just connect udpsrc with
a queue and a filesink.

-- 

Sebastian Dröge, Centricular Ltd · http://www.centricular.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: This is a digitally signed message part
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20160623/f999956f/attachment.sig>