SOLVED - ADI-2 Pro FS R Remote Control - Disconnected

Yes MIDI Control is On. Still disconnected.

Any other ideas?

Yes I have version 2.1 for the remote software.

The Madiface driver is version 1.0.17.0

I wasn't sure about the firmware with all the different numbers provided by the firmware update tool.... fut.exe. There was only a  button for "OK" and "Cancel". Is there another way to check firmware version?

Thanks for the help!
.

New Revision: USB, 269, DSP 130
Current USB Revision: 267

DSP Firware Version: 128
Fallback USB Version: 265

I went back and ran the update tool another 4 times and none of the numbers changed. But when I clicked the OK button it told me power cycles the device.
When I ran the update tool again the numbers changed for two of the lines.

Current USB Revision: 269

DSP Firmware Version: 130

The Remote still shows Disconnected.

I really need the Remote to work. My vision is 20/200 and it's very hard for me to read the display of the ADI2.
.

Do you have another PC or Mac where you can try this? It must be a MIDI issue on the PC.

Otherwise you can try this:

• Disconnect the ADI-2 device, open Device Manager, click View > Show hidden devices.

• Expand Sound, Video and Game Controllers and Universal Serial Bus Controllers, then right-click and uninstall any faded/greyed-out MIDI or audio entries.

• Plug your ADI-2 back in so Windows performs a clean re-detection.

- I tried the above suggestion, but no change.
- Then I uninstalled the device again, but this time I had it remove the software
- Restarted computer
- With the aDI2 USB disconnected, I installed the driver again v1.0.17.0.
- Connected the USB ADI2 and turned it on
- Open Remote
- Still Disconnected
.

Midiox will not help you.

You have to run the FUT and see if it can update the firmware of the ADI-2.

https://rme-audio.de/downloads/fut_madiface_win.zip

Do it.
Then you know the firmware is up-to-date and the driver is working.

Then the remote app should connect.

I've done this, it updated the firmware and it has not helped.
.

I have O&O Drive Image software for creating image files. I returned to a previous image from April 2026 that still had all the MS bloatware.

This solved the problem, the ADI2 Remote software is now CONNECTED!

I will grab another image file so that I can return to a known good Windows 10 image in a matter of minutes if I screw things up again.

Thanks to everyone that offered help, it's greatly appreciated!!!

You don’t simply install some tuning software that does all sorts of miraculous things ;-)

It doesn’t actually take that many settings in the BIOS and the operating system to ensure that a Windows-based computer works well as a DAW.

Essentially, it involves a few simple steps in the BIOS to prevent the CPU from entering deeper sleep states and the associated latencies. Here are a few examples for Intel BIOS; AMD BIOS uses different terms, but essentially it's all about the same story.

Disable C-states (in some older BIOS versions, this also includes P- and T-states). Waking CPU cores from sleep states causes delays that conflict with the real-time requirements of audio processing. Usually, you either disable this feature or set it to C0 or C0/C1, depending on the BIOS version.

It is best to disable C1E. This is the automatic idle state that reduces voltage and clock speed. This leads to noticeable latency spikes as well.

Enable TURBO. This slightly increases the CPU clock speed for all cores beyond the base clock. For my system, +200 MHz more, 3.6 instead of 3.4 GHz.

You could disable SpeedStep, but I leave it enabled so that I can control aspects such as the system clock and CPU core parking using the Windows power plans, which can be configured more precisely within Windows.
In ‘High Performance’ mode, CPU core parking is disabled anyway, and the cores run at the highest possible clock speed. Especially as there are tools for Windows like Bitsum's "Process Lasso Pro" that allow you to switch between different power profiles automatically based on the applications that are in use. For example, default balanced, if you are IDLE energy-saving and if you are using the DAW, then maximum performance. That’s why it’s not worth setting this fix in the BIOS.

I would also disable Spread Spectrum, because it modulates the motherboard’s reference clock by approximately -0.5% to -0.25% in order to spread electromagnetic radiation peaks across a wider frequency band. This primarily enables manufacturers to pass strict EMI certifications (FCC/CE). This might also introduce a little latency which I would avoild from ground up by disabling it.

For Windows, a fellow forum member created a tool, "Vilm Care" which concentrates on the essential Windows settings.
More than that is not needed.
https://forum.rme-audio.de/viewtopic.php?id=43146