> Based on your earlier post I was able to understand how to use filter for
> transcoding.and I'am able to transcode the video stream.
>
> However I have one problem in it. I cannot use 1 stream coming from the
> camera to be transcoded to multiple transcoded images.
When you say “1 stream
Hi,
I've been working on capturing an RTSP stream from a Sunba H.264 camera.
O/S is Linux, I have gotten the same result for X86-64 and for ARM
(Raspbian).
Linux len 3.19.0-32-generic #37~14.04.1-Ubuntu SMP Thu Oct 22 09:41:40
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
Linux pi5 4.1.13-v7+
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
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
> 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
> 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
A usual Ethernet header is 14 bytes. Why do we have 16?
Hemant
-Original Message-
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross
Finlayson
Sent: Sunday, October 16, 2016 9:52 PM
To: LIVE555 Streaming Media - development & use
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