Thanks, Edwin. I’m waiting for a reply from @andrew.v on the logs which I sent in. Things do seem to have improved in the meantime 
I confess to being a little disappointed here.
I’ve written several times to @andrew.v without receiving any reply - even to say they’re still investigating.
It’d be good to know whether the logs which I sent in over a month ago proved useful.
Is/was it something in my Library? Or a fix on RoonLabs end?
I do appreciate that the techs are busy; not a complaint.
Maybe someone else on the tech support team (@vova? etc ) would kindly take a look at this, please?
Thanks in advance!
Hello @Mark_Sealey ,
Apologies for the delayed response here, there’s been quite a lot of activity happening behind the scenes, and your case is still pending further review from the team.
With our next Roon release, we have made quite a lot of changes under the hood to the way Roon handles certain library operations, and I am hopeful that it may help clean things up the issue in your case as well. If not to fully resolve the issue, at least to make the logging clearer on where the stall can be coming from, as the logging is a bit inconclusive at the moment.
Please, let’s come back to your issue when the production release is published, or if you would like to test these changes even earlier, they are already available in our Early Access builds (to test you’d need to create a Backup, switch to early access as per guide and then restore the backup to test against the new behavior - early access testing is optional):
If you decide to load up early access, please let us know of any new observations regarding the issue, thank you!
1 Like
Thank you very much, @noris!
That’s good to know. I will be patient.
Good luck with all these changes.
Just to be clear, though, the phenomenon appears to have stopped BY ITSELF 
I just like to find out why.
Hi @Mark_Sealey,
Apologies for the long delay in following up! We wanted to check in and see how things were going after the last few updates. Are you still seeing any oddities with audio analysis speed?
Thanks!
1 Like
Thanks to you and your colleagues, @benjamin 
No! The analysis seems to be completing every time.
The odd thing, though, is that I was first able to confirm that my version of Roon was working as intended between updates.
So I put this down either to something which you did on your end (after seeing the logs which I sent you in February). Or to some other process which otherwise cleared the state.
As a Roon fanatic ( !) with a lifetime subscription and so a great deal invested in the system, may I ask you to let me know (if you can) what changed?
If not, I still appreciate your work and help here!
1 Like
Thanks for the update @Mark_Sealey!
I don’t believe any concrete changes were made in this area, I wish I had more information to share!
None the less, I’m happy you’ve got your library back to normal - happy listening! 
1 Like
Thanks, @benjamin Benjamin - but unfortunately - by sheer co-incidence - I seem to have run into the same phenomenon again.
Possibly as a result of this.
Can we re-open and look into this again, please?
Logs?
Hi @Mark_Sealey,
Sorry to hear this! Within your local library, roughly how many various artists do you currently have?
That could also be the case. If you temporarily move your recently edited boxsets to a disabled watch folder, do you experience the same issue?
I’d make a fresh backup before anything else, just to be safe. 
1 Like
Hello again, Benjamin - and thanks for being on top of this… I know you must all be working 24 hours a day; and it’s much appreciated!
640
I do, Yes.
However - I have discovered that if I quit Roon (build 1407 on macOS 13.6.6) and stop the Server from the web interface; then restart both in the reverse order the phenomenon seems to go away .
May I ask you to confirm that this makes good technical/coding sense to you and the team, please?
That is to say: could there be a cache somewhere which is both causing the phenomenon and which gets cleared upon such a restart for the server?
Secondly, may I ask you to review that thread and advise: now that I’ve changed all wrongly-named individual CDs to ‘CDn’ without a space, will Roon have somehow taken care of all those box sets which I’d Merged?
Thanks again!
1 Like
Hi @Mark_Sealey,
I’m glad to hear it!
As long as you aren’t naming albums “CD1” and “CD2”, etc. into separate folders that are also named “CD1” and “CD2” you should be fine.
Here’s more info on this from our KB:
Here’s an example from the KB:
Roon would reanalyze anything it doesn’t recognize when it scans. So anything changed outside of Roon will get treated as a new object, which could again slow you down. Making your changes within Roon vs the original files will likely save you any headache in this area. 
I’m sorry that I was not clearer in my post replying to yours.
In fact, it’s still in need of two answers, please:
- Would you and/or your team kindly confirm that - from a programming point of view - you would expect the bug where audio analysis stalls to go away if I quit Roon (build 1407 on macOS 13.6.6) and stop the Server from the web interface; then restart both in the reverse order? Another way of asking this: does the very act of restarting Roon’s server somehow clear the stall?
- As described here I’ve changed all wrongly-named individual CDs to ‘CDn’ without a space; previously I had Merged them. Now will Roon somehow take care of all those box sets which I’d Merged?
Thanks in advance for your(team’s) clarification!
My reason for pushing the point, please, is that I have a lifetime subscription and want together as close tubes practice as possible - even if it takes a day or two of consultation with the developers etc.
Hi @Mark_Sealey,
Your issue was likely due to a regression. Restarting Roon will result in Roon picking back up where it left off in regards to analyzing files.
I can’t speak on behalf of all of your specific Box-sets of course, but if Roon is given the proper information then you should be fine. Again, as long as you aren’t naming albums “CD1” and “CD2”, etc. into separate folders that are also named “CD1” and “CD2” Roon shouldn’t get confused. That said, manual editing around box sets is common.
Hello again, @benjamin; thanks for your encouraging replies.
I do hope you are sympathetic to my wanting to nail this right down to the last detail: like many (most?) users, I have a great deal invested in Roon and want to get things as close to ideal as possible
I hope you and your team may have the patience to pursue this with me for a little longer, please. Because, Yes, after a restart Roon (almost) always appears to stop analyzing.
But my concern is that, typically it shows something like ‘339/553’ before analyzing; and displays no evidence of picking back up (where it left off) after a restart of the server.
In other words, no analysis takes place after a restart.
Is that what you’d expect?
Is the act of restarting actually curtailing analysis? Or is this just a cosmetic bug, as has been suggested by other users?
No; understood
I’m now naming correctly. In the says you indicate to do (and not to do!).
My concern is that I have previously merged.
So will the very act of renaming correctly unmerge?
Thanks again in advance for your teams’ attention to this!
Any movement from the developers on this, please, @support ?
Just to be clear: there are still times when I make changes to the files on my Nucleus - with the server stopped - and on relaunching the Roon app, the audio analysis stalls or appears to stall:
This condition persists no matter how long I leave it to try and finish.
Again, a server restart appears to clear the stall.
A developer’s informed perspective on this would be most welcome, please !
Hi @Mark_Sealey,
From a fresh diagnostic report, we’re seeing frequent error traces in relation to Time Machine on the iMac. Do you have Time Machine actively running on the Mac? If so, it’s known to cause issues alongside Roon. Is Time Machine touching the same local library you have set as watched folders?
I’d be curious to see if disabling Time Machine may help you with finishing the analysis. Here’s a good discussion around it: MacOS Time Machine Question - #2 by Robert_F
Renaming should allow Roon to process each track as a new object, therefore removing any previous edits made within Roon. You can perform a library cleanup to remove any old traces as well. As long as Roon see’s the updated tracks as new objects, they will appear unmerged.
Hi @benjamin; thanks for your reply!
In reverse order, if I may:
Fantastic! Just what I’d hope you’d say. Thanks. Understood.
Using Settings . Library > Library maintenance > Clean up library ?
I do that often - but always get 0,0,0 - so it looks though I have a ‘healthy’ library, doesn’t it? Thanks for the re-assurance!
== stalling ==
Thanks for taking the time and trouble to do that!
I do, Yes.
Even though they’re separate Volumes, and even though the Nucleus device/volume is specifically excluded from Time Machine?
No. Not at all.
My local library/watched folder is on my Nucleus (Linux/roonOS).
Time Machine only backs up from Macintosh HD (macOS).
Could it be that the very act of having the ‘Internal Storage’ directory on my Nucleus specifically ‘mentioned’ in Time Machine’s options may be causing the errors, Benjamin?
Thanks. In the foreseeable future I’ll make sure that TM isn’t running while I make any changes.
I’m still unsure, though, please: when I restart the server (via the web interface) and any sign that the analysis has stalled goes away (IOW, no indication of ‘x of y files’ being processed), does that mean that the apparently hung/stalled analysis has:
- really completed and the error suggesting a stuck process was cosmetic; and so all the analysis has actually run its course, or
- that analysis has been interrupted and left incomplete by restarting the server?
I look forward to your advice here, please!
Have been experimenting extensively with the apparent audio analysis this last week.
Specifically, I’ve been avoiding any possible contention with a Time Machine run.
TM is set to the default, every 60 minutes.
Here’s an example.
- I stopped my Nucleus server via the web interface
- waited several seconds until that had time to ‘settle’
- renamed a half a dozen or so folders in my watched folder; equivalent of importing
- waited a minute or so again
- started the Nucleus server via the web interface
- waited several seconds until that had time to ‘settle’
- launched Roon
- watched progress in Library > Background audio analysis speed
It seemed to finish. But then this:
I hope it explains the issue better. And confirms that Time Machine is not involved.
No actual error messages.
Happy to help with further testing, logs, experimenting etc.
It would also help to know, please: when I abort the Background audio analysis with Library > Background audio analysis speed > Off (because of the (apparent?) hang), and then either restart the server and/or change back to Library > Background audio analysis speed > Fast (4 cores), can I assume:
- that analysis has completed?
- or - if not - that it may somehow pick up again and complete?
- that the bug is cosmetic?
If #2, how can I force it to complete?
I look forward to the results of your team’s investigations, please.
Hi @Mark_Sealey,
Thanks for your patience so far! Your ticket is still in the queue for review, I hope to have more actionable information to share soon.
You should be safe in this instance, like you mention having Time Machine ignore all associated Roon folders and vice versa shouldn’t result in any issues between the two.
Since the only place it’s mentioned is on the exclusion list, I think you’re safe to that regard.
This is the big question - and something our dev team will need to investigate a bit further.
1 Like
Benjamin,
Thanks for that update; it is much appreciated!
Looking forward to that: I hope I can help in some way by providing more data if you need it. Standing by… .
That, in some ways, is the crux of this - and what concerns me most.
Thanks - and looking forward to hearing back from you sometime soon!