Hardware / Software
Nucleus Titan early access 1448
ARC early access 288 (on Pixel 8 Pro)
Roon Remote on Windows 10
@Early_Access I wanted to bring this to your attention in case this is a regression. This looks/feels very similar to the ARC connection/sync issue that may have been related to genre tags discussed in arc-fails-when-syncing-to-core-update-to-build-1148. If not, I can take this over to regular support if I need additional help.
Logs (image highlighting where I believe the issue is vs success)
Details
I finally gave in and traded in my Nucleus+ for the Titan. It arrived the day 1448 rolled out, so I upgraded the Nucleus+ to 1448 and I made sure the Titan was on 1448 before I attempted to migrate over. I created a fresh database backup from the Nucleus+ with 1448.
I have a DHCP reservation set for the Titan, and it was the same IP address that the Nucleus+ was using previously. I have a port forwarding rule for ARC using that IP address. Testing ARC from within Roon Remote on the Titan is always successful.
I also moved over an internal hard disk. No issues with that.
When starting with a fresh database on the Titan, if I restore from my 1448 backup first and then login, everything within Roon Remote looks correct. Added / Played albums, history, playlists, etc. are all correct. However, starting with a fresh ARC (cache and storage cleared from android app settings), ARC fails to connect after selecting the Titan and logging in. I get “Something went wrong while syncing to your Roon Server”. I believe this corresponds to the first part of the logs I highlighted with orange.
On the other hand, if I reset the database (either by resetting from the web interface or renaming RoonServer), I can then start a fresh ARC (cache and storage cleared from app settings) and connect to the Titan without any issues.
I can repeatedly go back and forth between these two scenarios and so far, I’ve gotten the same results each time.
Hi, @gsuzor91, thank you for your report. We are investigating it now, will let you know if we need any additional data. Quick question, will it be possible for you to switch to the production track on your Nucleus Titan and see if this issue occurs there?
I just went through my library and cleaned up unavailable Albums and Tracks. Perhaps I missed some, but the same issue with ARC syncing is still occurring.
Some “broken” tracks in my playlists had a gray icon, would not play, and clicking on the Album said the album wasn’t available. However, these tracks were not marked as “unavailable”, and the playlist improver did not identify these. I’ve replaced or removed these tracks.
I noticed that when logging into a freshly wiped ARC, when logging in for the first time it would say that the Titan is only available on my network. If I then go to my Win 10 Roon Remote and navigate to Settings > Roon ARC, the automatic verification runs and the status of the Titan in ARC almost immediately turns Green.
Hi @ivan, well this is interesting, and I was not expecting the result I just got. ARC is working with Production!
The Titan, Windows 10 Remote, Android Remote are now all on Production 1442.
ARC is on Production 284.
Before moving to production, I was experimenting with logging out of Qobuz and disconnecting my local library. I then went to Win 10 Roon Remote > Settings > Library > Clean Up to see if this would clear the ARC error. It did not make a difference.
To set a level playing field, while still on early access 1448, I reset the Titan from the web page and then using the Wind 10 Remote I restored the backup that was automatically created last night. This backup contains my original library with plenty of unavailable tracks and albums. I restored the backup before logging in.
After restoring the backup, I believe I checked if ARC failed to sync, and I believe it did. I then switched everything over to production, cleared ARC app data one more time, and then connected to the Titan and it was successful the first time on production.
Update: I have confirmed that reverting back to Production 1442 / 284 fixes the issue, while starting with or going back to Early Access 1448 / 288 breaks ARC. I have flipped back and forth between production and early access several times now, and get the same results every time.
I have had similar issues with pretty much most builds of Roon arc and my Android DAP. Rebuilding an existing machine or swapping server to a new machine with a database restore stops a pre existing arc from connecting to it. Only a full reset of data on Android or a an uninstall on iOS remedies the issue.
I’ve also has similar issues in the past, but this one may be different. In the past I was able to get ARC working with a restored database, though that might mean fully resetting ARC on my android phone.
This time, ARC connects without issue on Production 1442 / 284 on the Nucleus Titan. However, I have not been able to get ARC to connect at all with Early Access 1448 / 288 using my restored database, even after resetting ARC. I believe the only time it did connect with EA 1448 / 288 was when I tested with a completely blank / reset database.
I’ll also add that I do not believe I tested ARC with my (old) Nucleus+ with EA 1448 / 288. I had the Nucleus+ on EA for quite some time now, but I started boxing it up to return for the Titan swap the same day EA 1448 / 288 was released. There’s a chance this is just an EA 1448 / 288 issue that would have happened even without the hardware swap / database restore… but I have no way to know since the Nucleus+ is now on its way back.
Either way, I’m glad Ivan and team were able to reproduce the issue.
I believe the particular ARC sync issue I was experiencing with ARC 288 early access was resolved back in early access 1456 / 296. I verified this with the latest 1459 / 298 ea release.
Steps Confirming Issue is Resolved
Web Interface
Reset database
Reboot
Roon Remote 1459 (Windows 10)
Select a different Roon Server / Yes
Connect
Restore a backup (hiding at the bottom)
Select the backup from last night from my NAS
Relaunch
Connect
Wait a couple of minutes for the history on home page to load
and traded in my Nucleus+ for the Titan. It arrived the day 1448 rolled out, so I upgraded the Nucleus+ to 1448 and I made sure the Titan was on 1448 before I attempted to migrate over. I created a fresh database backup from the Nucleus+ with 1448.