<div dir="ltr"><p>Hi there,<br></p><p>As an older thread, found in March 2008 archives, an alternative syntax exists for RTSP urls.</p><p>Here is a quote :</p><p>//////</p><p>>What I'd like to do:<br>><br>>MPEG4 streams: rtsp://host/video/MPEG4/stream[number]<br>
>H263 streams: rtsp://host/video/H263/stream[number]<br>><br>>Please note the filenames pathnames are "virtual", i.e. they don't<br>>exist. Every stream is associated to a live source read from a<br>
>configuration file, and it has no correspondent in the file system<br><br>Then why bother? I'm sure you could (somehow) hack the RTSP server <br>code to do what you want to do, but why not just use a character <br>
other than "/" in the RTSP URLs - e.g.,<br> rtsp://host/video:MPEG4:stream[number]<br>? This would require no change to the existing code.<br>//////<br></p><p>I wanted to verify this point, and it doesn't seem to work for me, or maybe I don't get the whole point at all :)</p>
<p>For instance, i have a medium that is located in this sub-tree : ./foo/bar/baz/video.mpg</p><p>As the RTSP server runs at the root of this tree, I thought I could access the medium with this url :</p><p>rtsp://localhost:6666/foo:bar:baz:video.mpg</p>
<p>Am I wrong on this one ?</p><p>Thanks in advance,</p><p>Guillaume.</p></div>