Have a feature request or suggestion? Post your idea here!

Post

2 followers Follow
0
Avatar

Auto-Relocate for Tracks with Same Title

I've been having an issue lately where the cloud library sync caused some problems with my folder locations. The original file paths randomly changed to look for the Dropbox file location on my computer, which is simply a backup and on another drive.

I didn't think too much of this because I've been successful using the auto-relocate feature in the past. My plan was simply to use auto-relocate and find the original file locations that never changed from my C:Drive. However, when I went to auto-relocate in bulk (most did relocate), there were a number of tracks that simply wouldn't relocate stating that the "track already exists in collection." I investigated further, and I noticed that the tracks Rekordbox were stating were "in the collection already" were simply completely different tracks with the SAME TITLES but DIFFERENT ARTISTS. Additionally, when I do a manual relocate to the separate files, it still errors out saying "track is already in collection."

The only fix I have found is moving the missing files out of the original folder and back in, then (only with manual relocate mind you), does it work. I currently have 151 missing files and do not have the time to do this with every one.

 

What can I do here? Also, why did my cloud library sync screw this all up to begin with? I want to backup to the cloud to have cloud-based security as well as a way to pull files to my laptop for mobile use. However, I'm scared that every time I backup, all the original file paths are going to move and this issue will happen all over again. I even tried to use selective sync to stop the backup to my other drive in Dropbox, and it still disrupted my file paths, and now the 151 tracks with same titles is just adding insult to injury when I have found a partial fix just to return to my status quo prior to Creative Subscription.   

 

Thank you for any help you may have with my issue.

Jonathan Venegas

Official comment

Avatar

Hey Jonathan,

The files are matched by the filename. If you had two songs which were the same filename, they could both be in the collection provided the path is different. If you had one "go missing" and then tried to relocate it, but instead of it finding the original, it found the other song, and that song was already in the collection (not missing), it would say "Already in collection" and not allow you to import it a second time.

The best resolution for you is to determine where those missing files went and either remove them from rekordbox and re-import them from their new location, or relocate them manually.

Pulse
Comment actions Permalink

Post is closed for comments.

Date Votes

2 comments

0
Avatar

Oooof. That's rough. And you are right. That ended up being my workaround. I found hundreds of missing songs with the same title 'connected to the wrong artist.' I had to go through one-by-one and move the song that was supposed to be correctly labeled in Rekordbox outside of its original folder, then manually relocate the twin song to its unrelated file, then move the file back into its original folder, and then auto relocate the track I needed to fix to start. This was bonkers! 

 

I guess what frustrates me is the system that got me into this mess to begin with. I was under the impression that when I chose "copy" instead of "move" that I would simply be placing a backup of my library in the cloud that would only be called upon if I needed to 'redownload my whole library' or 'grab a particular track/playlist for my mobile device.' However, when Dropbox made a local file on my computer, this TOOK PRECENDENT over all my original file paths. Why would it default to do this automatically without asking??!

I know this is true because when I right click on a file and click "show in folder," Explorer brings up the 'Dropbox local folder' and NOT my original music folder in which the song originated before uploading to the cloud. Moreover, I tested single tracks by "returning to local storage" and when I "showed in folder" after this, the file path showed "the recycle bin" instead of the original folder. 

This became a huge issue prior to me knowing about 'selective sync,' because I simply deleted the Dropbox local folder because I only needed files in the cloud and didn't want to take up extra space on my computer. I already have a backup on another drive as it is.

Moreover, before deleting the backup, I tried "online only" sync, and the files STILL auto locate to the Dropbox location and not the original folder. Why would this be the case for online only?? Seems very finicky for the software to do this by default when 'online files only' have metadata on the local drive and call on online access for use (if I understand correctly). 

 

All this being said, this seems like a giant bug for the Creative Plan cloud sync that could disrupt things for a lot of users. If this disruption never happened with my original files, I never would have had to auto relocate my ENTIRE library and deal with the duplicate titled tracks. 

 

To date, my issue is fixed because I simply adjusted the hundreds of tracks manually, made a library backup after, and then deleted my alternate local backup to simply use the one that Dropbox creates on my drive (I removed the selective sync to allow local storage). Similarly, I deleted the main library on my laptop and just use a local storage from Dropbox since I don't have the drive space for two. 

 

This fix is all fine and dandy for now, but am I going to have to deal with this all over again if I ever have to lose the Dropbox and Creative subscription and go back to my original library? Good luck with the auto-relocate! Granted, I know better now and will make a library backup before that happens.  

 

Just want to share my struggle to see if perhaps, I am missing something in my workflow, or maybe, something can be done here to save people headaches down the road. I know this feature is new and may have bugs but all and all, I'm happy now that I have a workaround. 

Thanks for your quick response. I really do appreciate it!

Jonathan Venegas 0 votes
Comment actions Permalink