[Announce] Squeezelite-X

[gorman]

Melodeon? https://forums.slimdevices.com/forum...ounce-melodeon Does not do starting/stopping of squeezelite as I was not sure of the necessity of that, but I maty add someday.

Thanks for this! I replied on your thread.

[gorman]

gorman, there is SqueezePlay for Linux, but you probably knew that already. SqueezePlay has a user interface that is similar to the Squeezebox Touch and Jivelite. You will need to create your own desktop shortcut, but that is an easy job.

Thanks for the suggestion. I hadn't thought about Squezeplay, although I was aware of it. I prefer Material Skin, but thanks a lot anyway. :-)

Also, sorry for the offtopic.

[rgdawson]

Hi. I am new to Squeezelite-X, which I just installed on my Windows 11 machine from the Microsoft Store.

I am getting the error message: "Unable to confirm squeezelite player Squeezelite-X. Check port 3483 is open."



SLX apparently finds my LMS server; it shows the right host name. Also, Squeezelite-X appears in the list of players on LMS. (That is, on the LMS Status page, SLX is listed as a player under "Player Information.")

What am I supposed to do? This is a firewall issue? I'm using Windows Defender. Squeezelite-X appears in the list of allowed apps in Windows Defender. (If there's a way to open a specific port, I can't find it.) Turning off Windows Defender does not make the error go away.

One possible wrinkle is that my LMS is piCorePlayer running on a Raspberry Pi. It has its own version of squeezelite, by which I run a different player.

-David

I was just seeing spaces in your host name which is not really valid, so that may be the issue. Try replacing the host name with the IP address of your LMS server.

R G Dawson

[dpotts]

I was just seeing spaces in your host name which is not really valid, so that may be the issue. Try replacing the host name with the IP address of your LMS server.

R G Dawson

No, I tried the IP address and also the server name, but I still get the error.

I found a command that gives the port usage on the server:



Among the "foreign addresses," 192.168.2.182 is my computer where SLX is running; 192.168.2.158 is the NAS that holds the music files; and 192.168.2.219 is a Squeezebox Duet player. (Obviously, 192.168.2.30 is the server.)

Does this help? It looks like port 3483 is being used as it should. But then why I am having this problem?

-David

[rgdawson]

No, I tried the IP address and also the server name, but I still get the error.

I found a command that gives the port usage on the server:

Among the "foreign addresses," 192.168.2.182 is my computer where SLX is running; 192.168.2.158 is the NAS that holds the music files; and 192.168.2.219 is a Squeezebox Duet player. (Obviously, 192.168.2.30 is the server.)

Does this help? It looks like port 3483 is being used as it should. But then why I am having this problem?

-David

This message is triggered when SLX launches squeezelite successfully (it does not abort) yet SLX does not get a 'play connect/player reconnect' message from LMS server (~6 seconds wait). Time to look at some log data. In Advanced Settings, Enable "Advanced Options", then "Log Level = Debug" and "Log To File", then restart. This will create a log file on your desktop. Let's look at that.

Judging from the that console window It looks like you are running LMS on PiCorePlayer (hostname "Euclid"?, so where does "Pottsworld Audio Lib..." come from?) and the music files are on another server (NAS). If so, this is very similar to my setup.

