TIME seek with filesrc - using demuxer and muxer unnecessarily

amitchawla amit at wowvision.in
Thu Jun 30 06:24:05 UTC 2016


Hi Sebastian,

I have been doing a experiment to check if a proper BYTES value from the
receiver gives me correct playback of a .mov file when I do a BYTES seek at
the sender. 

So, I ran the receiver without tcpserversrc but with a filesrc, and from
qtdemux DEBUG messages, I figured the byte offset generated by doing a TIME
seek at 40 seconds. 

Then, I ran my original set up with tcpseversrc and tcpclientsink at either
ends, and hard-coded the byte offset as position parameter in BYTES seek
operation at the sender. The receiver exited with unable to decode stream
error. It seems that the position mentioned in BYTES seek operation at the
sender is not correct. ...... I have used the same .mov file for both the
experiments.

Before doing a BYTES seek at the sender, do I have do a pipeline flush at
the receiver and the sender ?

I would be thankful for your reply.

Regards
Amit



--
View this message in context: http://gstreamer-devel.966125.n4.nabble.com/TIME-seek-with-filesrc-using-demuxer-and-muxer-unnecessarily-tp4677985p4678321.html
Sent from the GStreamer-devel mailing list archive at Nabble.com.


More information about the gstreamer-devel mailing list