Bugzilla – Bug 3818
Selecting 'Use Moodlogic' causes scanner.exe to scan for a Long Time
Last modified: 2008-09-15 14:39:24 UTC
... 2006-07-26 09:02:24.8922 file:///C:/Documents%20and%20Settings/Administrator/My%20Documents/My%20Music/Testcd/WaveWithCue/GTA%20San%20Andreas%20-%20K-Rose.wav #1771.89333333333-1778.68 2006-07-26 09:02:24.9027 file:///C:/Documents%20and%20Settings/Administrator/My%20Documents/My%20Music/Testcd/WaveWithCue/GTA%20San%20Andreas%20-%20K-Rose.wav #1778.68-1810.18666666667 2006-07-26 09:02:24.9126 file:///C:/Documents%20and%20Settings/Administrator/My%20Documents/My%20Music/Testcd/WaveWithCue/GTA%20San%20Andreas%20-%20K-Rose.wav #1810.18666666667-1874.34666666667 100% [=========================================] 2.86 tracks/sec 00m02s DONE 2006-07-26 09:02:24.9269 Import: Starting Plugins::MoodLogic::Importer scan 2006-07-26 09:02:24.9301 MoodLogic: using moodlogic: 1 2006-07-26 09:02:24.9340 MoodLogic: start export 2006-07-26 09:02:24.9794 MoodLogic: Opening Object Link... And then it stops. I left it there for over an hour and no further progress was reported. I notice some pages on the Moodlogic site are giving me a '500 Servelet Exception' so they may be having some server problems that complicate things. I sent them email about that problem. I am leaving this bug assigned to me for now until I hear back from them and eliminate the problem on their side as a factor.
Dan looked at this, and said it looks like almost certainly a Moodlogic server problem. I'll update the bug if I hear back from my email inquiries to them.
selecting 'use moodlogic' and clicking change shoudln't be starting a scan on it's own. are you talking about a scan with 'use moodlogic' enabled? I has appeared to work fine for me up until the last time I scanned (a few days ago). Just now, starting a clear library and rescan seems to have worked fine. This is with Win2k, however. 2006-07-26 11:07:21.2495 Found 4 files in D:\slim\server\Playlists 2006-07-26 11:07:22.3975 MoodLogic: using moodlogic: 1 2006-07-26 11:07:22.3978 MoodLogic: start export 2006-07-26 11:07:22.4026 MoodLogic: Opening Object Link... 2006-07-26 11:07:22.5043 MoodLogic: Begin song scan for 389 tracks. 2006-07-26 11:07:22.5070 MoodLogic: Creating entry for track 0: file:///D:/music/05%20-%20Seether%20feat.%20Amy%20Lee%20-%20Broken%20-%20ESDT%20-%20www.esdonkey.com.mp3 2006-07-26 11:07:22.6259 MoodLogic: Creating entry for track 1: file:///D:/music/05%20-%20Seether%20feat.%20Amy%20Lee%20-%20Broken%20-%20ESDT%20-%20www.esdonkey.com.mp3 2006-07-26 11:07:22.7014 MoodLogic: Creating entry for track 2: file:///D:/music/AGE%20OF%20ELECTRIC%20-%20Ugly.mp3
Good to know. I won't sweat it as much, but I'll still try to get it straightened out. Thanks for the info, KDF.
another idea, ML does annoying things when it's db gets "corrupted", which happens all to easily (so much so that I suspect it isn't really corrupted per se). Starting the ML app and closing again always fixes this, and I never got a response when I asked how we could replicate that fix from slimserver. Usually, however, that corruption is seen from slimserver on startup, which would disable ML altogether. Not sure if it woudl look like the above if it happened whiel the server was running.
Maybe their servers are better now. have another look.
I was not actually aware that moodlogic did anything to communicate with their servers once songs were activated. Scanning moodlogic accesses a local COM object which links to the MS Access database of moodlogic metadata.
Is this still an issue? Could the recent MoodLogic playlist changes have fixed this?
It now completes the scan promptly.