[Announce] Squeezelite-X

[whoareyou]

I'm pretty sure 2.3.3 will fix the issue. It is related to tasks going on in threads, where one piece of code is working with a list while it is being updated elsewhere. I think it was introduced in 2.3.0 when I eliminated a hidden main application window, which changed the order of certain startup code. My theory is that faster machines do not see the issue, but slower machines could, which is why I did not ever see it. I cringe knowing that others could be experiencing this and I would not even know about it, except for you letting me know, so I am grateful for that, thanks.

R Greg Dawson

Thanks. I'll let you know after I see the update.

Don't cringe over supporting a free app. I feel bad enough about asking for you take a look at this stuff

BTW - If this is the same issue I encountered on my desktop, that's my dev machine with 6 core i7, so it would have been just a matter of time before others reported the issue.

[whoareyou]

Thanks. I'll let you know after I see the update.

Don't cringe over supporting a free app. I feel bad enough about asking for you take a look at this stuff

BTW - If this is the same issue I encountered on my desktop, that's my dev machine with 6 core i7, so it would have been just a matter of time before others reported the issue.

Just installed the update:

Good news is that on the desktop I believe this completely resolves the issue I reported. App loads faster and the output device dropdown now works as expected.

On the tablets not so good news - The app crashes on loading with an Application error trying to read an address 00000004. Never gets to the splash screen. If there's any other information you'd like I can get it for you. Really not sure this is worth looking into any further. These are old tablets that are not truly windows 10 certified.
Thanks.

[dolodobendan]

On the (slow) Surface Go most of the symptoms I described earlier are back, too. When started, SLX sits in the tray as it should. Clicking it opens SLX, but then it closes almost immediately. The tray icon is gone, squeezelite-win and it's dependent conhost are still running in the background.

I tested it several times while writing this, and one time out of maybe five it did not crash. Maybe a timing issue again?

I will check my faster machines later.

Edit: No problems on the other machines.

[left channel]

I forced updates to 2.3.3 on my Win10 i7 laptop and Win10 Celeron streamer, and have experienced no problems. No Win tablets here.

[edwin2006]

I forced updates to 2.3.3 on my Win10 i7 laptop and Win10 Celeron streamer, and have experienced no problems. No Win tablets here.

How did you force the update for slx?

[whoareyou]

Just installed the update:

Good news is that on the desktop I believe this completely resolves the issue I reported. App loads faster and the output device dropdown now works as expected.

On the tablets not so good news - The app crashes on loading with an Application error trying to read an address 00000004. Never gets to the splash screen. If there's any other information you'd like I can get it for you. Really not sure this is worth looking into any further. These are old tablets that are not truly windows 10 certified.
Thanks.

Ok - no progress with the tablets. I tried a remote debug session with the tablet, but I couldn't figure out where it was blowing up. My assembly language is quite a bit out of practice.

More importantly, the Desktop has another issue related to the audio devices

Here's description of what I'm seeing:
On desktop , I primarily playback via a Bluetooth speaker, but I frequently turn off Bluetooth .

1) When Bluetooth is off and ...
2) The audio device is no longer present and ...
2) Start playback
3) Bad stuff happens

Squeezelite-x seems to select the next entry in the list.
I'm guessing that's what happens because the next entry in the list is an ASIO driver installed by JRiver Media Center. But this is not really even a valid audio device for playback.

What ends up happening is that Media Center launches repeatedly and ends up hanging my machine.

Now, I really don't think that should happen either, and I'll ask the JRiver folks about this, but I don't think this device should be a valid audio entry It's really a driver used by an audio device for playback.

When you bring up the list of audio devices for the computer via audio settings it doesn't appear, and I believe that is the correct behavior.

Hope this all made sense.

Thanks again


******************* Edit *********************
From Jriver site - This seems to be issue others have encountered between other apps and Jriver
They added an option to disable the ASIO driver.
That has fixed my issue.

https://yabb.jriver.com/interact/index.php?topic=83378.0

But, I'm still not sure why the ASIO ends up selected when Bluetooth is turned off. It never appears to become the default device.

[left channel]

How did you force the update for slx?

Search for "Store" and open the Microsoft Store.
At the upper right, click the three dots to open the See More menu.
Select "Downloads and updates".
Click the "Get Updates" button.

[rgdawson]

