HM... I have that off because i have an SSD for windows and it is fast enought for that service to be disabled and don.t have problems on win 10.
Hope others can confirm that as a workaround. Nice tip.
Hi all, I had a problem with Rekordbox DJ being so slow and unresponsive. I tried loads of ideas, but what worked for me was turning off Windows Indexing for searches in windows . If you've got the same problem, try that. Windows>Control panel>Indexing Options
Post is closed for comments.
HM... I have that off because i have an SSD for windows and it is fast enought for that service to be disabled and don.t have problems on win 10.
Hope others can confirm that as a workaround. Nice tip.
i just tried turning off ALL of indexing checkboxes, there was no entry for windows search, but my the results are exactly the same. there is no change and the software is thoroughly taxing my laptop. the software is not usable.
iggy, did you RB issues start with 4.1?
When you start RB and start playing a song, is there anything using too much CPU. Does the laptop start swapping (using page file) because of not enough memory?. Can you try with the AV disabled (AV's sometimes mess with apps)?
My laptop is an i5 2.5Mhz with 6Gb of memory and hell I'm even using my ddj-sb2 connected to a USB hub (ok, it is powered but still..) and I just finished a 50m trance mix using .flac files
0 hickups (but i'm using win10).
I'm reading from an external HDD (7200rpm btw) connected to a USB3 port and recording the mix to there too.
I'm writing this so you guys have a reference only.
BTW, it is not recommended to have you storage devices full. I'd say more than 80% capacity is above limits to be safe.
That being said, RB does need a bit of optimization wrt to CPU usage which reminds me, make sure your drivers are up to date and for those with nvidia make sure you install the latest ones if you updated a couple of weeks ago because they cause issues in some cases.
also running on an i5 with win7
Hi Bud, yes it did. The other thing I tried before that was re-analysing all my music. took about 48 hours!
i finally got v3.3 and tested it on same machine, with video proof and the same tracks too