[CLOSED] Very long track load times with mp3's

@Kube > Have you tried a higher quality flash drive?  I presume you're running your tracks through rekordbox?

i don't think it's the flash drives, because they are different, but the "rogue" files are the same on both of them so it doesn't depend on the flash drive's  speed, i'm guessing it has something to do with the way rekordbox saved the track in the playlist.

i  noticed another thing: if i access the track that takes so long to load and then go back in the playlist and access another track that is 2 or 3 numbers above or under the faulty one, after i reselect the long loading track it loads normally, like the rest. but if i select any other track that is 5 or more numbers away from it in the list and then back, it loads in 20+ seconds.. don't know why it happens...

I'm opening a ticket with the engineers, I'm sure they'll have more questions for you.

Thank you, I hope we can get to the bottom of this.

@Kube > Since engineers might want to take a look at rekordbox DB in the USB memory, please keep it as is. 

-Use another USB memory, format it, do the export again, and see if the symptom still occurs. 

Please do not store anything in the USB memory other than files exported from rekordbox, e.g. documents, pdf files etc. 

-Create another playlist which only contains the faulty track plus five tracks before and after it in the same order as the original playlist. 

This way, he now has a new playlist which contains 11 tracks. Export it to the formatted USB memory, and see if the symptom still occurs.

Please let us know the results from the above experiments. 

Also please let us know the following about the original USB memory: 

-How many tracks are stored totally in rekordbox? 

-How many playlists are stored? 

-How many tracks are in the faulty playlist? 

-How the faulty playlist was created, e.g. added tracks, deleted some tracks, and renumber tracks, and repeated these many times etc.? 

-Make of the USB memory and the size.

Thanks

This topic has been closed due to inactivity. Should you require future assistance with this issue, please create a new topic describing the problem and provide the URL of this topic as reference.