Is there a possible bug that after you request something higher than 3570 seconds it is not working on transport stream files? It always brings me back to the same scene.<br><br>Transport file length : 20177187044 (20GB)<br>
Index file lenght : 1151033004 (1.1 GB)<br><br>Thanks.<br><br><div class="gmail_quote">On Thu, Apr 2, 2009 at 11:18 AM, Steve Malenfant <span dir="ltr"><<a href="mailto:smalenfant@gmail.com">smalenfant@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">I can't use the live555 client, I'm using an Amino STB. My first test failed (maybe I used the wrong stream with no trick play), but my second test just worked.<br>
<br>Thanks.<br><br><br><div class="gmail_quote"><div><div></div><div class="h5">On Wed, Apr 1, 2009 at 5:21 PM, Ross Finlayson <span dir="ltr"><<a href="mailto:finlayson@live555.com" target="_blank">finlayson@live555.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div><div></div><div class="h5">
<div><div>
<blockquote type="cite">Seems like there is an option in RTSP to
specify a range in time that you want to start your
stream.</blockquote>
<div><br></div>
</div><div>Yes, and we support it, for both RTSP clients and RTSP
servers.</div>
<div><br></div>
<div>For RTSP clients: Note the "start" and "end"
parameters to "RTSPClient:: playMediaSession()" and
"RTSPClient:: playMediaSubsession()". These parameters
(if set to non-default values) tell the RTSP client to request a
specific time range.</div>
<div><br></div>
<div>For RTSP servers: Our RTSP server implementation (including its
use in the "LIVE555 Media Server" product) supports these
requests, ***provided that*** the underlying file type can handle
them. In our current implementation, the following file types
support this:</div>
<div>- MP3 audio files</div>
<div>- MPEG-1or 2 audio/video Program Stream files (but not
reliably)</div>
<div>- MPEG Transport Stream files (provided that they each have an
'index file'; see the documentation)</div>
<div>- WAV audio files</div>
<div><br></div>
<div>For other file types (including MPEG-4 video files), our
implementation currently does *not* support seeking.</div><div>
<div><br></div>
<blockquote type="cite"><a href="http://www.myiptv.org/Articles/RTSP/tabid/72/Default.aspx" target="_blank">http://www.myiptv.org/Articles/RTSP/tabid/72/Default.aspx</a><br>
"The important bits of this command are Range and Scale. See I
said you would want to know the range. Range specifies from where and
how much of the content to play. 0- tells the server to start at the
beginning and play to the end but you could also start anywhere in the
file as we'll see in a minute or only play the first 5 minutes of
the content. It's up to you."</blockquote>
<div><br></div>
</div><div>You don't have to worry about the details of the RTSP protocol;
we implement all of this for you. Just use our "RTSPClient"
class, and pass the appropriate parameters (as noted above).</div>
<pre>--
</pre><font color="#888888">
<div><br>
Ross Finlayson<br>
Live Networks, Inc.<br>
<a href="http://www.live555.com/" target="_blank">http://www.live555.com/</a></div>
</font></div>
<br></div></div>_______________________________________________<br>
live-devel mailing list<br>
<a href="mailto:live-devel@lists.live555.com" target="_blank">live-devel@lists.live555.com</a><br>
<a href="http://lists.live555.com/mailman/listinfo/live-devel" target="_blank">http://lists.live555.com/mailman/listinfo/live-devel</a><br>
<br></blockquote></div><br>
</blockquote></div><br>