I’ve just tried it. Oddly, it couldn’t find quite a few tracks (10%) when exporting the playlist to Qobuz. I say oddly as the tracks on the playlist were all from Qobuz so the solution works but isn’t perfect.
That means - the export function is not working as designed - or the import function is not working as designed
@zenit or other staff folks,
Definitely a big day for everyone at Roon - congratulations. However, any chance we can get an update on this issue? Is it now known and being worked on? Is it not prioritized? Is there no way to roll back to a previous version? Are there known causes that we could remove (I’m noticing a number of the people with issues are using Qobuz maybe?) to make Roon useable? Rebooting twice every 15 minutes doesn’t seem viable for very long.
4 Likes
I apologize for the silence. We’ve been actively working on the search slowness issue, particularly with large libraries. There are a few optimisations ready, but it needs to go through QA before we can determine a fix date.
The first time you did a double restart was sufficient to revert the search to an older version, so any issues that you have now seem to be rather related to some other changes in the latest update. The fixes mentioned above are unlikely to help your issue, but only OP’s. If you can, please open a new support case and describe exactly how/what/when is slow for you so that we can at least try to reproduce it. Please let me know if you do.
5 Likes
I hope an upcoming fix does not only adress the search slowness issue (and it is very very slow indeed, the double restart provided only a temorary fix). There are plenty of other issues with this build. I’m not happy to say I involuntarily reproduce daily all of the issues noted by OP Ronny, Nicola_Sforza, Jens_Lagerqvist et al: playback suddenly stopping, losing contact with all Roon Ready endpoints, complete rescan of the entire library, endpoints coming online again, sudden restart of playback, all search functions (artist, album, number) taking up to minutes to produce results. In short: Roon is pretty much useless right now.
21K albums
309K tracks
Qobuz
4 Likes
Thank you for your feedback - now we know, ROON is aware of the bug.
Is it for your teams not possible to reproduce the slow system?
Sorry, but during working time, it is not possible to get all data.
So i have to wait to be at home again.
And on the other side it takes plenty of time to report exactly all behavior inclusive testing and reporting - and again - testing and reporting.
I am sure, you will also have slow systems in your teams to check it out - hopefully.
There’s a bunch of ways how roon can be set-up, with various endpoints, libraries, streaming services, and configurations. Our QA team has lots of setups ready, but it seems that this particular issue has still slipped through, despite the very long testing process of the last update. That’s why it’s helpful for us to know what the prerequisites are and where to look at.
I work on search, and can probably help with that, hence why I’m responding in this thread, but other devs might be more helpful for the general slowness you’re experiencing. @jager has opened up a new thread regarding the slowness - if you do have the same issue as them, please describe your setup and issue in there. I’ll make sure someone has a look at it.
2 Likes
There are probably tens of threads opened about various kinds of slowness apart from search that people opened after the update reached everyone shortly before Thanksgiving
3 Likes
Yes absolutely! I think it would be best to “unify” them and investigate this further, rather than letting users just open up new ones. Or some are already irritated about opening up a new one as there are numerous already existing.
1 Like
I dunno, Roon must decide. Who knows which ones of these threads have the same cause and which ones just the same symptoms but different causes
1 Like
I must be one of the few, where with 1353 I do not have any issues with search, it is almost instanteneous, there is no percieved delay.
But I do have other issues with Roon Remote loosing connection to the server stated in other threads on the forums.
I have both and I don’t have a large library.
3 Likes
This slowness issue still hasn’t been resolved even after the x2 restarts (I should NOT have to do this)
Please issue a repair asap for this as its never been this slow!
1 Like
ROON is no more able to find songs within 2 minutes - even after reboot.
It is now even worse
HOW TO STEP BACK TO A VERSION THAT IS WORKING?
Is therefore any tutorial - how to step back to previous version?
The email newsfeed from yesterday: Roon enters a new era, software enhancements, new gear and more!
Is a little bit of kidding
I can understand, that roon cannot fix it, but i cannot understand, how to get a procedure to step back to an existing STABLE function.
2 Likes
I now disabled ALL STORAGE FOLDERS
Settings → Storage → disable each storage folder
NO lokal music is now in Database
Only Tidal and Qobuz
And it is working fine again.and FAST
So there seems to be a problem with lokal Storage and the size of lokal storage of music
Can anyone confirm this behavior?
This info might be useful for the roon-team.
1 Like
I think you are seeing the same thing as many others, inconsistent search performance…
I waited 30 seconds for the return of search for “the the”, while 5 minutes later the return of results for “led zeppelin” was almost instant. (local lib of 200K tracks, some 5K from Qobuz in library)
Interesting though is that the “search hints” for The The are reallly slow, whereas the hints for Led Zeppelin are very much quicker?
Things are getting worse and worse. And it has wider implications than a simpler search:
- many searches won’t show the first results before 30-60 seconds, unbearable!
- 3 out of 4 times Roon Radio fails to kick in when a song ends
- Playlists with only local songs stop randomly
Please fix this issue.
I fully understand everyone’s frustration with a software which used to run smoothly causing such issues from one version to another. Although, I refuse to believe that this happened due to neglect or indifference from roon´s technical staff side. It does not make sense to release such a version risking tons of frustration among loyal users.
It sounds much more likely to me that a software version has been released completely shifting the balance of requirements for network capabilities, computing power, cloud integration and alike but working fine under the majority of individual environments. While the sheer number of individual configurations might reveal some being not capable of keeping up with new requirements for whatever reason and collapsing. Some might want to blame roon staff for not doing enough of field testing before releasing this build. But let us be honest - one cannot oversee all the different machines, network scenarios, storage capabilities, streaming service quality and alike.
I sincerely hope things will be fixed for everyone soon, keeping fingers crossed!
3 Likes
And different usage patterns, I assume. I don’t use playlists, listen to whole albums, clean my queue, etc., and this new release works more memory-efficient than ever. Apart from a slightly slower search performance, in my case it has been a successful release. I’ve seen other user’s comments that to me suggest that the patterns of using Roon may have a noticeable impact on performance.
This isn’t tied to library size and I feel its more than the cloud, as I am experiencing different slowness, search is slow but not as slow as some report, but other aspects are slowly getting worse. Now switching a queue to another zone is taking time, adding material to my library makes the machine unresponsive and has severe delays in instigating playback when its analysing which its never had problems before. Also the analysis is noticeably slower. Feels like another memory leak of some kind as its got progressively worse the more I have uses the machine, Might reboot and see if it clears up anything.
1 Like