Re-exporting a changed file to USB requires a complete removal from collection & re-import

Re-exporting a changed file to USB requires a complete removal from collection & re-import

ben.english

Re-exporting a changed file to USB requires a complete removal from collection & re-import

Hello,

I have noticed a very odd workflow issue a while back and now it has come to be a problem.

If I change my file e.g. C:/Users/Ben/Music/My_Track.wav from 24bit to 16bit, I would expect to be able to re-import said file to Rekordbox and then have the new file re-exported to USB.

However, re-analyze does not update the file properties in the database and does not re-export the file in its new shiny 16bit condition to the USB either. To do this you need to completely remove it from the collection and then re-import it and THEN you can re-export the track to USB.

Why is this? In my mind you should be able to re-analyze the entire file and its subsequent properties, file size, bit depth/rate etc. with some kind of re-import option and update the underlying database.

I am using rekordbox 5 btw, not sure if this feature is in Rekordbox 6?

// Ben

Official comment

Pulse

If the filename / path doesn't change, then that's an issue. rekordbox identifies it as the same file, says "Hey, I have that suff in my collection already, and it's been exported before."

We do not recommend replacing existing files; bring it in as a new file instead.

1 comment

Sort by: Date Votes
Post is closed for comments.

Sign in

Can't find help? Search our Support Site or alternatively, reach out to our Support agents