[Bug 763278] tcpserversink problems with TS muxed stream.

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=763278

--- Comment #6 from Peter Maersk-Moller <pmaersk at gmail.com> ---
See inline

(In reply to Sebastian Dröge (slomo) from comment #3)
> You run "git bisect" according to its documentation in a GStreamer checkout,
> and for each step check if your problem is still there or disappeared. In
> the end it tells you which commit is the problem.

I'm checking it now. However it's a little complicated as it is probably caused
by a relation between at least two modules. Anyway, I'll give it a go.


> In any case, I'm not sure what the problem is you're observing. I tried this
> pipeline. With sync-method=2, nc never receives any data. In 1.7.90 and
> 1.6.3. With the default sync-method it does. Is this the problem you see?
> Which versions are you actually testing?
> 
> > gst-launch-1.0 -v audiotestsrc !\
> >         queue ! audioconvert ! audiorate !\
> >         voaacenc bitrate=128000 !\
> >         audio/mpeg,mpegversion=4, stream-format=raw !\
> >         aacparse ! queue !\
> >         muxer. videotestsrc !\
> >         queue max-size-bytes=0 leaky=2 max-size-buffers=30 !\
> >         videoconvert ! queue !\
> >         x264enc bitrate=3499 tune=zerolatency speed-preset=6 key-int-max=60 bframes=0 !\
> >         video/x-h264,alignment=au,stream-format=byte-stream,profile=main !\
> >         h264parse ! queue !\
> >         mpegtsmux name=muxer !\
> >         tsparse ! queue !\
> >         tcpserversink port=5010 host=127.0.0.1 sync-method=2


And that is probaly not the way to test it as you we have seen many times when
using audiotestsrc and videotestsrc since they start with time=0 while the
fdsrc and shmsrc with do-timestamp starts at time!=0. And you used voaacenc,
although that may not matter.

For testing purpose, does audiotestsrc output the same sort of timestamps as
'fdsrc do-timestamp=1' does if you set timestamp-offset=SOMETHING for
audiotestsrc or does audiotestsrc do some magic bus communication behind the
scene telling it is starting at zero anyway ? If not, it would be practical for
tests if audiotestsrc could start with timestamps similar to shmsrc and fdsrc
etc.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.