[FFmpeg-devel] [PATCH] RTSP-MS 9/15: add interleave property to the TCP transport line of the SETUP request

Ronald S. Bultje rsbultje
Tue Jan 6 14:12:49 CET 2009

Hi Luca,

On Tue, Jan 6, 2009 at 7:43 AM, Luca Barbato <lu_zero at gentoo.org> wrote:
> Ronald S. Bultje wrote:
>> When choosing TCP as a transport, RTP-compliant servers will
>> automatically select an interleave ID for each stream transmitted over
>> the TCP session. This property can then be used client-side to detect
>> which stream each packet belongs to. Somehow, Microsoft RTSP wants us
>> to request the ID client-side in the SETUP request.
>> This patch adds support for this weird protocol construction...
> Looks ok but
>  >                            ";unicast;interleaved=%d-%d",
> unicast isn't necessary, defining interleaved is part of the standard
> anyway.

Without unicast it refuses to start here (server replies 461:
unsupported transport protocol).

If you prefer, I can place the unicast alone under the if (WMS) and
place the interleave outside it so the default RTSP uses it also.


More information about the ffmpeg-devel mailing list