[Announce] Squeezelite-X

[rodlogic]

Not sure if that is it. I cannot reproduce the issue under any circumstances on any of my machines. My theory is that something is happening in an unusual order on startup where multiple threads are starting up and something is happening unexpectedly early or late based on the machine, configuration, and activity. I am carefully analyzing the code and investigating some theories, but nothing concrete yet. Expect to see some updates soon.

R Greg Dawson

I have unistalled the Win10 App and installed .19 from your Onedrive x86 version. The same error occurs with this version.
I also noticed that squeezelite-win.exe loads then exits whilst the squeezelitex.exe sits in memory not doing anything - the situation seems to be worse :-(

I have reinstalled the Win10 app now - but again squeezelite-win.exe loads and exits - very wierd.

[rgdawson]

I have unistalled the Win10 App and installed .19 from your Onedrive x86 version. The same error occurs with this version.
I also noticed that squeezelite-win.exe loads then exits whilst the squeezelitex.exe sits in memory not doing anything - the situation seems to be worse :-(

I have reinstalled the Win10 app now - but again squeezelite-win.exe loads and exits - very wierd.

rodlogic, Obviously something is going weird on your system. What I think you are saying is as follows:

You see an Access Violation on startup BEFORE the tray icon appears.
Then, you see the tray icon and you can get to the settings and see the Application Log.
The application log indicates that something went wrong after "Read Settings from Registry"
If you press "Apply" here, the icon turn blue and things work.

Can you send me what the application log says?

R Greg Dawson

[rodlogic]

rodlogic, Obviously something is going weird on your system. What I think you are saying is as follows:

You see an Access Violation on startup BEFORE the tray icon appears.
Then, you see the tray icon and you can get to the settings and see the Application Log.
The application log indicates that something went wrong after "Read Settings from Registry"
If you press "Apply" here, the icon turn blue and things work.

Can you send me what the application log says?

R Greg Dawson

This is a link to a screen capture video of what is happening.

https://drive.google.com/file/d/1D_u...ew?usp=sharing

You can see the app triggerred, The Access Violation Notice at the same time Squeezelite-win and Squeezelitex load, then Squeezelite-win unloads and only Sqeezelitex remains. Also Squeezelitex does not open from the Icon.

I have investigated further - I have changed the permissions on the c:\program files\windowsapps folder to gain access to your app package - if I launch squeezelite-win.exe from this directory and wait for a minute I can then launch squeezelitex.exe without the access violation. Of course I then have 2 x squeezelite-win.exe running - but no access violation window !

I can then kill the first squeezelite-win.exe and the app continues as normal.

I wonder if there is a race condition here where squeezelite-win.exe needs to load first before squeezelitex.exe communicates with it
I have attached the app log as well

?Squeezelitex Log.txt

[Dentaku]

Same error here but now it works again:
I simply used the repair option under advanced options in windows settings. After that Squeezelite-X started without the error.

[rgdawson]

I have unistalled the Win10 App and installed .19 from your Onedrive x86 version. The same error occurs with this version.
I also noticed that squeezelite-win.exe loads then exits whilst the squeezelitex.exe sits in memory not doing anything - the situation seems to be worse :-(

I have reinstalled the Win10 app now - but again squeezelite-win.exe loads and exits - very wierd.

I have noticed that if I remote desktop into my home machine and I configure Squeezelite-X to use a specific output device, "Remote Audio [Windows WASAPI]"), then disconnecting the remote session (while not signing out) causes squeezelite-win.exe to terminate. It apparently does not like its WASAPI output device disappearing on it. Interestingly, if I select "Remote Audio [Windows DirectSound], squeezelite-win.exe does not terminate when I disconnect the remote session. I'm wondering if your startup issue is related to output device. Do you have a specific output device selected, or are you using default. Do you get the error with output device = default?

[Edit...] Running some more experiments, I have observed that if there is something wrong with the output device (not ready, not there), squeezelite-win.exe will start OK, then terminate itself. I had code to capture that case, but was only giving a certain amount of time to detect it. My code would check and make sure squeezelite-win.exe was still running after 1 second and assume all was good. But my experimentation has found that sometimes it takes longer than that. So I am thinking the behavior you saw where squeezelite-win.exe terminated was such a case and that you have an output device other than default selected, just a guess. I'm working on better code to handle this case without causing too much delay in startup.

R Greg Dawson

[rgdawson]

Version 1.4.0

Version 1.4.0 is coming soon that should fix the startup issues a few here have seen.

R Greg Dawson

[rodlogic]

I have noticed that if I remote desktop into my home machine and I configure Squeezelite-X to use a specific output device, "Remote Audio [Windows WASAPI]"), then disconnecting the remote session (while not signing out) causes squeezelite-win.exe to terminate. It apparently does not like its WASAPI output device disappearing on it. Interestingly, if I select "Remote Audio [Windows DirectSound], squeezelite-win.exe does not terminate when I disconnect the remote session. I'm wondering if your startup issue is related to output device. Do you have a specific output device selected, or are you using default. Do you get the error with output device = default?

[Edit...] Running some more experiments, I have observed that if there is something wrong with the output device (not ready, not there), squeezelite-win.exe will start OK, then terminate itself. I had code to capture that case, but was only giving a certain amount of time to detect it. My code would check and make sure squeezelite-win.exe was still running after 1 second and assume all was good. But my experimentation has found that sometimes it takes longer than that. So I am thinking the behavior you saw where squeezelite-win.exe terminated was such a case and that you have an output device other than default selected, just a guess. I'm working on better code to handle this case without causing too much delay in startup.

R Greg Dawson

I am afraid that my sound output is set as Default - never changed that parameter.
I have tried the repair option which has fixed the start up issue - I will monitor the situation.

many thanks

[rgdawson]

I am afraid that my sound output is set as Default - never changed that parameter.
I have tried the repair option which has fixed the start up issue - I will monitor the situation.

many thanks

OK. Well I could sorta reproduce a similar issue if I intentionally selected output devices which were not ready or did not exist. In fixing that, I have made SLX startup more tolerant of squeezelite-win.exe startup issues. So maybe your issue will be fixed in any case in version 1.4.0.

R Greg Dawson

[left channel]

Updated to version 1.4.0 (as announced in Greg's post number 140 ...just sayin').

And as no good deed goes unpunished, now my mini player is blank:

[rgdawson]

Updated to version 1.4.0 (as announced in Greg's post number 140 ...just sayin').

And as no good deed goes unpunished, now my mini player is blank:

I'm looking into it. Can't reproduce it yet. Anyone else seeing this?

R Greg Dawson

[left channel]

Thanks Greg. I'm seeing it on two laptops, with Windows 10 Pro 1803 and Windows 10 Home 1709.

[bobertuk]

I'm looking into it. Can't reproduce it yet. Anyone else seeing this?

R Greg Dawson

Yes, exactly the same issue on updating to v1.4.0. Don't use the mini player myself but just checked it after seeing the post.

Bob

[rgdawson]

Yes, exactly the same issue on updating to v1.4.0. Don't use the mini player myself but just checked it after seeing the post.

Bob

OK guys, sorry about that. I have made a change that might fix it, but since I can't reproduce it, I don't know for sure. Perhaps something changed when I updated the embedded browser library. This all must have to do with timing and the browser component running in a separate thread. Anyway, 1.4.2, which I will submit shortly, hopefully will fix this. (There is no 1.4.1).

R Greg Dawson

[Jeff07971]

Hi Greg,

I'm afraid I'm reporting a bug ! (I think)

Squeezelite-X refreshes the whole screen (including mini) every 5 seconds, unfortunately its really annoying and have to minimise it

Was running 1.4.0 and seems to be after Windows 10 Pro x64 1803 update, Now have 1.4.2 and is the same.

Have tried on two seperate systems with two separate LMS servers

Jeff

[rgdawson]

Hi Greg,

I'm afraid I'm reporting a bug ! (I think)

Squeezelite-X refreshes the whole screen (including mini) every 5 seconds, unfortunately its really annoying and have to minimise it

Was running 1.4.0 and seems to be after Windows 10 Pro x64 1803 update, Now have 1.4.2 and is the same.

Have tried on two seperate systems with two separate LMS servers

Jeff

Are you saying the SLX browser window (including the mini-browser window is refreshing/re-rendering every 5 seconds? What version of LMS are you running? Nightly builds? I think I saw some weird stuff with the nightly LMS around that time and I went back to stable 7.9.1-1522157629 (Mar 30 2018). SLX does not do anything on 5 second intervals. It does check that the server is still there every 8 seconds. Does it behave this way with a regular browser? I have a spare R-Pi, so I guess what I'll do is install the latest nightly LMS on it and see what it does and try and remember why uninstalled the nightly a month or so ago. Can you check and see if your issue is on a 5 second interval or an 8 second interval just so I know in case something I am doing is causing this.

R Greg Dawson