OK, bitrate limiting OFF is fine. If it's just iPeng as a player (not the SBs), the I really believe it's the router issue. What happens is this: iPeng's player (not iPeng as a remote) has two connections to the server, one for the actual music and one for control of the player (the server has the control authority). There is a problem with some routers (probably a chipset incompatibility issue with what is being used in the iThingies) that makes the control connection actually break down (no data is being sent anymore) without the device noticing (the connection stays open and just doesn't send or receive data anymore). This causes the symptoms you describe.
The problem for iPeng is that it is hard to recover from this. It's not a problem for iPeng's remote control connections and also not a problem for the stream itself, these connections get shut down and re-established frequently. However, it's harder to do this with the control connection. The issue here is that as soon as the connection is being shut down and re-opened by the client (iPeng), the server will stop and restart the current track from the beginning. So just letting it run into a timeout and re-opening it if there is no data coming in has the unfortunate side-effect that it will sometimes stop and restart tracks even with a perfectly good connection that just didn't see any data for a while, for example because the server is busy - this often happens in transcoding environments. All the workarounds we have created for the router issue so far made playback less stable for all other users which is not a good solution. ------------------------------------------------------------------------ pippin's Profile: http://forums.slimdevices.com/member.php?userid=13777 View this thread: http://forums.slimdevices.com/showthread.php?t=51929 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
