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

Post

2 followers Follow
0
Avatar

Rekordbox Cloud Sync Made Multiple Songs Point to Same File

I recently upgraded my rekordbox plan to get access to cloud sync. I selected "copy files" instead of "move." Now it looks like any of my songs that have file paths that are too long have been truncated. This resulted in songs that have similar names pointing to the same file: E.g "Kiss Me Thru The Phone (Quick Hit Clean)" and "Kiss Me Thru The Phone (Intro Clean)" both point to "~/Dropbox (Professional DJ team)/rekordbox/contents_2084414516/soulja boy ft sammie/isouljaboytellem/soulja boy ft sammie - kiss me thru the phon.mp3". Rekordbox still shows different file sizes, but the songs have the same cuepoints and waveforms. When I play one of the songs, it also shows the "currently playing" icon next to both of the mixes. I have a backup of the song files but I've added over a hundred songs since I last did a database backup.
I saw a few forum posts from a while ago where Pioneer Support claims that this issue has been fixed in 2020, but it looks like it hasn't. How can I fix this without losing all of my metadata/cues/etc.

Screenshots: https://imgur.com/a/0DvBJmf

Old Forum Posts:

https://forums.pioneerdj.com/hc/en-us/community/posts/900001406426-Recordbox-cloud-deleted-my-files 
https://forums.pioneerdj.com/hc/en-us/community/posts/360062572692-RK6-is-deleting-different-versions-of-songs-on-cloud-sync-BUG-

 

(Note for support: I made a support ticket about this issue yesterday because I was having issues logging into the forum)

Ryan Ramsdell Answered

Official comment

Avatar

The support team will assist you with this through the ticket.

Pulse
Comment actions Permalink

Post is closed for comments.

2 comments

0
Avatar

I saw a few forum posts from a while ago where Pioneer Support claims that this issue has been fixed in 2020, but it looks like it hasn't. How can I fix this without losing all of my metadata/cues/etc.

Looking at the second link it seem the suggested "fix" is to manually relocate the files after renaming them. This is a pain-ass job.  

I wonder if this is related with the issue currently effecting relocate in 6.6.9. and 6.6.10

Ves 0 votes
Comment actions Permalink