Think I’m at 600MB with only 10000 analyzed tracks. Most of them also longer than standard versions. Will try to get it over 1GB as a test, but I’m certain several members would already be over that value.
I first assumed that a 1gb DB sounded huge after the initial post, but yeah it seems many here are using their gear with large DB files, so would suggest the issue lies somewhere else in the chain.
I going to watch a 27 minute youtube video on preparing an external drive and hopefully i can export all my playlist on to a new drive
So, I went back to basic and analyze my entire library. Should be able to recovery 99% of my work including meta-data. Seems like the method initially used to re-create my engine-dj library was not to denon specification. Hopefully my database can grow to infinity.
Was a 3rd party tool used on the database earlier or other possible issue? Good knowledge to share perhaps.
Exactly. Under the hood Engine is using sql light database system. A database system which is very robust and being used by many many well-known companies.
For example: Apple, Adobe, Airbus.
More:
You know that a gigs worth of songs does not mean that the engine database file will be a gig in size too, yes?
I’ve got a -music collection- of about 1.8 gigabytes , and yet the engine database files add up to about only 20mb roughly… so 20mb is just a fraction of the 1gb database “corruption” which you quote
On the version 4.0.0 update a new database system was introduced, it is very much more sensitive to corruption than other updates. The database corruption is typically caused by manually editing files / folders on an exported drive or because of unexpected data chunks in the audio files, like meta information caused by obtaining the music from dubious sources. With every update there is a risk that the database update will fail because of corruption. Restore the database from a backup, or if that fails do a fresh export. In theory the is no limit to the database size and I wonder if the 1Gb size is a symptom of the corruption, rather than the other way abouts.