Are you tired of constantly switching back and forth between your game and Spotify just to adjust the volume? With this app, you can finally control Spotify and adjust it's volume separately, all without the hassle of alt+tabbing. Say goodbye to interruptions and hello to effortless audio management!
This background Python Windows application utilizes the global_hotkeys module to listen for basic hotkeys, allowing users to easily control Spotify without the window focused. The app leverages the power of Spotify's Web API through the use of Spotipy, providing seamless integration between the app and the music streaming platform.
Please see FAQ for more information or if you encounter any issues. If your issue isn't listed, please create an Issue ticket.
Plans to refactor to C# soon! It will solve the following problems:
- Modularity
- Extensibility
- Update friendly
- No more false virus flags
Download the latest version from the Releases page.
You can build the .exe
yourself with the provided build command in the build.py
file.
- Windows 10/11
- Spotify Premium
- Spotify on your device of choice
The app requires the user to input four fields:
- To obtain the
Client ID
andClient Secret
, head to the following link Spotify for Developers. - Sign-in and click on your profile in the top-right corner, then click on "Dashboard".
- Click on the "Create app" button to the right.
- Enter any "App name" and "App description" you want.
- In the app, populate the
Port
field with a port (e.g., 8888, 8000, 8080).- There's a possibility that the port you chose is being used on your network, if so, choose a different port.
- Back on the website, enter the following into "Redirect URI" with the port you chose (e.g., 8888):
http://localhost:8888/callback
- Click on the checkbox and then "Save".
- Click on the "Settings" button to the top-right.
- Copy your
Client ID
andClient Secret
(press "View client secret") and paste it into the app.
- To obtain your
Device ID
, press the button "Get Devices" in the app once yourClient ID
andClient Secret
are filled in. - Click on the drop-down arrow and select your device of choice.
- Note: if you don't see your device listed, open the Spotify app on that device and play something, then check again.
Once you're done, click on Save
within the app to save your settings. Click on Start & Close
to close the window and start listening for your hotkeys!
You can open the settings again by right-clicking on the app's system tray icon.
Please go through the below steps before creating an Issue ticket.
- If your app is not starting/opening, please see Why Is The App Not Starting?
- If your app is not starting on Windows startup, please see Why Isn't The App Starting on Startup? and Not launching on startup. #5
- Make sure your Client ID and Secret is correct and matches what is displayed in the Spotify developer site.
- Check if you have the Spotify desktop app installed, and make sure the Device ID selected is the correct one.
- Check if you're able to see the app within the system tray after pressing
Start & Close
. - After confirming the above and it still doesn’t work, it is likely a port problem and you’re already using the selected port on your network. Choose a different port in the app, and also change the Redirect URI set in the Spotify developer site.
- Where Is My Information Saved?
- What Information Is Saved?
- How Do I Update The App?
- How Do I Disable Certain Hotkeys?
- Why Isn't The App Starting on Startup?
- Why Is The App Not Starting?
- My Hotkeys Stop Registering After Waking From Sleep
- Press
Win+R
to bring up the "Run" menu, or type in "Run" within your Windows search bar. - Enter the following in the "Open" input field:
%appdata%
- Your information is stored locally within the
.../AppData/Roaming/.beatbind
folder. It stores your configuration settings and the token information required to interact with Spotify's Web API.
There are two files stored within the .../AppData/Roaming/.beatbind
folder:
config.json
, which contains your Client ID, Secret, Device ID, and your hotkey combinations..cache
, which contains your token information to communicate with the Spotify app.
You can just replace your existing file(s) with the updated version. The config files are still saved within the .../AppData/Roaming/.beatbind
folder, so your settings won't be lost.
Note: If your app keeps crashing after an update, you'll have to delete the .../AppData/Roaming/.beatbind
folder and reinput your settings, or update your config.json file (Where Is My Information Saved?). Here is the current format your config should look like for v1.2.0+:
{"startup": true, "minimize": true, "client_id": "{your client id}", "client_secret": "{your client secret}", "port": "{your port e.g., 8888}", "device_id": "{your device id}", "hotkeys": {"play/pause": "control+alt+shift+p", "prev_track": "control+alt+shift+left", "next_track": "control+alt+shift+right", "volume_up": "control+alt+shift+up", "volume_down": "control+alt+shift+down", "mute": "control+alt+shift+space"}}
- Uncheck all of the
Modifiers
checkboxes. - In the
Key
field, press "Backspace" or "Delete" on your keyboard to clear the field.
This happens if the location of the app file was changed. The registry key used to start the app on Windows startup needs to be updated to the new .exe
path. Starting the app again will update the path in the registry key and should resolve the issue.
- If you had "Start minimized" checked, you can find the app's icon hidden within your system tray and then right-click on it to find the settings menu.
- Windows could be flagging it as a virus. Downloading the
.zip
folder instead or adding the.exe
file to allowed files under Windows Security could fix your issue. - Check to see if you have the following folder, and then delete it:
.../AppData/Roaming/.beatbind
. Please see Where Is My Information Saved? to find the folder.
There are rare cases where hotkeys stop registering on system wake up from sleep, and pressing Start & Close
button again fixes the listener. For a more permanent fix, try disabling Windows Fast Startup. If the bug keeps occurring after disabling Fast Startup, please create an Issue ticket.