M1 CPUs require a 30 minute "break in" period for the CPU's machine learning to understand how rekordbox handles the system requests. Have you just left it to run on its own?
I've been using RB 5 in export mode only for years. Never had a problem. I do use link mode with my CDJs and XDJ-RX. I never updated to 6 before because my old mac didn't seem to be able to handle the conversion of the library. I tried multiple times, would let it go for 24 hours and would only ever make it to 30% complete. Fast forward to this November. I finally updated the computer to the brand new M1 Macbook Pro. It made very quick work of converting the library and reanalyzing for RB6. HOWEVER. RB6 is so dreadfully slow to use. I continuously get the spinning beach ball, and constant freezing. Even removing a song from the database locks it up for upto 30 seconds. It's completely unusable while importing anything. So if I wanted to import a song for a request I have to wait several minutes before I can browse or select my next track. I decided to try the unsupported RB5 on this brand new computer and WOW! what a difference. A program that wasn't even designed to work with the latest OS or processor is spanking the brand new RB 6.6.1 in every performance metric I need. We've spent $1000s of dollars on gear lets get the software usable shall we pioneer?
Post is closed for comments.
M1 CPUs require a 30 minute "break in" period for the CPU's machine learning to understand how rekordbox handles the system requests. Have you just left it to run on its own?
As in leave it without touching the computer or doing anything in the software? No I haven't done that except when it reanalyzed the library for RB6. I've probably logged close to 10 hours. Between the several hours it took to convert the library, regular prep work, and the 5 hours I was running it at a show last week. When I converted the library I left it alone for the duration.
Try leaving it open and doing nothing for about 30 mins and if you still have issues, please file an inquiry ticket here and our support team will gather some additional information to assist you in resolving this issue. Thanks!