2017-03-03, 00:20
@ant0n1j4
Yep you're mis-reading that. XSqueeze, when acting as a local player, starts an external player process for the actual playback (i.e. squeezelite). If that fails to start, then XSqueeze can then not connect to it.
And, as per your SSH test, it IS failing to start. Because a device/resource is busy - i.e. something (most likley kodi) is hogging the audio device and squeezelite can't start. So you need to refer back to the wiki and your Kodi setup and work out why the device is being held on to by Kodi (e.g. keep audio device alive is set, or gui sounds are on etc)....
Yep you're mis-reading that. XSqueeze, when acting as a local player, starts an external player process for the actual playback (i.e. squeezelite). If that fails to start, then XSqueeze can then not connect to it.
And, as per your SSH test, it IS failing to start. Because a device/resource is busy - i.e. something (most likley kodi) is hogging the audio device and squeezelite can't start. So you need to refer back to the wiki and your Kodi setup and work out why the device is being held on to by Kodi (e.g. keep audio device alive is set, or gui sounds are on etc)....