> Also, we would like to find out which frames are key frames so we will try to
> get that by passing the packets to ffmpeg which should construct the frame
> and tell us whether its a key frame.
That makes no sense. The things that you feed into “ffmpeg” (and other
decoders) are *frames* (or,
should construct the frame and tell us
whether its a key frame.
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross
Finlayson
Sent: 04 March 2015 16:43
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] RTP header information
I have been trying to
Thanks for your response. I will have a look as you suggest.
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Deanna
Earley
Sent: 04 March 2015 13:29
To: 'live-devel@lists.live555.com'
Subject: Re: [Live-devel] RTP header information
Which header data are
> I have been trying to work out how I can get Live555 to provide me with the
> RTP packet header data as well as the payload but have had no luck. I did
> look at using a SimpleRTPSource but that seems to strip off the RTP header as
> well.
Our code doesn’t just ‘strip off’ the RTP header - it
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Minor,
Matt
Sent: 04 March 2015 10:23
To: live-devel@lists.live555.com
Subject: [Live-devel] RTP header information
Dear Live555,
I have been trying to work out how I can get Live555 to provide me with the RTP
packet
Dear Live555,
I have been trying to work out how I can get Live555 to provide me with the RTP
packet header data as well as the payload but have had no luck. I did look at
using a SimpleRTPSource but that seems to strip off the RTP header as well. Is
there any way to do this?
Many thanks,
Matt
