Ok.<br><br>And you are right, the easiest way for you (and for the client) is the http mode.<br><br>Regards,<br>Antoine<br><br><div><span class="gmail_quote">On 3/28/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;">Antoine Roussel wrote:<br>> It depends of your network and of your file. If i remember well, Mpeg
<br>> 4 bitrate may vary between few kbit/s and 4Mbit/s.<br>><br>> So, on a 100mbit LAN, you don't really need to transcode it. On a wifi<br>> 802.11b network, you should reduce the bitrate...<br>><br>> Concerning the udp, any computer on the same subnet could pick up the
<br>> flux. If you have to change of subnet, you need to route the udp port<br>> through you router.<br><br><br>Thanks for those precisions.<br><br>The problem with UDP unicast is that the client has no control over the
<br>flux. I want the server to stream a file from any time point (which can<br>been done with the --start-time switch), but I also want the client to<br>be able to seek the file. When I start the udp server, there is no<br>
problem with UDP unicast. However, when the client starts and reads the<br>udp stream, he cannot restart to the beginning or seek in the file.<br><br>What I would like, is that the client get control using the slider, as<br>
it is the case when the file is sent over http, without any streaming. I<br>thought about writing a small client (maybe http client) to send the<br>"play", "stop" or "seek" control commands to the rtcp server, through
<br>the telnet or http interface of VLM.<br><br>Regards,<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>