“Can this be fixed in the next release or is there an existing process to do this.?”įirst, if this hasn’t been fixed, using Roon for detection and then deletion doesn’t appear to be as functional as the size of my library would dictate.Īny suggestions/observations would be much appreciated… “With 12,000 albums this means I have to scroll through my library to find the place where I did my last edit. Or, before creating a Core, would you recommend doing the “cleaning” off-line from Roon, using other software or media players? If so, what Windows based programs have you to be best?Ĭonduction a search here I found the following from May/2017:Įditing and deleting of duplicate albums – “When I am editing albums and delete a duplicate within the Roon I am returned to the first album in my database.”
What is the most accurate and expeditious method to ID duplicates and then delete them? Use Roon to do this? If so, what instructions might you suggest? So, just among the different bit-rates, there are going to be inherent duplicates. Especially considering that: 60-70% (approx.) of our library is 16-bit. So, the effort is going to be significant. We began ripping over 20-yrs ago – & even within our own libraries we have duplicates, so they will be profuse! We’ve both ripped similar and different albums.
My son and I would like to combine our libraries.
0 kommentar(er)
