>> As you can see, the RTSP client is not passing 'track1' in the SETUP url.
>
> Yes, and that's what's causing the problem. "SETUP" is an operation on a
> specific track within the file, not on the file as a whole. The RTSP client
> should be adding "/track1" to the URL for the "SETUP" comman
> As you can see, the RTSP client is not passing 'track1' in the SETUP url.
Yes, and that's what's causing the problem. "SETUP" is an operation on a
specific track within the file, not on the file as a whole. The RTSP client
should be adding "/track1" to the URL for the "SETUP" command.
*Howe
Ross,
Thanks for the prompt feedback.I tried now with 0.72 but the problem still
occurs. Wit the embedded RTSP player of the setop box (player software coming
from Broadcom I think) I still get a "404 Stream Not Foud" response on the
SETUP request.
Here is the RTSP dump (exported from wireshark
> I read in the history notes that starting from v.0-71 streaming from a
> subdirectory (like in: rtsp:///MyVideos/MyStreams/a-video.ts) now works.
> I can confirm that it indeed works with the VLC player, but unfortunately not
> with the RTSP player I am working with on an embedded device (a bro
Hi,
I read in the history notes that starting from v.0-71 streaming from a
subdirectory (like in: rtsp:///MyVideos/MyStreams/a-video.ts) now works.I
can confirm that it indeed works with the VLC player, but unfortunately not
with the RTSP player I am working with on an embedded device (a browse
