Yes, I've tried this MIDI protocol but I can't get a simple muting/unmuting command to work with sendmidi

sendmidi dev "ADI-2 DAC (59651073) Port 1" syx "F0 00 20 0D 71 02 0F 00 01 F7"

Won't trigger anything to output

Thanks, I own the ADI-2 DAC. I've tried the command and downlooaded MIDI Monitor and doesn't seem like DAC is actually set up to accept incoming MIDI. The only thing I found researching through the forums is with Roon (https://community.roonlabs.com/t/rooadi … acs/258291) which I don't use.

Yes I have 81/62, the ADI-2 Remote App connects and works. However, it is all controlled via mouse controls, it doesn't support keyboard shortcuts. Therefore I'm trying to rely on MIDI but I think it's somehow disabled or unsupported for volume control.

It's sending SysEx messages but not reacting to incoming SysEx commands. I don't see a SysEx on/off toggle in the ADI-2 Remote app nor the DAC itself

@waedi

pbj uses sendmidi (with the syx parameter in his command, see his Post #3 or details below)...

We do not want to send midi sysex messages to the Remote App. It is not involved in our scenario.
We want to communicate with the ADI-2 DAC directly...

(correct me if I'm misunderstood sth)

-----

@pbj

i just saw you try to send sth like this:

sendmidi dev "ADI-2 DAC (59651073) Port 1" syx "F0 00 20 0D 71 02 0F 00 01 F7"

this will not work as  intended.
In fact, you send F0 00 F7 (I verified this via MIDI Monitor).

a "sendmidi -h" tells me this:

So, try this instead your command above (no surrounding „“, no F0/F7 status bytes but add the hex parameter to inform sendmidi that the following bytes should be interpreted as hex bytes):

sendmidi dev "ADI-2 DAC (59651073) Port 1" syx hex 00 20 0D 71 02 0F 00 01

Additionally, looking into the sheet, and putting things together regarding your unit, make a test:

1) sendmidi dev "ADI-2 DAC (59651073) Port 1" syx hex 00 20 0D 71 03 09 (=Request all settings from ADI-2/4 Pro - or sayin "Hello!" to the unit)

2) then you should receive a big bunch of messages (all settings)

3) then you should continuously receive the status from ADI-2/4 Pro (after first valid command) which looks like this: F0 00 20 0D 71 07 11 30 7E 08 00 00 00 02 04 01 11 00 F7

4) Now, try to set Volume of Phones 3/4 to -10dB (address 9, parameter index 12, value -100) via:
sendmidi dev "ADI-2 DAC (59651073) Port 1" syx hex 00 20 0D 71 02 4B 1F 1C

5) Or try to set Input-Range to 13dBu (address 0, parameter index 1, value 2) via
sendmidi dev "ADI-2 DAC (59651073) Port 1" syx hex 00 20 0D 71 02 00 20 02

I am pretty sure this should work now (according to Ralf's really good documentation).

PS: I did not verify if ADI-2 DAC really has Phones3/4 and the Input Ranges till now. But I would bet sth that this should work...

i didnt look what this exactly does...

Is the ADI-2 Remote app running while you do this? (should probably not)

A midi monitor screenshot or detailed midi log what you send and what you receive would help to understand what happens...

Edit: Verify you have set midi monitor like this:

Ok, thanks to this other thread: https://forum.rme-audio.de/viewtopic.php?id=38970
– I finally got it working. macOS media keys on F10/F11/F12 are controlling mute/volume down/volume up on my adi-2 dac now.
Next to some adaptation to the script using sendmidi on macOS it needed the Hammerspoon app to get access to the keys.
It is perfectly in sync with the hardware now and the keys maintain their original function when used with other Audio interfaces.
just the the adi-2 remote app does not update its volume dial when I change it through the my keyboard and the big dB overlay is not displayed.

Great effort and potentially a very useful tool.

However, while using it with my ADI-2 Pro (of course, I have selected the correct device model in the app's settings), I encountered a couple of broken functions.

1) The "Sync from DAC" command does not sync the active output and the current volume level. The "reconnect" command, however, does re-read the current volume.

2) The Line/Phone output switch does not work (regardless of how I configure the "Toggle Ph./Line", "Mute Line vs. Phones", "Dual Phones", and "Balanced Ph. Mode" settings).

Also, it's worth noting that the ADI-2 Pro has two independent headphone outputs and also has quite a few toggle settings combinations. I think that the toggle function in your app should work identical to the corresponding "Toggle" control of the RME's ADI-2 Remote app, and specific toggle behavior should be set by the user using the device settings. This way, I think, we can avoid overloading your app with settings in the UI and with their handling in the code.

Might be of help to look at this post: https://forum.rme-audio.de/viewtopic.ph … 72#p212972

I hope my feedback is useful. Thank you!

Thank you! I tried this out quickly. The feedback when I adjust the volume using other means works (albeit with a slight delay when I do it via the RME's Remote app). But there still are some rough edges.

1) The output toggle command works as intended, by switching the active output in accordance with the unit's settings. But your app assumes that the output switches in a fixed sequence "Line Out → Ph 1/2 → Ph 3/4", which is not how most of us have this set up. I have it toggle between Line and Ph 3/4, and this is the most common arrangement. I suggest to relabel the menu entry to "Toggle output" and each time when it's activated to poll the device to determine the currently active output. Otherwise it's a mess: every time I toggle the active output, the app assumes that a different output is active, and controls one that is actually inactive. Also, when I toggle the output manually, the app does not detect this.

