Home Assistant - there is now MQTT state publishing with autodiscovery. Once you point the app at your broker, entities for volume, mute, output, media info, and album art URL appear automatically under Integrations - MQTT. No manual YAML needed. Requires paho-mqtt>=2.0.0. Note that full two-way media_player control via MQTT alone is not possible without additional HACS extensions - the standard HA MQTT integration does not fully support the media_player platform out of the box. For sending commands back to the app from HA, use the built-in HTTP API (REST commands) or the web remote as an iframe card.

Other notable additions:
- Album art fetching - background download from iTunes, MusicBrainz/Cover Art Archive, and Deezer when the SMTC art is missing or poor quality (no API keys required)
- iOS / PWA support for the web remote - installs as a standalone app
- Media key interception fix - the intercept is no longer gated on Now Playing mode, so it works correctly in all modes

Note on Brave browser: if you use Brave and play media (e.g. YouTube), you may find that play/pause via the media key does not work as expected. This is caused by Brave Shields - disabling Shields for the page resolves it. I tested this on Brave Origin (Nightly) but I expect the same applies to all Brave versions.Chrome, Firefox, Edge work without any changes.

To fix this modify rme-volume-controller-main.py line 17 and restart it :

__version__ = "1.3.2"

It's great to see Stream Deck features in this version :-)

Cool new features!

Question, is it possible that the commands wont work if I try it while playing a game? I dont seem to be able to get the volume down with it when I am inside a game. If I alt tab back to my desktop then it does work. I do use the Steam Deck plugin so I am not sure if that is the difference here

Thanks for the update, gonna try it later today

Since it works when you alt-tab back, the app and DAC connection are fine. The issue is that the fullscreen game is capturing the key events before they reach our hotkey handler.

I've just pushed v1.3.1 which includes diagnostic logging for exactly this scenario.

Once updated, could you test with Debug mode ON (Settings -> General -> Debug mode):

1. Start the app
2. Change volume on desktop. Confirm it works, check log for lines like:

2026-04-20 23:51:14,506 [DEBUG] LL hook: VK=0xAF (VolUp) flags=0x11
2026-04-20 23:51:14,508 [DEBUG] WM_HOTKEY received: id=1

3. Go into the game (fullscreen)
4. Try changing volume in-game
5. Alt-tab out, check the log file (right-click tray icon -> Open log)

What we're looking for:
- If both LL hook: and WM_HOTKEY lines are missing while in-game the game is blocking all key events at a low level (DirectInput exclusive mode)
- If LL hook: appears but WM_HOTKEY is missing the low-level hook sees the key but RegisterHotKey doesn't receive it in fullscreen
- If neither appears the game is consuming the keys entirely before Windows can process them

Quick workaround: switch the game to borderless windowed mode instead of exclusive fullscreen. Hotkeys should work there since Windows keeps processing them normally.

v1.3.1 also adds a few new features: volume slider popup (left-click the tray icon), sample rate display in the tray tooltip, and AutoDark on idle. Full changelog on the release page.

Thanks for the update, gonna try it later today

Playing OSD
The app now shows a custom "Now Playing" overlay when tracks change, triggered by play/pause, or optionally on volume changes. It uses the same dark design as the Volume OSD. Consistent look across both overlays.

- Track name, artist, album art, and a progress bar with timestamps
- Album art fetched via Windows Media API, preserving aspect ratio (square for music, wide for YouTube thumbnails)
- Bouncing marquee scroll for long titles that don't fit
- Play/pause indicator icons
- All independently configurable: position, size, opacity, duration, colors
- Drag-to-place positioning

The progress bar interpolates between API updates, so it runs smoothly even when the source app only updates position data every ~30 seconds.

App Filter
The app auto-detects which programs are playing media (Spotify, foobar2000, browsers, etc.) and lets you choose which ones should trigger the Playing OSD. Detected apps show up as checkboxes in Settings with live refresh. Just play something and it appears. You can also add app IDs manually.

Auto-Update Checker
The app checks for new releases on Codeberg on startup and periodically. When an update is available, dialog pops up with the changelog and options: Update now, Skip this version or Later. The update script auto-detects your git branch, does git fetch + git reset --hard, and reinstalls dependencies if requirements.txt changed.

Settings UI Overhaul
Everything is now organized into tabs: General, Volume OSD, Now Playing, Hardware, Updates. Much easier to navigate with all the new options.

!Important: New Dependency!

This release adds winsdk as a dependency (required for Now Playing/media control). If you're updating an existing install:

venv\Scripts\activate
pip install -r requirements.txt

Or for a fresh install:

git clone https://codeberg.org/Epocha/rme-volume-controller.git
cd rme-volume-controller
python -m venv venv
venv\Scripts\activate
pip install -r requirements.txt

Playing Modes (Settings → Now Playing)

