Adding other slowwwww moves:
-
Just launching sync manager: about 3 minutes
-
Then syncing 2 smartlists to drive…
It took more than 15 minutes!!! Engine DJ seems to be calculating (12% CPU) with almost no disk access (< 1%).
Do you have access to another computer. To test Engine On using your drives
I’ve got a very old W10 desktop. I can try of course (that would be fun if it had better performance). However, I may understand performance issues for whatever reason on whatever configuration, but this will not explain why new tracks are not detected.
I’m on my why for testing. I let you know.
1 Like
So, with my very old PC, reopening Engine DJ and letting drive aggregation takes about 20 min (so = same time than with the other PC).
Spec: |Processeur|Intel(R) Core™ i7-6700K CPU @ 4.00GHz 4.01 GHz| |Mémoire RAM installée|32,0 Go (31,9 Go utilisable)| |Stockage|233 GB SSD Samsung SSD 750 EVO 250GB, 466 GB SSD CT500P5SSD8, 1.82 TB HDD ST2000DM001-1ER164| |Carte graphique|Intel(R) HD Graphics 530 (128 MB)|
|Édition|Windows 10 Famille| |Version|2009| |Installé le|15/08/2020| |Build du système d’exploitation|19045.5608|
Could this issue come from my external Sandisk SSD drive?
That is a possibility.
Is Sandisk the performance drive or library/collection drive?
Is it ExFAT, FAT32 or NTFS?
The 31K folders could also be slowing things down.
Try this -
-
Delete all the folders/playlist, it would not delete the tracks. All the Tracks are still in COLLECTION even if you REMOVE the playlist/folder . It is a simple job if they have a parent folder.
-
Now do a database clean up
-
Restart engine dj
If you dont have a parent folder
- Delete Engine Library folder on PC and SSD
- then drag the folder containing the music to the collection window, not the LEFT Panel
- It will add all tracks but would not create playlist based on the folder structure
Hi @mufasa Thank you so much for the time you spend for helping me! It’s very comforting for the new enginer I am and that counts!
I would like to explain how I’m working, or how I’m intending to work, and I’m quite comfortable to adapt and change some habits in order to fit in Engine DJ “philosophy”, as long as I remain able to work along with Engine & Virtual DJ together.
VDJ is not comfortable with directories containing a large collection of subfolders, because this take a lot of time to load in VDJ explorer, this is why I sorted my collection this way:
- Full albums: Artist Initial \ Artist \ Album name and year \ tracks
- Singles : decade\ Artist initial \ Artist \ tracks
Sample:
My expectation is to have E:\ being my performance drive for VDJ but my library for Engine, having M: playing the double role of backup (NB: I will perform NAS backup as well) + Engine OS performance drive. This is a schema of my expectation: again, I’ll be happy to adapt if necessary.
As I have a parent folder (E:\Musique), I’ll test your idea to remove folders. (But it might disturb my navigation through library in performance mode, might it not?)
Ouch!!!
With all folders deleted, loading Engine DJ took … < 37 sec !!! 
🏃➡:bottle_with_popping_cork:
You spotted it!!! (Are you in touch with dev team? Something needs optimization here.)
But now, I’m naked for navigating into my large library! Probably what I need is to find the right balance between “no folders” and “all folders”!
Hum…
37" yes, but my new tracks remains undetected 
I get the same issue with all modern SSDs
It’s even worse if you have your main drive and backup drive plugged in and Engine can take hours.
I’ve been dramatically reorganizing my library to find a way that matches both my use of Virtual DJ and Engine DJ. Described here ==>
Yet, this work is not over
So I’m not 100% sure that my problems are behind me. Yet you should have a look to check if your issue has the same origin than mine.
Hi guys, I’ve encountered the same problem. I’m using an external ssd as my master disk and Prime 4 + ssd enclosed.
This is how I fixed it:
- Only connect Prime 4 to Engine DJ (to avoid confusion)
- Full format on Prime 4 SSD (MBR + ExFat)
- Reconnected Master SSD
- Cleaned up database on Master SSD
- Full Sync back to Prime 4 SSD (took 2,5 hours for 850MB)
- Success, lost nothing during the process and everything back to normal, no more CPU/Memory spikes, no more autoclosing within Engine DJ, aggregating is back at normal)
I take it you mean ‘850GB’ for the 2.5hrs sync Peter?
Aha, yes 850GB!
1 Like
Ahh good, otherwise there may be a much wider issue in play 
Thanks for sharing the process though, hopefully this helps some people out who are having this problem.
Follow-up:
After my drastic change of folders organization, now the aggregating drives task lasts < 44 sec 
.
So, this is really Engine DJ badly dealing with deep folder tree (was: 46 k tracks in 31 k folders / now: 46 k tracks in 2,7 k folders). I would consider this as a software bug/default – yet I’m happy with my new organization so I will move to my next challenge: dealing with Virtual DJ & Engine DJ together.
I’m going to have a look at Lexicon. They recently announced 100% free library conversion.
~31.000 folders???
My brother in christ, that is almost 1 folder for every 1.5 tracks. That is not library organisation, that is library abuse. 
1 Like
Someone ticked the ‘let Apple Music organise your library’ box 
My brother in whatever,
I congratulate you on your skill with numbers. I can hear your surprise, yet this organization had its logic, and it worked very well in Virtual DJ so I had no reason to change before discovering the highly renowned library management from Engine.
But that is now in the past, I am no longer a lost sheep.
PS @STU-C » I’m not yet an Apple Music user, but I’m considering it 
1 Like
just make sure you untick that box and organise it yourself, otherwise you’ll end up with a right mess of folders and sub folders.
1 Like