The database and/or the source files gets corupted now that the database has reached just over 1000mb. Was really lucky to have a copy of the database which is a week’s old but i cannot add new songs as the software does a madness to prevent the database from growing… Engine DJ version: 4.01 Operation system: Windows 11 Drive: SSD 2TB
I think your issue here is, working out why your DB file is 1GB, not what to do when it reaches it.
Mine is 192mb.
Well all my tracks have been analysed since 2017. If denon has an issue with large database sizes it should be printed in bold in the manual. A 1GB database is tiny for 2024. Denon has to address this. If there is a limit, the software should display a pop-up saying that it cannot analyse the selected songs as the database has exceeded 1000mb. Corrupting the database and source files is criminality
I hope that somebody can confirm that there is a limit … because I am a strong candidate for going beyond that scope in the future. I use Engine DJ as a library software for my entire music collection = ongoing ever-expanding project, not going to stop until I die …
If this issue exists, it would be a good feature request: No limits …
No no limits, we'll reach for the sky
No valley too deep, no mountain too high
No no limits, won't give up the fight
We do what we want and we do it with pride
1 Like
Check this link out below, and scroll down to version 2.0 of desktop, here it explains how there was a whole new database introduced in that version, did you migrate to it?
Version 3.0 was also refactored.
Quite a lot of users completely wiped their DB and started afresh with the 2.0 version update.
Yes i migrated the library years ago. I am using 4.01
how many tracks are you exporting? There are other threads on here about bloated DB files, im not sure if it was solved or not.
All my music is on the SSD. Im not sure of the term bloaded DB. Engine DJ manages the analysis process not the user. So Denon needs to address the short comings of these players
But how many tracks do you have in your engine library? its important to help understand why it might be so big.
Bloated means oversized, too full… people have reported having DB files that are too big on here previously.
Did you try the db cleanup thing in the settings
Just curious how many tracks are in the library?
1 Like
Close to 1gig of vinyl ripped music. Got thousands of records.
Engine DJ should be optimized. i am not sure what the cleanup functionality does.
No software on planet earth should be allowed to legally destroy data
Run the cleanup then export all your music to the drive again.
This is from the manual;
Library Optimization: This tool allows you to clear the database of un-needed information. Click Run Cleanup to perform. While the cleanup is in progress, do not close Engine DJ or shut off your computer. Note: We recommend performing this operation on a regular basis with your Engine DJ library and all Engine drives to help optimize performance on Engine hardware. Before running cleanup, make sure you have also backed up your Engine Library and the Engine databases on each of your drives using the process described above.
Edit: you will need to format and export all your library to your drive after the cleanup. That will be the best way to get your newly optimised library to the drive.
1 Like
OK. I gain 100mb after cleanup. But whats happens when i add more tracks to the drive?
Denon must understand that engine DJ should prevent data corrution. You cannot do a cleanup after the drive gets corruted.
The software needs to prevent data corruption and abort further analysis
How many tracks are in the library?
1 Gig of music.
Imagine a commercial aircraft running engine DJ !!!
The DB getting to be that size isn’t the problem. One of our beloved community members had a DB size of 1.72GB when we began troubleshooting the db export issue. My own DB is nearing 640MB and grows weekly. =)
@DJ5000, are you doing this on an external exFAT or FAT32 drive by chance?
2 Likes
I know of a fighter jet that uses NodeJS 
I’m just a pee-on community member and have spent many hours looking at the DB schema and writing lots of code for my own tools. The DB schema very pretty robust and does a lot to prevent things like this from happening.
If you are using a volume with exFAT or FAT32, then that likely is the problem and not caused by Engine. If you want, i can go into the dirty details, though it won’t solve your problem.
Assuming the above is true, I would suggest formatting the drive to NTFS as that will be the solution you’re looking for.
my external SSD is exFAT formated.
What will happen in the next 3 years when many users hit this brick wall?
Thanks for the advice. I will format my backup ssd to NTFS and hopefully that should work. Thanks for the advice