- default - no changes, Windows handles everything
- hide - intercepts media keys to suppress Windows overlay, no custom OSD
- custom - full Playing OSD with all the features above

Not everybody own a Stream Deck so the Python version has to stay alive

There are options to dev plugins without owning a physical Stream Deck :

• there is a Stream Deck Simulator : https://docs.elgato.com/ipad/simulator/

• an emulator : https://github.com/FritzAndFriends/StreamDeckEmulator

• there is a mobile version https://www.elgato.com/us/en/explorer/p … for-free/,  which offers 6 free buttons which can be used in an android emulator (not sure if you can simulate a rotary encoder with this) : https://www.reddit.com/r/elgato/comment … ream_deck/

Do you plan to add an autoupdate feature ? or at least a check if a new version is available option ?

Thanks for the resources, good to know there are options for development without the hardware. Auto-update is a good idea, I'll add it in the next version. For now I want to focus on getting this project fully stable first, especially the ADI-2 Pro support which is still being worked on. Once everything is solid I can look into the Stream Deck plugin.

There are options to dev plugins without owning a physical Stream Deck :

• there is a Stream Deck Simulator : https://docs.elgato.com/ipad/simulator/

• an emulator : https://github.com/FritzAndFriends/StreamDeckEmulator

• there is a mobile version https://www.elgato.com/us/en/explorer/p … for-free/,  which offers 6 free buttons which can be used in an android emulator (not sure if you can simulate a rotary encoder with this) : https://www.reddit.com/r/elgato/comment … ream_deck/

Do you plan to add an autoupdate feature ? or at least a check if a new version is available option ?

Hello,

I've a DAC 2 FS, a Stream Deck and Windows 25h2.

@Epocha : your script (v1.2.4) is working fine with Stream Deck default System Volume plugin (El Gato drivers 7.4.0) which is great !

I you don't know what to code you can make your script a native Stream Deck plugin

Thanks for your work.

Thanks for confirming it works with the default Stream Deck plugin. A native Stream Deck plugin is an interesting idea, but it would be a completely separate project since the Stream Deck SDK uses a different architecture (Node.js/HTML). I don't own a Stream Deck myself so I wouldn't be able to develop or test it, but once the project is fully polished, anyone is welcome to use it as a foundation for building one.

I've a DAC 2 FS, a Stream Deck and Windows 25h2.

@Epocha : your script (v1.2.4) is working fine with Stream Deck default System Volume plugin (El Gato drivers 7.4.0) which is great !

I you don't know what to code you can make your script a native Stream Deck plugin

Thanks for your work.

Thanks. Found a plugin that hooks into the volume keys like you mentioned (not all of them did properly apparently) but now it works and its great. It's no longer an absolute pain to volume change in Roon too. Really appreciate ur effort.

Glad to hear it's working. Enjoy the setup, and if you run into any issues, feel free to post here.

Now it detects correctly when Line Out 1/2 is activated, but does not detect the Ph. 3/4 as the active output if I have Toggle Ph/Line option set to "3/4" or "1/2+3/4" — it shows that the active output is Ph 1/2 then.

Now if I set the Toggle Ph/Line option to "All Plugged", then the app detects Ph 3/4 as the active output. If I then plug another headphone to Ph 1/2, and the "Dual Phone Mode" is enabled, the unit then cycles between all three outputs and the app detects this correctly. What is weird enough, is that when I plug headphones in both outputs and have the Toggle Ph/Line option set to "1/2+3/4", it then shows strictly the output 3/4 as active (when actually both phone outputs are active at the same time, each with its own volume setting).

Here is the log, hope you'd be able to figure it out

Sorry about the previous version mix-up, I accidentally pushed an older codebase. v1.2.4 now has the actual fix with the toggle config cache.

Changes based on your logs

- The app now reads your Toggle Phones/Line setting (idx=10) during sync and caches it. After a toggle pulse, when the Pro sends the ambiguous 0x05 status, the app uses your toggle config to determine the correct output instead of guessing.
- Added dual phones mode: when toggle is set to "1/2+3/4", volume wheel adjusts both Phones 1/2 and 3/4 simultaneously (same dB step applied to both, each keeps its own level). Mute also toggles both. OSD shows "PH 1/2+3/4".

What I need from you to nail this down:

Please test each toggle mode one by one and for each one write me which output the app detected vs which output was actually active on the device. The log lines I need to see look like this:

0x07 resolve: model=ADI-2 Pro active_bits=1 line=0 ph34=0 toggle_cfg=2 -> Phones 3/4

If the app says Phones 3/4 but the actual active output on your device is something else, write that. For example: App says Phones 3/4 but actual output is Phones 1/2.

I apologize for the back and forth on this, debugging the Pro output detection remotely is quite challenging since the Pro has significantly more toggle combinations and output routing options compared to the ADI-2 DAC I develop on. Your logs and feedback are invaluable.