I've had LMS on x86 linux, with headless musicip running without a problem for a couple years now. My workflow with new music is to actually load the music into the musicip windows application, analyze, and then archive the analysis into the files, then move the files to the server that's running the LMS, force the headless musicip to add the new music, and all is well.
I just re-arranged the music collection a bit, changing directory structures around. As everything is archived in the files, I figured just wipe the x86 linux headless setup database, and re-add. Which was fine, other than it's decided it needs to validate 1/3 of my collection again. As I spent a long time encoding/archive analysis in the files, I was under the impression this should allow the musicip headless server to just rebuild the database rapidly. Validation is going, but as i have 1000's of files to re-validate, the the number is moving down very slowly, I'm hoping there's something else I can do. (Which may be look at the bliss scanner) Any suggestions? Any easy way to determine from the headless musicip what files are being validated? I can check to see if by chance I somehow didn't archive 1/3rd of my collections musicip fingerprints? ------------------------------------------------------------------------ Matt Drown's Profile: http://forums.slimdevices.com/member.php?userid=69476 View this thread: http://forums.slimdevices.com/showthread.php?t=116105 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
