> There is also an option: int b_repeat_headers; /* put SPS/PPS before each
> keyframe */. It should be set in 0?
I suggest setting this to 1, to ensure that the downstream
"H264VideoStreamDiscreteFramer" gets to see the SPS and PPS NAL units at least
once. (This is important, otherwise the R
Sorry. You are right. In x264.h written:int b_annexb; /* if set, place start codes (4 bytes) before NAL units, * otherwise place size (4 bytes) before NAL units. */Thus in any case, the first 4 bytes should be removed. There is also an option: int b_repeat_headers; /* put S
> Warning: Invalid 'nal_unit_type': 0. Does the NAL unit begin with a MPEG
> 'start code' by mistake?
This message means exactly what it says (and you can very easily see - in the
"H264VideoStreamDiscreteFramer" source code - where/why it's displayed).
Remember, You Have Complete Source Code.
I'm not sure I totally understand what you're asking/suggesting (but since you
use a non-professional email address, I really don't care :-). But it sounds
like you want to perform RTSP client operations in a 'synchronous' way, whereby
you block - waiting for the response to each RTSP request -
libx264 returns a pointer to an array of NAL units during encoding using the
function x264_encoder_encode. But i can't feed them
H264VideoStreamDiscreteFramer.
My code in DeviceSource:
...
newFrameDataStart = (u_int8_t*)(nals[current_nal].p_payload);
newFrameSize = nals[current_nal].
As a user of your library, i have some problems with your RTSPClient
while integrating it to my app.
So i decide to write my "pains" and my "ideal" client example for testRTSPClient
-- What i need to create client? Do i have to know "env" or "task scheduler?
string rtspUrl = "rtsp:///video.h
