I’m a mobile/Wedding DJ also, so have a large library of tunes which I could be asked to play at any gig that I attend. I fully understand that when we wear our “mobile DJ” hat, we can’t simply export just a part of our collection and take only that to a gig.
OK, the whole 2.4gb size thing…
Lets say that “Tony” has 80,000 Tracks - and they’re using up 1.5 TB of storage on a 2TB drive.
If Tony sets Engine Prime to “Auto analyse: ON” then everytime Engine Prime is opened up it will look for unanalysed music files on that 2TB drive and will store a few hundred bytes of info, about EACH file it analyses, with its BPM data, Waveform, Music Key etc. Those small amounts of data about each file are stored in the Analysed Music Database.
All those little amounts of data in the Music database all add up. By the time it’s analysed over 10,000 - 12,000 tracks, the music database could be around 2.4gb and that’s largest database size the players will -------currently-------- share over the network.
Now, I know that as a mobile/wedding DJ, I’ll typically play 15 songs per hour, so around 75 tracks in an evening and maybe 200 tracks in a full days celebration. Of course, different gigs need different songs… some songs are the same at many weddings (the popular party/dance ones), but some songs in my collection will be album fillers etc, files which are good to have, but will rarely get played, and even more rarely mixed or sliced/rolled - meaning that I won’t need my entire collection fully analysed - and of course… any song that I do pull up at any event, the SC5000 will fully analyse it, in seconds, whilst it’s cued or playing anyway…
So, I deleted my database file off of the drive, switch Auto Analyse: off in Engine Prime and now all my players can see/find all my 70,000 tracks.
A future revision of firmware may well negate the 2.4gb database share/size thing altogether.