The VideoLAN Forums

I had the same problem - turned out to be Network Card drivers...

Cheers, Andy E.

...amazingly, when I started using VLC, I followed this process, and I found I could transcode and stream at 128kbps (terrible picture!) but nothing better. Turned out to be a Network Card driver problem. Just goes to show - take nothing for granted where computers (and video) are concerned!! Cheers...

I have done this on a Netgem i-player. Start an HTTP stream on the serving end and type http://server-ip:1234 into the web access page of the STB.
I am assuming here that the Pace STB can access URLs...

Cheers, 7&Y

Perhaps a little more information might assist the understanding

Real Inc tends to ask a lot of money for access to its codecs, which goes against the policy of making Videolan free and open for everyone.

Cheers, 7&Y

... a bit more info on this. On the PC which doesn't seem to be able to send the video quick enough, I changed the NIC for a Realtek 8139 and disabled the on-board one. The problem is still there, so I think it must be related to some settings within Windows. If I send from the PC that is OK, I can ...

...if you set up an http:// stream, then the address you type into the http box at both ends needs to be the exact address of the PC doing the sending. Personally, I've never got any of the other methods (UDP etc) to work

Cheers, 7&Y

...there's one thing that had me well confused for a little while. The docs give this strange IP address to illustrate how things work, and, unless you use exactly the same address, range and subnet, it won't work. It was a moment or two before I realised I actually have to use the real IP address e...

I'm also getting loads of these PTS errors when I stream from PC#1 to PC#2. Interestingly, if I stream the other way - PC#2 to PC#1, it is perfect! I can ramp up MPEG2 to max bitrate, and it still only uses less than 40% of my 100Mb LAN. PC#1 to PC#2 - if I use more than 128 bits/sec (!) it falls ov...