> Can I confirm that this shouldn’t interact with the file sink buffer sizes as
> they effectively receive decoded and depacketised frames?
They’re different buffers, with different purposes.
A single RTP packet may contain one or more ‘frames’ (for H.264 video: ‘NAL
units’). Or a single very
1 8BZ. Company Number : 03428325
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross
Finlayson
Sent: 15 April 2015 22:26
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Maximum interleaved RTP packet size
I might, however, add a mechanism that will
Of *Ross Finlayson
*Sent:* 15 April 2015 18:33
*To:* LIVE555 Streaming Media - development & use
*Subject:* Re: [Live-devel] Maximum interleaved RTP packet size
We have an open case with one of our RTSP source vendors where RTP
streams over interleaved TCP seem to be throttled resu
er : 03428325
From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Ross
Finlayson
Sent: 15 April 2015 18:33
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Maximum interleaved RTP packet size
We have an open case with one of our RTSP so
evel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of Deanna
Earley
Sent: 15. april 2015 16:10
To: 'live-devel@lists.live555.com'
Subject: Re: [Live-devel] Maximum interleaved RTP packet size
If you're interested, here's a patch that adds custom headers to the
Request
> I might, however, add a mechanism that will allow the client code to specify
> that it wants a specific incoming packet size, and then (if this option is
> set) include a “Blocksize:” header in its requests.
FYI, I’ve just released a new version (2015.04.15) of the “LIVE555 Streaming
Media” c
> We have an open case with one of our RTSP source vendors where RTP streams
> over interleaved TCP seem to be throttled resulting in dropped frames in
> situations where the camera increases the frame size.
> This does not happen with UDP unicast.
> For reference, here's the video explaining the
: 15 April 2015 15:45
To: LIVE555 Streaming Media - development & use
Subject: Re: [Live-devel] Maximum interleaved RTP packet size
I'd rather not hard code a header string in the liveMedia code so is there any
nice mechanism to be able to pass additional headers in the RTSP request?
What
> I'd rather not hard code a header string in the liveMedia code so is there
> any nice mechanism to be able to pass additional headers in the RTSP request?
What specific RTSP header(s) do you want to add?
> I can't see one, and if not, would you be open to patches that implement this?
Not for
d, Romsey, SO51 8BZ. Company Number : 03428325
> -Original Message-
> From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of
> Deanna Earley
> Sent: 15 April 2015 14:20
> To: 'live-devel@lists.live555.com'
> Subject: Re: [Live-devel] Maximum int
> -Original Message-
> From: live-devel [mailto:live-devel-boun...@ns.live555.com] On Behalf Of
> Deanna Earley
> Sent: 15 April 2015 11:15
> To: 'live-devel@lists.live555.com'
> Subject: [Live-devel] Maximum interleaved RTP packet size
>
> Hello Ross.
>
Hello Ross.
We have an open case with one of our RTSP source vendors where RTP streams over
interleaved TCP seem to be throttled resulting in dropped frames in situations
where the camera increases the frame size.
This does not happen with UDP unicast.
For reference, here's the video explaining
12 matches
Mail list logo
