Triode wrote: > Try adjusting the server parameters for the player on the server > settings -> player -> synchronize web page. (I think the player audio > delay may help)
thanks for that. I've tried those settings for both the audio group (apart from the Android device) and the reverse - it just seems to increase the latency - and makes the SqueezePlayer client start even earlier than the others. It's strange as on a Spotify track, the players start to all sync ok within the first 10 seconds of the track (after skipping to the next track). I guess it's because they start out of sync by 40ms and then try and re-sync back. It must be the additional buffer that VMware is creating as part of the virtual sound card architecture that is causing the issue here. On the following track on a Spotify playlist, the players again start out of sync (it sounds as if the droid SqueezePlayer is starting 40ms before the rest of the audio group). Is the issue here an underlying issue with the Squeeze sync protocol not correctly dealing with fixed audio latency caused by the vmware buffering? I have the minimum sync adjustment set to 10ms if that makes a difference (I don't seem to be able to set it to less than this). ------------------------------------------------------------------------ ashleyw's Profile: http://forums.slimdevices.com/member.php?userid=58923 View this thread: http://forums.slimdevices.com/showthread.php?t=97046 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
