Here's a visualization of the output underrun, the pause, and resume:
36848 I was wondering why this might be Windows-specific. A total shot in the dark, but any chance it has to do with differences with Windows sockets? > > Under BSD Unixes, if the remote peer closes its connection and your > program is blocking on recv(), you will get a 0 back from recv(). > Winsock behaves the same way, except that it can also return -1, with > WSAGetLastError() returning WSAECONNRESET, WSAECONNABORTED or > WSAESHUTDOWN, to signal the detectable flavors of abnormal > disconnections. > From: https://tangentsoft.net/wskfaq/articles/bsd-compatibility.html A couple other references: https://docs.microsoft.com/en-us/windows/win32/winsock/porting-socket-applications-to-winsock https://docs.microsoft.com/en-us/windows/win32/winsock/return-values-on-function-failure-2 Sorry if that's something you're already aware of. And thank you again! +-------------------------------------------------------------------+ |Filename: 2022-01-15_squeezelite-playback-interruption-visualization.png| |Download: http://forums.slimdevices.com/attachment.php?attachmentid=36848| +-------------------------------------------------------------------+ ------------------------------------------------------------------------ thickasabrick's Profile: http://forums.slimdevices.com/member.php?userid=72476 View this thread: http://forums.slimdevices.com/showthread.php?t=114661 _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
