[Announce] Squeezelite-X

[Rasemuck]

...does anybody know where to find the option "play from RAM drive" at Squeezelite-X? Can't find it anywhere!





Regards

Martin

[microspock]

Does the server combo box in settings show you your server(s) or does it say none discovered?

None discoverered

but i've understand the problem, i use tailscale, there was an update of windows app, and even not activated it messes up the setting.

[rgdawson]

Been using your app for a while but today I added a Sound Blaster Audigy FX v2 and now the app errors on startup:


After hitting ok, the configuration screen comes up, but I am unable to populate anything and have to end the app in the task manger or in the task bar. I did download prior versions, tried a few but same issue.

I don't know what would cause this and I don't have much to go on. Maybe we can get some log info. Run RegEdit and go to the Squeezelite-X area. (Computer\HKEY_CURRENT_USER\Software\Squeezelite-X). Set EnableDebugLogging to 1 and EnableLogToFile to 1. Start Squeezelite-X. That should create a log file on your desktop and lets see what that says. Thanks.

R Greg Dawson

[rgdawson]

Not the same problem but my problem start today, my lms server is unfindable (i can access it normaly in chrome). I wonder if the last windows 11 update i made yesterday is guilty. i read somewhere it is a big update.

Edit: using IP of the server works, but the auto discover not.

Does the server combo box in settings show you your server(s) or does it say none discovered?

[microspock]

Been using your app for a while but today I added a Sound Blaster Audigy FX v2 and now the app errors on startup: After hitting ok, the configuration screen comes up, but I am unable to populate anything and have to end the app in the task manger or in the task bar. I did download prior versions, tried a few but same issue.

Not the same problem but my problem start today, my lms server is unfindable (i can access it normaly in chrome). I wonder if the last windows 11 update i made yesterday is guilty. i read somewhere it is a big update.

Edit: using IP of the server works, but the auto discover not.

[Varvous]

Been using your app for a while but today I added a Sound Blaster Audigy FX v2 and now the app errors on startup:


After hitting ok, the configuration screen comes up, but I am unable to populate anything and have to end the app in the task manger or in the task bar. I did download prior versions, tried a few but same issue.

[rgdawson]

Version 2.11.60

I submitted an update.

Changes

• I replaced the XML library I was using (related to the Denon AVR control feature). It had some issues with oddly formed XML files and I got tired of working around them. This fixes some issues I was seeing consistently discovering Denon AVRs on the network.

R Greg Dawson

[rgdawson]

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

Thanks for letting me know!

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]

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

[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

[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.

[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

[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]

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