Just looking at code a look at s.cpp - is musicSocket open as Blocking or non-Blocking ?
If opened as Blocking then possibly the chunkiness of buffers which do not align with how data is consumed by the player may end up with player having too few bytes in buffer. The LMS way to handling streaming audio is to use non-Blocking socket and then write as much data as possible until a EWOULDBLOCK is returned (i.e. do not sleep on notional internal buffer boundaries - replenish instead) - sleep when output buffers are all full. The Sleep can then be at least 200ms. 16ms seems to be too small. If I can I understand the dynamics of why.csv - I'll see if it sheds light. ------------------------------------------------------------------------ bpa's Profile: http://forums.slimdevices.com/member.php?userid=1806 View this thread: http://forums.slimdevices.com/showthread.php?t=110986 _______________________________________________ unix mailing list unix@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/unix
