Official comment
I have over 53K songs and it takes about a minute to load my rekordbox library on a 2019 MacBook Pro, so yours taking a minute on that computer sounds about right.
Good morning to all of you.
I installed Rekordbox version 6.4.1 on my MacBook Pro 13 early 2011 with a 1TB internal SSD and 16GB of Ram.
I understand it may be a bit outdated as a computer.
My music is all located in the MacBook SSD.
I had all about 50,000 songs analyzed by taking them from Itunes and it took several days to have them all analyzed.
Does it also happen to you that it takes more than a minute to load the library? It seems to me a little too much time.
When I load a track on the deck I notice a certain lag in loading the waveform and in addition when I put the padlock on a track the classic umbrella appears that starts spinning making me understand that it is doing a demanding operation. I also use Djay Pro 2 for several purposes. The library loads it for me in about 15 seconds and when I load the track on the deck it has no lag in loading the waveform.
I thank all of you in advance for all your advice on this matter.
I have over 53K songs and it takes about a minute to load my rekordbox library on a 2019 MacBook Pro, so yours taking a minute on that computer sounds about right.
Post is closed for comments.
Thanks Pulse for your quick reply.
When I had installed Rekordbox 5.8.5 I was able to open the library in just over 20 seconds always with 50,000 songs and I had no lag problems in loading a track.
Now with the latest version of Rekordbox 6.4.1 it takes much more than a minute to load the library and I have lag problems when I load a track.
My nephew has a MacBook Pro similar to mine and a library of around 45,000 songs. It opens them in just over 20 seconds and has no lag problems when loading a track.
Mine is annoying and slow to use. I don't really know how to fix.
I want to clarify that I have everything disabled, video lyric, Dvs etc.
Thank you very much for any of your advice on the matter.
There could certainly be something in the database causing this issue; please file an inquiry ticket here and mention topic 900001862726 in the description, ask that it's assigned to me. I'll escalate it to our rekordbox team and get some additional info to troubleshoot.