After tonight, I'm convinced something is wrong with my SDP stuff.
I fired up Wireshark to see the traffic between my transmitting
application and VLC, and I don't see the SDP stuff anywhere in the
bitstream. Would it be contained in the RTP packets, or the RTCP
packets?
No, the SDP descript
Thanks for the response Debargha.
<< You need to send NAL units to your H264VideoRTPSink. Is the X264 encoder
you are using creating a single NAL unit per video frame encoded? >>
My encoder is creating a single NAL unit per video frame encoded. I
verified that very thing this evening just to dou
...@ns.live555.com
Subject: Re: [Live-devel] H.264 NAL confusion
I'm still struggling to get this code to work correctly, and I'm sure I'm just
doing something dumb (sorry, new to Live555 and H.264, and the available
samples leave much to be desired). I've attached the co
I'm still struggling to get this code to work correctly, and I'm sure I'm
just doing something dumb (sorry, new to Live555 and H.264, and the
available samples leave much to be desired). I've attached the code I've
written/used (some of it is stuff I found previous posters had used).
Once again,
I'm confused about what information I need to supply to the framer
to get all this to work correctly. So far it seems I need to:
1. Supply NAL units
2. Implement currentNALUnitEndsAccessUnit() (for me, this always
returns true since each NAL unit I have seems to correspond with a
whole encod
> Yes. (I wonder, what were you passing as the "sprop_parameter_sets_str"
parameter before??
> That parameter is there for a reason.
Before, just "h264" which is what the sample code I started with used (I was
hoping I could just start with an existing sample and move forward, but
apparently it's
1. I have my stream running, but I can't seem to get VLC to digest
it. Should VLC be able to play it?
Yes, but this is not a VLC mailing list.
2. Do I need to do anything with PPS and SPS information?
Yes. You need to Base-64-encode each of these special NAL units,
concatenate the result
> No. Our software (in particular, the "H264VideoRTPSink" class)
> already implements the RTP payload format described in RFC 3984.
> All you need to do is deliver - one at a time - NAL units to it
> (*without* a preceding 'length' field).
Ross,
Thank you for the clarification. A few follow up
My question is: do I need to package this according to RFC 3984?
No. Our software (in particular, the "H264VideoRTPSink" class)
already implements the RTP payload format described in RFC 3984.
All you need to do is deliver - one at a time - NAL units to it
(*without* a preceding 'length' fi
As an H.264 source, I'm using a DirectShow filter implementation of x264
which can be found here:
http://blog.monogram.sk/janos/2008/12/29/monogram-x264-encoder-1020/
...and here are some comments by the author of that x264 filter regarding
the output:
<< This filter delivers NAL units in the fo
10 matches
Mail list logo
