Skip to content
This repository has been archived by the owner on Feb 2, 2023. It is now read-only.

Settings not being saved. #94

Closed
Bas950 opened this issue Sep 1, 2018 · 6 comments
Closed

Settings not being saved. #94

Bas950 opened this issue Sep 1, 2018 · 6 comments

Comments

@Bas950
Copy link

Bas950 commented Sep 1, 2018

My settings are not being saved if I restart toastify or my pc.
The key settings are being saved but enable or disable the setting doesn't work.

Also Volume up and down isn't working but that might be due to the settings not being saved the right way.

@aleab
Copy link
Owner

aleab commented Sep 1, 2018

Volume hotkeys work fine on my end.
Everything else is a duplicate of #93.

@aleab
Copy link
Owner

aleab commented Sep 3, 2018

Fixed in the latest release: v1.10.12.

@MBS17
Copy link

MBS17 commented Sep 5, 2018

Love Toastify, but Volume Hotkey is not working. It is under "Spotify only". Tried more than one combination of Keys, it keeps only controlling System Volume, and Spotify's volume (while streaming) does not change. And now, it doesn't even work for system volume. Other hotkeys (Play/Pause, next, previous all working fine. Thanks. (with latest version just installed)

@aleab
Copy link
Owner

aleab commented Sep 5, 2018

@MBS17 If I understood correctly, that's the expected behaviour!

Spotify's own, in-app volume, if that's what you are referring to, can't be controlled; what Toastify can change is just what the OS exposes, and that is the Volume Mixer:

Windows Volume Mixer

When "global volume" is selected, the system-wide volume is changed (the one associated with "Headset" in the image above, for example); when "Spotify only" is selected, only the volume associated with Spotify (in the mixer) is changed.

If you can't notice any change while increasing or decreasing the volume, you can try to change the "Windows Volume Mixer increment" value, which controls by how much the volume changes each time you press the hotkey. Keep the Volume Mixer open while trying, to see if Spotify's volume slider actually changes.

However, please note that if Spotify's volume (in the mixer) is already at 100% (relatively to the system-wide volume, which means if it's equal to the volume of "Headset" in the image above), it can't be increased further.

If it still doesn't work or if I misunderstood, please open a new issue with more details (for example, does is not work only when you are streaming or always?).

@MBS17
Copy link

MBS17 commented Sep 5, 2018

Got it. Thanks. On the PC is working correctly. On Spotify Connect to my AVR, the Spotify Mixer Slide keeps moving on the PC, but it does nothing to the sound coming from the AVR (as opposed for instance to my iPad, where I can control de AVR volume via the iPad). But from what I gather from your explanation, this seems right with how the PC connects to outside Sound Speakers... Or not? Thanks anyway.

@aleab
Copy link
Owner

aleab commented Sep 6, 2018

@MBS17

as opposed for instance to my iPad, where I can control de AVR volume via the iPad

I'm guessing you are using the volume slider inside Spotify on your iPad to control the volume of the AVR. Right?

Unfortunately, I'm not familiar with AVRs, so I have no clue on how they work. I can only make a guess.
If your AVR has built-in Spotify (many from Denon do, I think) and is connected to the internet, I guess the music is not being reproduced from your PC (and then streamed to the AVR), but rather reproduced from the AVR directly and then streamed to the connected devices. You can see the active device from Spotify Connect on any other device:
Spotify Connect

If it's not your PC, then that's why changing the volume from the Volume Mixer does nothing, since the Spotify app on your PC is not outputting any sound whatsoever.

Some time in the future I'll implement Spotify's Web API and it might be possible (only for Spotify Premium users, though) to control the in-app volume.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants