There was a comment in the general section asking about using more than one core for analyzing files.
I know that Torq split certain functions across two separate threads, leaving the audio processing on one, and I believe the database searching and the like on another. The result was the app could completely crash the GUI and/or database and the audio would continue to play unimpeded. While not exactly what I'm thinking of, I'm hoping that it could shed some light on some ways it's been done before.
So....
How about multi-threading the application to take advantage of the parallel processing capabilities of the modern mutli-core processors? This, in theory, would allow you to analyze multi files in parallel - greatly speeding up at least the initial analyzing of the tracks.
However it's implemented isn't important... but I just wanted to throw it out as food for thought and see what happens.
