The problem of mplayer stopping after 20 mins with bandwidth is related to TCP and the "Receive Window" and not the processor type.
The "bandwidth option" is supposed to mimic the RealPlayer Turboplay option but i think there is a problem. Basically the bandwidth option enabled mplayer to receive a lot of data as fast as possible but the problem is the mplayer only processes it in RealTime - what happens is the TCP connected thinks some of the data downloaded has been lost as it is only acknowledged when it is played and this can take minutes. When this happens TCP reset the link. I think one way to resolve the issue is to get the right value for bandwidth depending on the user's broadband connection. Raising a bug in mplayer list is not very effective unless it is in a popular area such as DVD playback. The "garbled audio" bug was reported for at least 6 months until I decided to track it down and pinpoint the problem - then the code was changed. I reckon I'll have to the same for this bug ( as well as why R4 LW doesn't work). On your VIA system - are you running Windows ? Have you tweaked registry values to improved download or has an app run to optimise network ? What speed & type of broadband connection do you have ? -- bpa ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=27993 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
