Pretty sure this is coincidental and not build version related @Uwe_Albrecht .
| 05/22 15:20:40 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
|---|---|
| 05/22 18:42:56 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/22 20:46:59 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 06:51:09 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 12:07:07 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 13:28:36 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 14:07:25 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 15:07:36 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 15:19:02 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 16:04:38 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 17:29:08 | Info: Starting RoonServer v1.8 (build 943) stable on linuxx64 |
| 05/23 19:21:32 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
| 05/23 19:32:44 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
| 05/23 19:36:44 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
| 05/23 21:15:32 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
| 05/24 06:04:41 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
| 05/24 06:13:17 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
| 05/24 08:42:20 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
| 05/24 10:05:30 | Info: Starting RoonServer v1.8 (build 952) stable on linuxx64 |
It fits exactly in time and before and after give clear differences in connect.
|05/22 18:43:03|0ms last in 943
|05/23 19:47:48|46340ms first in 952
iOS app is crashing after a few clicks or several seconds.
I already reported a bug: https://community.roonlabs.com/t/roon-remote-app-crashing-on-ios-build-952/202299?u=henrik_lampe
1 Like
There is also still work for the team here. When the Wine GUI is started first on Linux, the non-playable WASAPI/ASIO devices of the Windows world come up. Linux devices are missing!
A systemctl restart roonserver does not fix the problem.
Restarting the PC helps, but then the Wine-GUI can only be started without errors after a complete rescan of the external hard disks. Waiting longer for working solutions gets annoying sometimes, although I know patience is the art of life.
I’m noticing some weird things since this update. When I try to rescan a folder, it just hangs up saying “scanning” and then I lose connection and the core reboots. Just odd.
I started a thread about my Lenovo tablet here, because Roon is now much darker after upgrading to 952 than it previously was.
Before:
After:
as does mine
Could this be affected by the Samsung dark screen changes they put in the new release
I suspect it does. It used to look this way before but then it was fixed. Now it’s gone back to this darker version.
I see the user’s in the other thread confirming that it has been fixed for their device’s, so let’s hope that they can add others as well.
Play Now within existing Playlist greyed out. Newly created playlist woks fine however.
Reconnect times are much improved on iPad 12.9 3rd generation & iPhone 13 
2 Likes
I discovered that bug as well. While the main Play button at the upper right is now non-functional, I still can play the playlist using the play buttons next to the songs in the playlist. The playlist will play as normal.
Still having issues since upgraded to the latest version on my core and remote were after adding what seems a random amount of albums via Tidal, Qobuz or my own music it seems to get stuck were I have to close the remote and then open again to continue adding albums.
I have tried deleting the db’s for the core and remote, still having this issue. I have tried to delete everything and starting totally afresh and it is still doing this issue. Not sure what else I can try to get this resolved as is bugging me.
Search not working since last update. Just get the spinning roon icon. Have tried rebooting the core as well as ipad and android. No dice. Not a network problem as I can search no problem locally or Qobuz with other apps like Lumin and Linn.
Search works fine here. I do however see that remote UI stops responding regarding search, play etc (seems to happen when remote app is active over a long time) - closing roon remote and starting it again will fix this.
Not for me it doesn’t. Closing roon remote and even rebooting remote devices has no effect. I’m seeing similar reports in the support forum so I guess it’s a known issue with some configurations.
Could be connected to specific regions in the world (I think Roon is hosting their services on Google cloud-platform).
I’m located in Norway - no issues here.
wow, i have never had issues like this before. (well, I had that database issue a few updates ago, I guess)… but this is nuts.
I’ve always been surprised by how smoothly my Roon experience has been, but now it’s dropouts galore. “Roon lost control of the audio device” etc… This is all happening since the latest update. Maddening.
WHAT DID YOU DO
Multiple dropouts with this build. Even music on internal drive skips. Tidal and Qobuz only go for seconds before stopping. Restarted everything including router without resolution. Able to stream using an alternative app to my speakers with no issues.