Hi,<br><br>if i understand well, in the first case, you don't use any "video server", just a http server. In the second case, you use a "video server".<br><br>So, if your network is enough fast, you can play your movie directly from the http link.
<br><br>Otherwise, you have to transcode your source and use a server.<br><br>With your first solution, you use more network resources, with the second one, you use more computer resources.<br><br>Bye,<br>Antoine<br><br>PS : if your are on a local network, you should try UDP unicast.
<br><br><div><span class="gmail_quote">On 3/24/06, <b class="gmail_sendername">Zeb</b> <<a href="mailto:zeb@zebulon.org.uk">zeb@zebulon.org.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi,<br><br>I was trying to setup a client/server solution in order to be able to<br>watch a video file over the network using random access, and thanks to<br>some help from the forum, I could experiment two solutions:<br>
- the simple solution was client-side: to use the --start-time option<br>with VLC player, using the HTTP address of the video file.<br>- I found another more complicated solution, but server-side: setting up<br>with VLM a RTSP server, and "pilot" the streaming of the file using VLM
<br>commands play and seek through the telnet interface.<br><br>Is there a reason to prefer one solution over another one ? The first<br>one is easier, however, is RTSP better if there is a higher charge ? Is<br>there a possibility to send commands using the GUI (for example, the
<br>time slider in the VLC GUI would automatically send seek commands) ?<br><br>Thanks,<br>Eric<br><br>--<br>This is the streaming mailing-list, see <a href="http://www.videolan.org/streaming/">http://www.videolan.org/streaming/
</a><br>To unsubscribe, please read <a href="http://www.videolan.org/support/lists.html">http://www.videolan.org/support/lists.html</a><br><br></blockquote></div><br>