Thanks, guys. That did it. There's some other issus with the stream from
the camera but I have it working well enough for what I need.
Len
On 10/16/2016 09:35 PM, Ross Finlayson wrote:
Well, an H264 NAL must begin with 00 00 00 01.
No. “00 00 00 01” is a standard ‘start code’ that is often
> Well, an H264 NAL must begin with 00 00 00 01.
No. “00 00 00 01” is a standard ‘start code’ that is often put in front NAL
units when they appear in a byte stream. But it’s not part of the NAL unit
itself, and it is not used at all when NAL units are carried within RTP
packets. (That’s
Thanks for getting back so quickly. I do see the MAC for the camera in
the first 16 bytes.
Well, an H264 NAL must begin with 00 00 00 01. At least that's what I
read... Maybe I'm not reading enough. Do I have some other format?
When I pass the data that I do get to avcodec_decode_video2 I
> A usual Ethernet header is 14 bytes. Why do we have 16?
Dunno. Ask the OP’s ‘Wireshark’. The rest of the bytes are as I described,
though.
Ross Finlayson
Live Networks, Inc.
http://www.live555.com/
___
live-devel mailing list
555.com>
Subject: Re: [Live-devel] Missing 44 bytes
Just to clarify some more - your ‘missing’ 44 bytes are just the Ethernet
header (16 bytes), the IP header (20 bytes), and the UDP header (8 bytes).
Specifically breaking down your ‘Wiresha
Just to clarify some more - your ‘missing’ 44 bytes are just the Ethernet
header (16 bytes), the IP header (20 bytes), and the UDP header (8 bytes).
Specifically breaking down your ‘Wireshark’ output:
> 00 00 00 01 00 06 00 12 14 1b f7 78 00 00 08 00 ...x
> 0010 45 00 00 3e
From what I can tell, you’re on a ‘wild goose chase’. Your code seems to be
working just fine:
> Here's the first RTP packet after PLAY as reported by wireshark:
[…]
>Payload: 674d002a95a81e0089f96103000103000284
>
> 00 00 00 01 00 06 00 12 14 1b f7 78 00 00 08 00