On the (slow) Surface Go most of the symptoms I described earlier are back, too. When started, SLX sits in the tray as it should. Clicking it opens SLX, but then it closes almost immediately. The tray icon is gone, squeezelite-win and it's dependent conhost are still running in the background.

I tested it several times while writing this, and one time out of maybe five it did not crash. Maybe a timing issue again?

I will check my faster machines later.

Edit: No problems on the other machines.

Oh Jeez, in fixing the output device init problem I re-introduced this issue. Fix next version. Sorry about that.

R Greg Dawson

[rgdawson]

Version 2.3.4 Submitted to Store

Changes:

• Fixed Startup crash on some machines [dolodobendan]
• Fixed problem with Output Device Selection where Select device exists, but elsewhere list has changed (Device unplugged/turned off) and wrong device could be selected [whoareyou]

R Greg Dawson

[dolodobendan]

Oh Jeez, in fixing the output device init problem I re-introduced this issue. Fix next version. Sorry about that.

R Greg Dawson

Thank you!

[dolodobendan]

Version 2.3.4 Submitted to Store

Changes:

• Fixed Startup crash on some machines [dolodobendan]
• Fixed problem with Output Device Selection where Select device exists, but elsewhere list has changed (Device unplugged/turned off) and wrong device could be selected [whoareyou]

R Greg Dawson

Unfortunately, the problem still persists.

[rgdawson]

Unfortunately, the problem still persists.

Your problem is that on the Surface Go, the application appears to start and you see icon in tray, but when you click on tray icon to open main window, the main window shows, but immediately goes away and leaves squeezelite-win.exe and its host window running, is that correct? Is behavior same no matter how long you wait to click icon after starting up app? What happens if "Run In Backround" is not enabled? Is your O/S on the Surface Go running that S-Mode?

R Greg Dawson

[whoareyou]

Windows Tablet Startup Crash - Fix

The startup crash on my tablets is caused by setting the screen resolution to 125%. Set the tablet's resolution to 100% and app starts up fine.

The desktop doesn't have this issue.

Thanks

[rgdawson]

The startup crash on my tablets is caused by setting the screen resolution to 125%. Set the tablet's resolution to 100% and app starts up fine.

The desktop doesn't have this issue.

Thanks

Thanks for this clue, obviously, a bug. Back when I had the hidden main window, handling hiDPI was more complicated than it otherwise would have been and I had code to handle all the various monitor scenarios. Now that I don't have the hidden main Window, a piece of this code remains that may be getting called too early, in this case now that the browser Window is created first. And I don't think I even need that code anymore, anyway. So I am investigating this and will have a fix.

R Greg Dawson

[dolodobendan]

Your problem is that on the Surface Go, the application appears to start and you see icon in tray, but when you click on tray icon to open main window, the main window shows, but immediately goes away and leaves squeezelite-win.exe and its host window running, is that correct?

It freezes for a second before it vanishes.

Event viewer, Application Error, ID 1000:

Name der fehlerhaften Anwendung: SqueezeliteX.exe, Version: 2.3.4.0, Zeitstempel: 0x5d14249b
Name des fehlerhaften Moduls: KERNELBASE.dll, Version: 10.0.18362.145, Zeitstempel: 0xf5733ace
Ausnahmecode: 0xc000041d
Fehleroffset: 0x001133d2
ID des fehlerhaften Prozesses: 0x1ee0
Startzeit der fehlerhaften Anwendung: 0x01d52de80a61ab07
Pfad der fehlerhaften Anwendung: C:\Program Files\WindowsApps\16237RGregDawson.Squeezelite-X_2.3.4.0_x86__qhedj8x0bjmhg\SqueezeliteX.exe
Pfad des fehlerhaften Moduls: C:\WINDOWS\System32\KERNELBASE.dll
Berichtskennung: 36f6ccbd-07fa-43ef-8837-caff29f1c7b2
Vollständiger Name des fehlerhaften Pakets: 16237RGregDawson.Squeezelite-X_2.3.4.0_x86__qhedj8x0bjmhg
Anwendungs-ID, die relativ zum fehlerhaften Paket ist: SqueezeliteX

(Sorry, this notebook has a German OS.)

Is behavior same no matter how long you wait to click icon after starting up app? What happens if "Run In Backround" is not enabled? Is your O/S on the Surface Go running that S-Mode?

To answer the three questions: Yes, the same, and no (Windows 10 Home #1903).