Hi, I've developed an extension that provides volume control functionality for RME ADI-2 series devices. The extension supports multiple devices connected simultaneously and reacts to USB hotplug events to create a new Roon API volume control instance via the .new_device() call when the DAC device is connected, and device.destroy() when the device is unplugged/turned off. I've found a bug. If the volume device is destroyed and a new one is recreated with the same ID (device serial number is used as the ID), the changes are not reflected in the Roon app (I'm using the latest macOS version) - the recreated device is not displayed. I've implemented a workaround - to re-pair (unpair and pair again) the extension. Although the workaround works fine, as the repair is instantaneous, the issue should be fixed.
Dear Roon Support Team,
I wanted to check if someone is currently looking into this matter and if you could provide an estimated timeframe for when I might expect an update.
If you need any additional information from me to assist with investigating this issue, please don’t hesitate to reach out.
Thanks.
Best regards,
Andriy
I can turn off my ADI-2 device and the volume control still works if the ADI-2 is powered on again. I do this every evening and never got an issue with that.
Also I have a lot of customers and never got an error report regarding this by one of them.
The issue is described in detail in my first post and is not related to a specific device. The virtual volume control device created with the .new_device() can be removed with the .destroy() call. The removal works as expected, but if the device is recreated with the same ID by calling again .new_device(), the volume control will not appear in the Roon app until the extension is reconnected.
The Roon Extension is the entry point for the volume control. If the Roon Extension is not enabled it can’t work even if it has the same ID. An enabled Roon Extension is always necessary.
Your comment suggests that you didn’t understand this issue. I’m sorry that my explanation wasn’t clear enough for you. I didn’t imply that the extension was not running; what I meant is that if the volume control virtual device is recreated (destroyed and created again while the extension is running and connected to the Roon Core), it will not appear in the Roon app until you force the extension to disconnect from the Core and connect again.
My bug report was addressed to the Roon Support team, so I don’t require any assistance from the community in this particular case. I have a unit test demonstrating the problem, and I’ll share it with the Roon team as a code snippet if requested.
You are posting in the Tinkering category where Roon Support will not see it. Also, other Roon customers are free and encouraged to offer help. @DrCWO probably knows more about this topic than anyone else on this forum.
I don’t know why, but the level of insults on the forum has increased significantly recently. People ask for help, then insult those who offer help.
@Jim_F I didn’t meant to insult anybody. But I see now where this misunderstanding is coming from. I didn’t realize that my issue report ended up in the Tinkering section of the Community forums. I didn’t post it here, but reported via the form in the official Roon website. I assume moderators dispatched it here. Anyways, @Geoff_Coupe already mentioned he would tag the Support team.
@Jim_F Well, it is natural for a forum that people post
I may be repeating myself, but this is my first time reporting an issue, and I didn’t realize it would start a regular forum thread. I wasn’t looking for help, as my extension works perfectly. It will soon be released as free and open-source software.
My goal was to make the Roon team aware of the issue so they could address it.
I must say, the community here is amazing - big, active, and very helpful. There are many instances where community assistance can be incredibly beneficial. However, when assistance is not requested, I believe it makes sense not to force it.
I’ll switch completely to the “forum mode” now.
Thank you all for your comments and explanations: @DrCWO, @Jim_F, @Geoff_Coupe.
@Geoff_Coupe, as a moderator, could you guide me on whether there’s a way to submit a bug report without starting a forum thread?
Feedback is monitored by Roon’s product team.
Though they rarely comment on specifics, and don’t interact with users in the same way that the support team do.
