I know that the location of the Engine DJ library can be found in C:\Users\<username>\Music\Engine Library, however when removing that folder, EngineDJ still boots up fine, and still with the original database. All removed files are simply restored.
Since Engine DJ lacks a way to completely clear the collection, this is a bit annoying. Does anyone know where Engine DJ gets those restored files from? And why it keeps a shadowcopy somewhere?
Or, if you happen to know how to clear the entire collection, including the playlists, let me know.
What @STU-C says is one possibility, when the database is not found it might fetch the backup. Those backups are not created every time, so, be careful, you might lose data.
Thereās also another potential explanation. Iām on Mac. Based on my observation, Engine DJ creates an \Engine Library\ folder on each drive you add music from. Those data from each drive are stored in the \Engine Library\Database2\m.db database on the drive the music files are on. M.db has many tables, the main one being track. When you open Engine DJ it conglomerates those data from all attached drives into the library. So, in essence, the library you see in Engine Library is not one Engine Library database.
Are the music files you added on a remote drive? If so, then those data are stored there and reloaded to Engine DJ library view when you open the program.
If you want to dig around. You can use a program like DB Browser for SQLite to view the m.db databases. Just donāt edit anything there.
this was it! I had an older synced SD card inserted and Engine just used that database when it didnāt find one. Completely random behavior if you ask me.
Itās almost certainly by design. If there was a main database on your local drive that included the information for tracks on the connected drive(s), it would be inaccurate when those drives arenāt connected.
Slow connected drives are likely the source of the slow Engine DJ startup / āaggregating drivesā complaints.
Itās not random, itās just not well described.
Engine DJ is partially baked and there are plenty of error and edge cases that it just adapts to /takes care of with little to no notification to the user. Itās infuriating as an end user for sure.