If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
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)
Windows will only allow a single application to register a hotkey. So, if when SLX attempts to register tone of the media keys as a hotkey, Windows will deny the request if another app has already registered it. So the only thing you can do is to avoid another app from registering the hot key by not running it, disabling that feature, or running SLX first.
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
This is a single user instance - the player name is only used on my latop with one user (me) I have noticed that this happens when I find the app has disappeared from the taskbar and thus I have starting it again (but I guess it hasn't exited cleanly and left the squeezelite-win.exe instance running). If I select exit to cleanly exit the app then the restart is fine. This seems to occur when the app has been running for a long time 12 hours + and may also be affected because my laptop goes into sleep mode. I will try and see if there is a pattern.
I have now opened up my laptop and the app has just winked out of existence (Squeezelite-X.exe(s) - BUT the Squeezelite-win.exe is still running - hence the message I get when I start up Squeezelite-X. No idea why this is happening - suspect it started with 2.4.9
Last edited by rodlogic; 2019-09-07, 09:56.
Reason: App Crash
Hi All, this has been probably asked before but I am unable to find the answer in the forum so I have to ask again.
I have installed Squeezelite-X from the Microsoft Store and now it starts running at every log on: how can I avoid this behaviour? I see no options in Squeezelite-X configuration page itself. Do I have to look for that in Windows 10 control panel or use a third party app like Autoruns from Microsoft/Sysinternals team to stop it running at logon?
Hi All, this has been probably asked before but I am unable to find the answer in the forum so I have to ask again.
I have installed Squeezelite-X from the Microsoft Store and now it starts running at every log on: how can I avoid this behaviour? I see no options in Squeezelite-X configuration page itself. Do I have to look for that in Windows 10 control panel or use a third party app like Autoruns from Microsoft/Sysinternals team to stop it running at logon?
Thanx for any support, Paolo.
Run task manager, click on startup tab, select Squeezelite-X and disable. I would like this to be configurable inside the app, but Windows Store apps have certain limitations.
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.
If you start squeezelite on a wasapi device and add -a :1 to the command line options, there is no need to modify the sample rate in control panel, provided allow exclusive device access is enabled for it.
If you start squeezelite on a wasapi device and add -a :1 to the command line options, there is no need to modify the sample rate in control panel, provided allow exclusive device access is enabled for it.
So with WASAPI exclusive mode enabled, I should be getting bit perfect audio from Squeezelite-X, right?
So with WASAPI exclusive mode enabled, I should be getting bit perfect audio from Squeezelite-X, right?
Well, Squeezelite-X just uses squeezelite under the covers, so whatever it does is what you get. I'm not sure what "bit-perfect" is, so I'll let someone smarter than me answer that.
If you start squeezelite on a wasapi device and add -a :1 to the command line options, there is no need to modify the sample rate in control panel, provided allow exclusive device access is enabled for it.
I never really mess much with some of the more advanced squeezelite settings, but now I remember this discussion from back when you enabled exclusive mode. When I tried "-a :1" I got no sound unless I also specify sampling format using "-a <f>", where <f> = 16|24|32. But I have little idea of what is going on with these settings.
R Greg Dawson
Last edited by rgdawson; 2019-09-07, 21:38.
Reason: spelling
I rewrote several sections of the code (involving threading) in an effort to solve an occasional issue where the browser could fail to load when changing skins or even on startup where the skin was changing simultaneously with the window resizing.
Rewrote the logging functions. Before, if a logging function failed in a thread it could crash the app.
Rewrote Javascript handling code and fixed area that handles when a Javascript function fails. Before, if a Javascript function failed, all future Javascript calls would fail with Javascript Busy. SLX uses Javascript extensions to read/write to Material Skin's localStorage, in order to persist localStorage while clearing cache between sessions and when switching servers.
Mini player is zoomed at 90% of the main window zoom setting to make it more mini.
Unfortunately, the Windows operating system does not have mouse wheel events for tray icons, so this is not possible.
That's fair enough then! I suppose that's also why Microsoft haven't implemented it in their volume control, though you can never be sure with some of their odd design decisions.
That's fair enough then! I suppose that's also why Microsoft haven't implemented it in their volume control, though you can never be sure with some of their odd design decisions.
On Windows 10 with my (Logitech) mice, on all my PCs clicking on the speaker icon and using the wheel works fine, unless you mean elsewhere?
We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.
By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.
Comment