I was finding that my RME ADI2-DAC no longer connected with rooADI. It showed as disconnected within the Extensions control and the system log showed a constantly looping MIDI service on my rooExtend device. The good Doctor kindly investigated and it turns out that “MIDI control” on my RME device had been turned off. I’ve yet to understand how this happened, but all was quickly resolved when this was re-enabled via the Settings menu on the RME device. Thanks @DrCWO
Now, if only my rooDial would start working again too…
Edit: @DrCWO - is it possible that the BT patch may somehow have got lost in all the attempts to get things working? Is there any harm in me running the script again? It was all working correctly but now just shows unpaired and won’t reconnect if I attempt to pair - much like the situation before the BT patch.
Just updated to Roon 2.52. In the Display Roon menu, no more screen available, although mine is connected to the PI4.
I use rooExtend to take advantage of my RME ADI 2 DAC, and from the web GUI of rooExtend I see that the screen is connected to the system.
I am running Roon Core from a NAS Synology (updated as well), and I am controlling the apps from a Mac running Sequoia 15.5.
FYI I did not start again with my PI4 since the previous issue (it was impossible to enable the RME), as so far it’s working, and I didn’t receive my 2nd PI4 for other activities yet.
As per the edit to my post - it just shows unpaired…again. It feels like it needs a lot of hand-holding to work reliably between power offs etc, though had been stable up until this unfortunate issue. I wonder if it’s something to do with the BT driver again but have no way to check.
The BT 5.4 antenna is not yet supported. You need the driver Patch for that.
Pairing in rooExtend is only enabled for a limited time after rooDial shows up in Roon Settings Extensions. Please try the steps below. It ONLY works is the Surface Dial was never paired with an other device as the Raspberry PI!
Power of Raspberry with rooExtend
Batteries out of Surface Dial
Power on Raspberry with rooExtend
Batteries in the Surface Dial
Open Roon Settings Extensions
Wait until rooDial shows up in Roon Settings Extensions
Press the Pairing button at the Dial. It shall blink up to 20 times.
After that you should see “Connected” in the Status of rooDial.
If connected
Now open Settings of rooDial
Select the Zone to control
In Roon Play Music in this Zone
Press the Dial and see pf you can start and stop playback.
Many thanks but unfortunately it remains stubbornly unpaired. To recap, this is the same RPi, same dial and same install that was previously working before all the RME issues.
If I login in via SSH, given the credentials, is there a way of telling whether the patched driver is working correctly? As I said before, it looks to me like for some reason the patch is no longer working.
Edit: For reference, this is the ZEXMTE double Antenna BT 5.1, not 5.4.
If all I wrote did not help please re-flash your SD-Card and retry.
After flashing please start the forced update so you are on the latest rooExtend release.
What happens if you press the pairing button? Does the Dial blink and never stop blinking?
EDIT:
I’m out of office for the weekend so my relies may last a bit…
Thanks - is that a change? I previously had to apply a patch, which you supplied, when running the same version of rooExtend (3.4.3) - in your email to me at the time you confirmed that you’d found out it was not supported?
Well, having now tried two different patched installs and 2 different BT 5.1 devices all I can think is perhaps the previous patch is now the issue I guess I’ll try a clean, unpatched install instead - of all the gizmos I’ve tried over the years I think getting the dial to work reliably has been one of the more frustrating challenges!
Hi @dhusky,
I’m really sorry you have so much issues with rooDial. There are approx. 1000 users of rooDial now and only few had some issues in the past.
The idea to start up with a fresh SD-Card install is good in my eyes. Withe the BT 5.1 double antenna it shoudl work right out of the box. Please don’t miss to upgrade rooExtend after the first fresh install to the latest release by waiting one nicht for OTA update or doing a forces update. Most of the users are on the Pi4 platform maybe you also should consider this if you’re not already there.
After the update please re-power the Pi and wait until rooDial shows up. Remove batteries from the Dial, reisert them and press the pairing button. This should work right out of the box.
I’m new to RME. I have an ADI-2/4 Pro SE. I have the rooADI extension licensed and installed. I have headphones plugged into the 4.4mm balanced out on the front and active monitors plugged into the XLR connections on the rear.
I have the volume knob set up to toggle between phones on 3/4 (which is the balanced out on the front) and 1/2 which is XLR on the back.
The issue I’m having is that when I’m playing through headphones, adjusting the volume in Roon correctly adjusts the volume (via the extension). When I switch to the XLR outputs, adjusting the volume in Roon does not adjust the output volume on the RME. The volume knob on the device itself works, but changes made are not reflected in Roon. When I change it in Roon, Roon adjust the displayed volume in Roon itself, but no change is made to the device.
Is it possible to get this work? Do I need to link the volume on the RME or something like that?
You can see a table with clarifying the different models of the RME ADI-2 family dacs.
Also in this post there is a link where the benefits of the “Auto Ref Level” feature is described in an Excel table, showing the effect regarding SNR if you decrease device volume using “Auto Ref Level”. Clearly visible that with the ADI-2/4 Pro the SNR is still -119dB at vlume setting of -23dB. Down to this volume there is no decrease in SNR. Great table and good news for rooADI users.
@DrCWO This is an excellent extension and one I’ve been eager to see working - thank you very much for making it!
I have just one question, which is if we can install RooADI s as a service on an existing Pi rather than having to have a single function appliance. For example many users have a Pi endpoint like Ropieee to have a touchscreen display. As RooADI cannot be using many system resources it seems practical to be able to run it alongside some other things on the same Pi. Certainly it would be wasteful to have two Pis running just to add volume control. If one buys a Roo ADI license can one install it as a service rather than as an appliance? What dependencies would have to be installed for it?
Thank you!
Hi @klerm,
I’m sorry but as I’m a one man business I can only offer and support the appliance. At the moment I have no plans to offer a package that can be installed on different environment.
