H264Parse output-format types

[Chuck Crisler]

Yes, I (unfortunately) know that. I am just trying to make this code work
with my current system for now and need to understand the implications of
parameter options. I will not waste anyone's time filing a bug against this
ancient code, I just need to understand it.


On Mon, Nov 11, 2013 at 10:47 AM, Sebastian Dröge <sebastian at centricular.com
> wrote:

> On Mo, 2013-11-11 at 15:36 +0000, Tim Müller wrote:
> > On Mon, 2013-11-11 at 09:47 -0500, Chuck Crisler wrote:
> >
> > Hi Chuck,
> >
> > > I am just asking basically what the terms mean, what is the difference
> > > in the output formats? I have been using AVC Sample Format and found
> > > that the H264Parse was re-writting my first 1 or 2 bytes (depending on
> > > the type code), causing serious downstream problems (as in total
> > > failure). This was video that, in this particular case, originated as
> > > RTP from an Axis camera, was transmuxed to multi-cast MP2T, then
> > > processed back to RTP via MP2TDemux -> H264Parse -> RTPH264Pay ->
> > > UDPSink.
> >
> > Sounds like something that would need to be investigated in some more
> > detail, maybe there's a bug somewhere. In this setup h264parse shouldn't
> > really need to modify anything, it should be able to just pass through
> > the data as it comes in (assuming things are negotiated right and the
> > depayloader outputs byte-stream).
>
> Also there where many changes in h264parse since 0.10, including many,
> many fixes to make it produce better streams and be better at parsing
> weird h264 streams.
>
> --
> Sebastian Dröge <sebastian at centricular.com>
> Centricular Ltd - http://www.centricular.com
> Expertise, Straight from the Source
>
> _______________________________________________
> 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/20131111/ca226fdf/attachment-0001.html>