(Although maybe skeptical about that hostname "Euclid" vs "Pottsworld Audio Lib..." not being valid and what the effects of that could be, I'll assume that is not the issue for now since you got same results with IP Address entered into SLX.) I might be able to learn more from the log file.

R Greg Dawson

[dpotts]

This message is triggered when SLX launches squeezelite successfully (it does not abort) yet SLX does not get a 'play connect/player reconnect' message from LMS server (~6 seconds wait). Time to look at some log data. In Advanced Settings, Enable "Advanced Options", then "Log Level = Debug" and "Log To File", then restart. This will create a log file on your desktop. Let's look at that.

Judging from the that console window It looks like you are running LMS on PiCorePlayer (hostname "Euclid"?, so where does "Pottsworld Audio Lib..." come from?) and the music files are on another server (NAS). If so, this is very similar to my setup.

(Although maybe skeptical about that hostname "Euclid" vs "Pottsworld Audio Lib..." not being valid and what the effects of that could be, I'll assume that is not the issue for now since you got same results with IP Address entered into SLX.) I might be able to learn more from the log file.

R Greg Dawson

Thanks for your reply. I attached the log file.

Yes, LMS runs on piCorePlayer, which has Euclid as the hostname. "Pottsworld Audio Library" is the "Media Library Name" in LMS. And yes, the music files are on a separate NAS.

I am ashamed to admit that I only just now discovered that SLX is actually working! That is, I can play songs through the web browser interface with SLX as the player once it is running on my computer. I never tried it because of the error message. (The error message is still there, it just doesn't seem to matter.)

I see that the log reports that "Wait for server to confirm player 'Squeezelite-X'" times out. Could it just be that the server is slow to respond?

-David

[rgdawson]

Thanks for your reply. I attached the log file.

Yes, LMS runs on piCorePlayer, which has Euclid as the hostname. "Pottsworld Audio Library" is the "Media Library Name" in LMS. And yes, the music files are on a separate NAS.

I am ashamed to admit that I only just now discovered that SLX is actually working! That is, I can play songs through the web browser interface with SLX as the player once it is running on my computer. I never tried it because of the error message. (The error message is still there, it just doesn't seem to matter.)

I see that the log reports that "Wait for server to confirm player 'Squeezelite-X'" times out. Could it just be that the server is slow to respond?

-David

Took a look at the log file. It appears that things are working somewhat correctly just very slowly, It appears the squeezelite gets launched correctly, but SLX does not get a message from the LMS server that it has connected for 28.4 seconds. This is far outside the maximum SLX will wait before giving up, which is about 16 seconds. (For comparison, on my system right now, this time is 0.3 seconds.) So, something weird is going on there. Sometimes, the sound card can cause delays in squeezelite connecting. Next is to experiment with different output device/protocol selections and see if we can correlate to a specific device. Try Primary Sound Driver [Windows DirectSound] and Echo Canceling SpeakerPhone [WASAPI], for example.

R Greg Dawson

[dpotts]

Took a look at the log file. It appears that things are working somewhat correctly just very slowly, It appears the squeezelite gets launched correctly, but SLX does not get a message from the LMS server that it has connected for 28.4 seconds. This is far outside the maximum SLX will wait before giving up, which is about 16 seconds. (For comparison, on my system right now, this time is 0.3 seconds.) So, something weird is going on there. Sometimes, the sound card can cause delays in squeezelite connecting. Next is to experiment with different output device/protocol selections and see if we can correlate to a specific device. Try Primary Sound Driver [Windows DirectSound] and Echo Canceling SpeakerPhone [WASAPI], for example.

R Greg Dawson

I usually have my computer docked to a monitor (HP E243m) with its own sound options. Here is a screenshot of the "Player Output Device" options:



I have indicated the outcome of each in yellow text to the left.

• "Unable to confirm" means I get the message from SLX that the player can't be confirmed, "check port 3483 is open."
• "Aborts" means I get the message "Squeezelite player aborted. Check parameters."
• "1 second loop" means that SLX seems to start properly, no error message, and player controls appear along with tracks in the queue, etc. However, it won't really play. If I click play, it starts for 1 second, then returns to 0, starts for 1 second, returns to 0, etc. (And it only seems to start. There's no sound.)
• "Plays" means hallelujah, SLX starts properly and plays music.

So, clearly, "Windows DirectSound"—whatever that is—is the answer for me. Too bad it doesn't work with the Echo Cancelling Speakerphone, which is usually my best sound option.

Do you have any idea what is going on here?

-David

[rgdawson]

I usually have my computer docked to a monitor (HP E243m) with its own sound options. Here is a screenshot of the "Player Output Device" options:



I have indicated the outcome of each in yellow text to the left.

• "Unable to confirm" means I get the message from SLX that the player can't be confirmed, "check port 3483 is open."
• "Aborts" means I get the message "Squeezelite player aborted. Check parameters."
• "1 second loop" means that SLX seems to start properly, no error message, and player controls appear along with tracks in the queue, etc. However, it won't really play. If I click play, it starts for 1 second, then returns to 0, starts for 1 second, returns to 0, etc. (And it only seems to start. There's no sound.)
• "Plays" means hallelujah, SLX starts properly and plays music.

So, clearly, "Windows DirectSound"—whatever that is—is the answer for me. Too bad it doesn't work with the Echo Cancelling Speakerphone, which is usually my best sound option.

Do you have any idea what is going on here?

-David

Not precisely, just that squeezelite has trouble with directly accessing certain soundcard / API combinations. Windows DirectSound is Windows' the sound API that provides an interface between applications and the sound card driver. In other words, you are going through an OS layer and the OS is talking to the soundcard (which I think is a good thing, as it seems most reliable). I generally recommend using Primary Sound Driver [Windows DirectSound], which, basically is saying, "use what you have selected in Windows", configure Windows O/S output device to be "Echo Cancelling Speakerphone" or whatever you want your output device to be.

Are you able to set the Windows Sound Device to the speakerphone? (If so, then do that, then select Primary Sound Driver in SLX).



RGDawson

[dpotts]

Not precisely, just that squeezelite has trouble with directly accessing certain soundcard / API combinations. Windows DirectSound is Windows' the sound API that provides an interface between applications and the sound card driver. In other words, you are going through an OS layer and the OS is talking to the soundcard (which I think is a good thing, as it seems most reliable). I generally recommend using Primary Sound Driver [Windows DirectSound], which, basically is saying, "use what you have selected in Windows", configure Windows O/S output device to be "Echo Cancelling Speakerphone" or whatever you want your output device to be.

Are you able to set the Windows Sound Device to the speakerphone? (If so, then do that, then select Primary Sound Driver in SLX).



RGDawson

Yes, I had set it up that way already, actually.

Thanks for your assistance with this!

-David

[microspock]

Hi !

I have a character encoding problem i think, i've found in this topic that it already happened before :

ok on in the playlist




Not ok in the taskbar




And in the settings



Anyway, thanks for this app, this is exaclty what i need for my setup.

[rgdawson]

Hi !

I have a character encoding problem i think, i've found in this topic that it already happened before :

ok on in the playlist




Not ok in the taskbar




And in the settings



Anyway, thanks for this app, this is exaclty what i need for my setup.

Ha, I just logged in to post that I submitted a new version that fixes character encoding for output devices. A few days ago, I decided to install a non-english language pack and see what SLX looks like. I chose French, and I saw exactly what you posted. Anyway, 2.11.59 fixes that for the appearance of the output devices.

Now that you have pointed it out, I'll also go and fix the taskbar appearance. I didn't notice that, but should be an easy fix.

Thanks for letting me know.

[EDIT]: I was able to cancel/resubmit submission to MS Store to include further fix for character encoding in taskbar.

R Greg Dawson

[rgdawson]

Version Update: 2.11.59

I have submitted version update to the MS Store and the OneDrive location. Might take a day or two to publish on the store.

Changes:

• Fix character encoding issue as described by microspock above.
• Changed error message for when squeezelite fails to run or aborts. It used to say "Check squeezelite parameters.", now it says "Enable squeezelite debugging for details".

R Greg Dawson

[microspock]

Version Update: 2.11.59

I have submitted version update to the MS Store and the OneDrive location. Might take a day or two to publish on the store.

Changes:

• Fix character encoding issue as described by microspock above.
• Changed error message for when squeezelite fails to run or aborts. It used to say "Check squeezelite parameters.", now it says "Enable squeezelite debugging for details".

R Greg Dawson

MS Store version published, everything is back to normal, perfect ! thx

[rgdawson]

MS Store version published, everything is back to normal, perfect ! thx

Thanks for letting me know!

R Greg Dawson