[Live-devel] [PATCH] Sets RTP-Info for every subsession

[Rafaël Carré]

On Mon, 2008-09-08 at 23:35 -0700, Ross Finlayson wrote:
> >I understand that the 2nd call to parseRTPInfoHeader() should go away:
> >parse the rtpinfo once, and then associate it to all subsessions.
> 
> That's not correct.  Each subsession should have a *separate* list of 
> parameters, within the "RTP-Info:" header.  E.g., consider the 
> example given in RFC 2326:
>       RTP-Info: 
> url=rtsp://foo.com/bar.avi/streamid=0;seq=45102,url=rtsp://foo.com/bar.avi/streamid=1;seq=30211
> 
> Note the two parameter lists, separated by ",".

Indeed, that's what the server sends me.
RTP-Info: url=rtsp://example.org/bar.asf/audio;seq=34421;rtptime=0,
url=rtsp://example.org/bar.asf/video;seq=24151;rtptime=0

> As far as I can tell, the existing code correctly handles reponses 
> from compliant servers.

The code just iterates over the lists separated by "," on one side, and
over the subsessions on the other side, but it doesn't check that the
list it is parsing is associated to the particular subsession.

The 3 subsessions are declared in this order:
audio, application, video.

So application gets associated to the rtpinfo of the video subsession,
and the video to nothing.

I'll send another patch shortly, thanks for the details.

-- 
Rafaël Carré <rcarre at m2x.nl>