[Announce] Squeezelite-X

[rgdawson]

Version 2.4.8

Turns out I broke some minor things in the last release, so 2.4.8 is on the way

Fixes:

• I broke logging. Not essential, but fixed in 2.4.8.
• Introduced a bug with Squeezelite startup. I was experimenting with creating the squeezelite process in a background thread and forgot to take it out in 2.4.7. This may cause you to see "Squeezelite failed to start" message" even though it actually started.
• Fixed a sizing problem with the mini-player.

R Greg Dawson

[left channel]

• Introduced a bug with Squeezelite startup. I was experimenting with creating the squeezelite process in a background thread and forgot to take it out in 2.4.7. This may cause you to see "Squeezelite failed to start" message" even though it actually started.

I saw that message, but just thought it was good proof that the startup player selection was working, because I wound up with the right player after the message went away. My selected player and top-listed player are the same, sorted to the top of all lists by putting a "." in front of the name. That seems to be working well, though I haven't yet thoroughly confused everything again by running Group players and such.

[left channel]

Now auto-updated to 2.4.8.

[cfuttrup]

Now auto-updated to 2.4.8.

Today, same here.

[dolodobendan]

Does SLX check for squeezelite instances running? Yesterday, the Surface featured three players in LMS (SLX was not even running, it must have crashed at some point. I guess that and restarting SLX created these additional players.)

[rgdawson]

Does SLX check for squeezelite instances running? Yesterday, the Surface featured three players in LMS (SLX was not even running, it must have crashed at some point. I guess that and restarting SLX created these additional players.)

No. It might be a good idea to look for squeezelite instances and give the user a chance to do something about it. I'll think about it.

R Greg Dawson

[dolodobendan]

No. It might be a good idea to look for squeezelite instances and give the user a chance to do something about it. I'll think about it.

R Greg Dawson

Thank you. One more thing I noticed before but forgot about: SLX doesn't work with the touch/virtual keyboard on the Surface. It pops up as it should, but typing (touch or mouse) doesn't produce any output in SLX. Not sure what it is, at least mouse works on my other notebook (doesn't have touch).

[rgdawson]

Thank you. One more thing I noticed before but forgot about: SLX doesn't work with the touch/virtual keyboard on the Surface. It pops up as it should, but typing (touch or mouse) doesn't produce any output in SLX. Not sure what it is, at least mouse works on my other notebook (doesn't have touch).

I don't have a touch screen or Surface, but when I bring up the virtual keyboard on my desktop and use mouse to click keys, it works. Not sure what I can do.

R Greg Dawson

[dolodobendan]

when I bring up the virtual keyboard on my desktop and use mouse to click keys, it works

That works on my "normal" notebook, too. I'll try some things to narrow it down.

[Maury]

Hello! I don't know if this question has been already addressed, but when I choose WASAPI in Player Output Device, no sound comes from the app, while it works fine with DirectSound. What could be causing this issue?

[rodlogic]

Player already in use - Choose another player

I have Squeezelite-X set to run on start up. Since 2.4.9 I now get th settings panel opening and the above error message.
If I kill the squeezelite-win.exe and hit Apply the App runs OK.

[rgdawson]

I have Squeezelite-X set to run on start up. Since 2.4.9 I now get th settings panel opening and the above error message.
If I kill the squeezelite-win.exe and hit Apply the App runs OK.

This is confusing to me. When SLX starts up, if enable player is set, before starting the player, SLX will query the server for already connected players and if it finds that there is a player already connected to the server with the same name, SLX will show you that message. So by your description, there actually is a squeezelite-win.exe instance running with the same name. Do you have another user logged in on your machine that is also running SLX and using the same player name? That could cause this. Otherwise, in a single user scenario, if SLX only allows a single instance per user, so squeezelite-win.exe should not already be running when SLX starts (but it apparently is?).

R Greg Dawson

[rgdawson]

Hello! I don't know if this question has been already addressed, but when I choose WASAPI in Player Output Device, no sound comes from the app, while it works fine with DirectSound. What could be causing this issue?

WASAPI configuration was a little tricky for me first time I tried it. I recall I had to go into the settings somewhere and make sure the data rate was set to 44100Hz instead of 48000Hz. As I recall, when I did that it started working. But this was a long time ago and my memory is vague. YMMV, but try that.

R Greg Dawson

[Maury]

WASAPI configuration was a little tricky for me first time I tried it. I recall I had to go into the settings somewhere and make sure the data rate was set to 44100Hz instead of 48000Hz. As I recall, when I did that it started working. But this was a long time ago and my memory is vague. YMMV, but try that.

R Greg Dawson

Thanks! Changing Windows's sample rate to 44100Hz fixed the issue. So now I should be getting bit perfect audio, am I correct?

[Stan Pulsar]

Hi there,

first, thanks for this great app, love it.

I'm having an issue though with media keys integration. I've browsed the thread a bit, but didn't find much relevant, except maybe that somewhere I think you wrote that if the keys were already registered by another software, SL-X wouldn't register them (not 100% sure now).

Actually, on my system, it seems they have been registered by "Media Player Classic" (MPC). This has an option to enable them, but strangely enough it says "not enabled" but MPC still responds to the keys.

Anyway, I don't need MPC to use the keys at all, but I'd really like SL-X to do so.

Any idea how I could force key registration ?

Using SL-X 2.4.9 on Windows 10 1809 (17763.615)