1a) When either of the "Sync from DAC" or "Reconnect" functions are invoked, the app does not get the currently active output, at least not until I change the volume on the unit itself.

2) The app sometimes does not capture the media keys events, and Windows (I use Windows 10 Pro 22H2) shows the system volume control OSD, though I have not yet figured out the pattern here.

Anyway, I appreciate the amount work you've put into this piece of software and hope it won't be too time consuming for you to polish it up

Hi, another updates. This one focuses on connection reliability and a new feature for those with a Flirc USB.

USB Device Detection (event-driven)
The app no longer relies solely on MIDI port polling to detect when the DAC is plugged/unplugged. It now uses Win32 RegisterDeviceNotification to receive instant USB events. You can optionally set your DAC's VID/PID in Settings (USB Device Detection section) so the app only reacts to your specific device not every random USB stick. If the Win32 registration fails for any reason, it falls back to the old polling method automatically.

MIDI Port Monitoring (standby detection)
Separate from USB detection, a lightweight background thread now watches whether the MIDI port is still present in the system. This catches the case where you power off the DAC via its front button or remote the USB device stays on the bus but the MIDI port disappears. When it reappears (DAC wakes up), the app reconnects and re-syncs automatically.

Reconnect stability
Previous versions occasionally detected the wrong output after reconnect. Root cause: the DAC sends a burst of Setup Name packets (0x05) right after boot, and the app was trying to sync before the firmware was fully ready. Fixed by adding proper init delays after connect and increasing the SysEx response timeout. Also fixed a race condition where both the USB watcher and MIDI monitor could trigger a reconnect simultaneously they now share a lock so only one runs.

Flirc IR Power-On
If you have a Flirc USB IR blaster, you can now power on the DAC by holding the Mute key. The app uses a low-level keyboard hook (WH_KEYBOARD_LL) to detect the hold gesture, so it works even when the DAC is offline and the volume keys are released back to Windows. Setup is simple capture the IR timing from your RME remote in Flirc's Device Log, paste it into Settings, done.

One limitation: Flirc's sendir command can only transmit short IR bursts (buffer limit of ~8 NEC frames). This is enough to power ON the DAC (short press), but not enough for power OFF (which requires a continuous long-press signal). So this is power-on only use the remote or front button to turn it off.

The app also saves and restores the Windows mute state during the hold gesture. Since the Mute key passes through to Windows while the DAC is offline, holding it would normally mute your system audio. The app snapshots the mute state on key-down and restores it after the IR signal fires, so your speakers/headphones stay unaffected.

Other fixes
- Shutdown no longer hangs force exit with 3s timeout if pystray blocks
- OSD no longer crashes on shutdown (Tk thread safety) 
- 64-bit Python compatibility: fixed ctypes overflows in CallNextHookEx, CreateWindowExW, DefWindowProcW
- Settings scroll wheel no longer leaks to other windows
- "Sync from DAC" menu item actually works now (was broken by an extra lambda wrapper)

Thanks for the report. I've pushed v1.2.2 with a reworked output detection that should fix the ADI-2 Pro issue.

What changed

The previous version was comparing the raw 0x07 status byte as a whole value (0x04 = Line Out, 0x05 = Phones). This happened to work on the ADI-2 DAC rev 1 by coincidence, but it's actually a bitfield:

- Bit 0-1: active output (0 = Line Out, 1 = Phones 1/2)
- Bit 2-3: device revision
- Bit 4-5: active line output 
- Bit 6: Phones 3/4 active

The app now properly masks the individual bits, so it should work across all hardware revisions and all three models (DAC, Pro, Pro SE).

I also fixed the sync timing — the app now waits for the 0x07 status packet before deciding which output is active, instead of guessing from mute states (which are both UNMUTED in Toggle mode).

What I need from you

1. Update to the latest version from the repo
2. Enable Debug logging in Settings
3. Start the app, do a few output toggles
4. Send me the rme_volume.log file

In the log, the key lines to look at are:

status 0x07: raw=0x?? [active=? rev=? line=? ph34=?] full_packet=...
0x07 resolve: model=ADI-2 Pro active_bits=? ph34=? -> ???

This tells me exactly what status byte your Pro sends and how the app interprets it. If the output is detected wrong, I can see from these lines which bit combination your ADI uses.

Also look for lines like:

Pro output param: Toggle Phones/Line (idx=10) val=?
Pro output param: Mute Line vs PH12 (idx=11) val=?
Pro output param: Mute Line vs PH34 (idx=12) val=?
sync mute: Line Out = MUTED/UNMUTED
sync mute: Phones 1/2 = MUTED/UNMUTED
sync mute: Phones 3/4 = MUTED/UNMUTED

These show your Pro's toggle mode and mute crossover configuration, which helps me understand the full picture.

About the AutoDark issue

"Wake display on output toggle" briefly disables AutoDark to wake the DAC screen when you switch outputs. If you don't want this behavior, go to Settings and uncheck Wake display on output toggle.

Thanks for your effort. I look forward to trying it out

My only volume knob is on my Stream Deck, would I be able to map this to it?

It should work out of the box if your Stream Deck sends standard volume key events (VK_VOLUME_UP/DOWN/MUTE).That's the default behavior for volume controls. The app intercepts those via Win32 RegisterHotKey.
If your Stream Deck sends different key codes, you can remap them in Settings - Hotkeys (just set the Windows VK codes to match whatever keys your Stream Deck sends).
The only case where it wouldn't work is if your Stream Deck plugin controls volume through the Windows audio API directly rather than emulating keypresses. In that case, you'd need to reconfigure the Stream Deck to send keyboard events instead.

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.

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.