RME announces app control for RME Adi-2 series

[thegeton]

You said it's reporting not connected?

Did you check the number of the Midi Port to which you thought it should be connected?

 

[Jimbob54]

Re-read it and yes that’s how I’m reading it. I’m not understanding how windows can communicate with the dac without a driver though.

Generic usb driver in windows

 

[Jimbob54]

You said it's reporting not connected?

Did you check the number of the Midi Port to which you thought it should be connected?


View attachment 300594

Umm......

(I have no idea what that means in terms of my little laptop connected via usb to this dac, or more importantly how I find that out)

 

[thegeton]

Umm......

(I have no idea what that means in terms of my little laptop connected via usb to this dac, or more importantly how I find that out)

You might try this:

Using a MIDI Monitor to Test a MIDI Device

TABLE OF CONTENTS Windows/PC macOS From Inside Your Browser What does this mean? If data is displayed in the MIDI monitor: If only some data is displayed in the MIDI monitor: If no data is displayed in the MIDI monitor or the device is no...

support.inmusicstore.com

 

[thegeton]

Umm......

(I have no idea what that means in terms of my little laptop connected via usb to this dac, or more importantly how I find that out)

Also, do you have Windows 10 or higher and a graphics card that supports Direct3D 12?

 

[Jimbob54]

Also, do you have Windows 10 or higher and a graphics card that supports Direct3D 12?

Yes (utd 11) and no idea !

 

[thegeton]

Did you check your Midi Ports config with the MIDI-OX?

 

[thegeton]

You should be able to check the port mapping like this:

 

[thegeton]

Once you have it mapped, you can check comms:

 

[MAB]

Isn’t the madiface driver a dependency for the remote software? The firmware flashing software certainly needs it to communicate with the device.

I have it installed yet cant get the Remote software to connect. I read @MAB posts as they can get the Remote software to connect on the device that DOESNT have the madiface driver thing installed but not on the one that does.

Yeah, I'm confused too.
The only machine I can get the unit to recognize with remote is my laptop, which has nothing but the remote application installed!
I'll try to debug it more this evening.

 

[MAB]

Once you have it mapped, you can check comms:

View attachment 300600

Thanks for all of this.
I will go dig into this later tonight!!!

 

[iconoclast]

Ooh, so this app communicates with the device via MIDI? So technically, with a bit of reverse engineering you could write a Home Assistant integration that talks to the ADI-2 via MIDI for automation purposes? It would be amazing to be able to automatically switch EQ curves tuned to the speakers in the room in which I currently reside (using presence sensors) in a multi-room setup with the ADI-2 as a source.

 

[Trell]

Ooh, so this app communicates with the device via MIDI? So technically, with a bit of reverse engineering you could write a Home Assistant integration that talks to the ADI-2 via MIDI for automation purposes? It would be amazing to be able to automatically switch EQ curves tuned to the speakers in the room in which I currently reside (using presence sensors) in a multi-room setup with the ADI-2 as a source.

RME will release the MIDI protocol later when things are working as intended, so no reverse engineering will be needed.

 

[thegeton]

You can use this tool if you need to create your own Midi Ports:

loopMIDI | Tobias Erichsen

www.tobias-erichsen.de

Virtual loopback MIDI cable for Windows 7 up to Windows 10, 32 and 64 bit.

This software can be used to create virtual loopback MIDI-ports to interconnect applications on Windows that want to open hardware-MIDI-ports for communication.

The ports created are unique for each user and only exist while the loopMIDI-application is running. So if you log-off, the created ports cease to exist.

When you close the configuration, the application will not terminate, but rather be minimized to the traybar. When you right-click on the traybar-icon of loopMIDI, you get an options-menu to either deactivate the application, configure the ports or to activate autostart each time you log on to the computer.

This software uses the virtualMIDI driver to actually create the ports.

 

[pjn]

Pretty nice - still a complex interface but so much better to have it all right there and easily manipulated. Very impressed.

 

[Trell]

For Windows latest driver is needed for MIDI to work.

>>>I added a crucial information to the opening post, that got totally lost (don't know why):

For the MIDI port to be available in Windows the latest driver version 0.9824 or higher must be installed. Sorry for that. With older drivers the app will stay on disconnected state.<<<

Post #13 in https://forum.rme-audio.de/viewtopic.php?id=37784

 

[MAB]

For Windows latest driver is needed for MIDI to work.

>>>I added a crucial information to the opening post, that got totally lost (don't know why):

For the MIDI port to be available in Windows the latest driver version 0.9824 or higher must be installed. Sorry for that. With older drivers the app will stay on disconnected state.<<<

Post #13 in https://forum.rme-audio.de/viewtopic.php?id=37784

I uninstalled the ADI2-Remote software. Ran the MADIface driver install again. Re-installed Remote. It works. No idea why it didn't initially, no looking back though!

I'm really happy with the application.

 

[thegeton]

I'm really happy with the application.

Congratulations!

Me too!

 

[Jimbob54]

I uninstalled the ADI2-Remote software. Ran the MADIface driver install again. Re-installed Remote. It works. No idea why it didn't initially, no looking back though!

I'm really happy with the application.

Yup - Madiface driver needed updating here too. All good now.

 

[MC_RME]

Nice to see you all connected now

One note: the MIDI port is Class Compliant, that's why it works without driver on the Mac. Audio also works without driver under Windows, but MIDI port access failed for us. Support for that might be incomplete within Windows 10/11. So for using the remote under Windows the latest driver is a must.