MacBook Air
1.7GHz Dual core intel core i7
Memory 8Gb
Catalina 10.15.5
SSD
Also Docker Toolbox and Container running on above iMac - 8gb and the same 6 core i7 processor
Also VirtualBox and a VM running Debian 10.4 and Roon Core latest version
ALL MUSIC STORED ON NAS
Synology DS216Play
Running DSM 6.2.3
4TB HDD Raid 1
Total tracks currently 12275
Roon 1.7 Build 555 with latest updates applied
Preferred install is with iMac running RoonServer and Roon as Control so that Roon is always running whether or not Roon control is running. Also use iPad and iPhone apps.
However have also tried installing just Roon as control, core and output and this makes no difference to the issue.
Lifetime licence
Also have a Qobuz Sublime+ account
Network Details (Including networking gear model/manufacturer and if on WiFi/Ethernet)
BT SMart Hub 2
Netgear 24 port gigabyte switch
BT Whole Home Mesh and ethernet (NAS)
Have tried iMac both ethernet and wireless
Audio Devices (Specify what device you’re using and its connection type - USB/HDMI/etc.)
System Output plus Auralic Aries and Auralic Altair G1.
iPhone and iPad N.B. this issue applies whatever output device is used.
Description Of Issue
From time to time (maybe once a day or so) I can have issues with a device which was previously enabled showing as 'Enabling with a blank name field and it just gets stuck.
Entering a name seems to cause Roon Control to crash on whatever device you are using for control (I have had this on my iMac, Macbook, iPhone and iPad.). I think there maybe a connection between whether you are enabling a device on Control running on the device - i.e. enabling Audi on iPhone from the iPhone.
Usually but not always going back into the control app shows the device enabled. This doesn’t seem to be happening with RoonServer on Linux but if it does happen I will confirm as soon as I can.
I can also confirm this is happening on Roon Server on Linux.
I also found if stuck on enabling with the empty name box then it will appear as stuck on each control point for that controller - i.e. if you view Settings >> Audio on the iPhone and the iPad is showing ‘enabling’ then viewed on the iPad it also shows the iPad as enabling.
Trying it just now entering text into the iPad device stuck on enabling crashed the iPhone control app. Entering text on the iPad did not crash the control app on the iPad and reloading on the iPhone the iPad was enabled.
Hello @Marcus_Russell, thanks for your report! I ran this thread by our QA team and they asked if you could provide specific reproduction steps to get into this state. We’re happy to test this out but were unable to reproduce this on our end.
Similar/same thing happens to me when trying to choose to use my iPad as the output device from the Roon app on the self same iPad. More often than not I see the same thing mentioned here where it shows ‘Enabling’ with a blank name field. Entering a name seems to cause Roon Control to crash . When I reopen the app things seem ok again and I can successfully choose the iPad as output.
Just thought it might be helpful to know you’re not alone!
This may be coincidence but I noted the following:
Load the app on iPhone
iPhone was immediately available as an end point
Leave the app playing on a different end point (i.e. not set to output to the iPhone)
Leave the iPhone to go to sleep
On awakening and going to the app (which is still loaded and which will display the last displayed end point with what ever is playing) then select that output as if to switch zones - the iPhone is not available
Go to Settings >> Audio
the iPhone shows as ‘Enabling…’
Enter a name
Hit return
Control App disappears/crashes
On reloading the Control app the iPhone is now available from the current playing item when you select to switch zones
Exactly the same thing happens with an iPad
At no point did I actually select the iPhone for output (or in the case of the iPad the iPad)
Hello @Marcus_Russell, while researching this thread I found the following directions from another support member that might be helpful here. Please give this a try!
The issue is rather different as far as I can understand and this relates to a containerised Roon Server environment - I am running full Debian Linux and it doesn’t use the ‘deep freeze’ concept as far as I know.
I have also seen this same issue with Roon Server on Mac OS on both my iMac and MacBook Air so I don’t think this is the cause of my issue.
Hello @Marcus_Russell, thanks for checking that. Another item we wanted to try was your other mac as the core. I know you had mentioned it in the first post, have you tested it to see if the issue is present there too?
Hello @Marcus_Russell, could you please reproduce this issue one more time with the iPhone and iMac one more time and reply here with a timestamp when you do? I’d like to enable diagnostics for your account and get a report to our QA team for further analysis. Thanks!
I have now replicated this but it is still difficult to repeat to order.
Kit
iPhone 7s running iOS 13.6
Roon app is always in Dock
Steps:
iPhone running and Roon Control already running on iPhone
On iPhone tap Roon app in dock - appears to crash
Reload
Go to Switch Zone - no iPhone end point showing
Go to settings >> Audio
iPhone showing as previously stated ‘enabling’ - wait a few seconds nothing happens
Enter some text to ‘name’ the end point
App crashes
On reloading app the iPhone now shows in switch zone and settings as enabled and all works until the next time
All times are BST
Checking the RoonServer log this started at 08/17 06:48:37 with connection working at around 06:52
load Roon control on my iPad (technically it’s in standby mode I believe)
go to zones from the track currently playing
If iPad is not showing as a zone then force close the app
Reload Roon control
And then in zones the iPad is now available
Hello @Marcus_Russell, my apologies for the delayed response. Our team is still investigating the issue and would like to pull a fresh set of diagnostics. Could you please reproduce the issue one more time and reply here with a timestamp of when you do?
Afterward, please use the directions found here and send us over a set of logs using a shared Dropbox link.
