Been using ARC all afternoon been fine then on way home on train not far from home it stops during Magnetic field 69 Love Songs says no Roon Radio available happened about 7.30pm GMT. It then won’t play a thing and has issues connecting. PlexAmp on same network to same phone and on a different server machine works fine so it’s not my network.
I know I am not the only one this happens as others have commented in other threads this is something that seriously needs looking at what the cause is. One factor that seems to be consistent in my case is that it’s been used for long periods of time in one sitting do we have a memory leak with the transcoding engine? And it’s always when on cellular.
To add a data point to the support request…
The same thing happened to me four times in the last two weeks. Since last March, when I went abroad for more than a week, I never experienced any problems with Arc, but suddenly connection problems came up that also caused problems to Roon Server.
All four incidents happened on the train while commuting. And all four times it happened on the way back. I always listen to playlists that consist of different tracks from different albums that are either from Tidal or local. These local files are always downloaded to my phone.
In the morning on my way to work, I have no problems at all. But on the way back several hours later, each time while switching to a new Tidal track, Arc says it has difficulty connecting to the core. After this, I can only play my downloaded files.
And at home, in Roon Remote, I only get a dark screen. Restarting Roon Server solves the problem.
Edit: I noticed that after the bad connection issue, Arc still communicates its play history. After having restarted Roon Server, my history showed all (downloaded) tracks that were played on Arc.
@Will_Moore already referenced the other thread and maybe it is best to keep all discussions around this issue in one thread.
But this is quite interesting. I could not distill a pattern honestly. Sometimes it happened within 30 minutes of ARC playback. Yesterday it only happened in the afternoon after I listened to ARC throughout the day multiple times.
Thank you for the report. We’ve investigated available logging with development - while there is an identifiable connectivity issue here, there’s strong evidence in diagnostics to suggest it’s a known situation that the next upcoming production release of ARC should resolve or at least improve.
These changes have already gone live for testing in #earlyaccess - if you switch your Core and ARC to the EA branch to test the beta, we’re curious if this will help. It’s obviously up to you, and the production release should be released relatively soon.
I updated core and Arc yesterday to the latest (non early) versions: 1303 and 209 respectively. But still, while playing a playlist that consists of both local and Tidal content, my core becomes unresponsive the moment Arc loses connectivity. This happens when a local (downloaded to the phone) song has ended and a Tidal song comes up in the queue while I my phone has no connectivity (in a train in a tunnel).
It happened again at about 17:08 hours local time today, while switching from ‘Sueño feliz’ to ‘Quintessence’ in the playlist below:
I’m wondering what the latest update on this is. I have been struggling with what appears to be the same symptoms for a few weeks now. I now find ARC unusable. I am in the EA program and currently have 1310 installed on Debian and ARC build 207 on my iPhone 14 Pro Max. I have with my limited skills looked through the log files at the appropriate date/time stamps and could not see anything that made me think it indicated relevance.
I just knew this would be happening: an announcement was made for an Roon update, and immediately Roon Arc would struggle to work. It can’t connect to my core, probably because of an update of my core that is waiting. This is not the first time this happened.
Luckily, I can still play files that are downloaded to my phone, but everythng else stopped working.
Arc says it cannot connect because a backup is running. This cannot be true.
