Bug 4066 - Scanner runs non-stop with MusicMagic enabled.
: Scanner runs non-stop with MusicMagic enabled.
Status: RESOLVED DUPLICATE of bug 4056
Product: Logitech Media Server
Classification: Unclassified
Component: Scanner
: 6.5b1
: PC Windows Server 2003
: P2 normal (vote)
: ---
Assigned To: Chris Owens
http://forums.slimdevices.com/showthr...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-09-08 04:50 UTC by jeff
Modified: 2008-09-15 14:39 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jeff 2006-09-08 04:50:17 UTC
SlimServer Version: 6.5b1 - 9424 - Windows Server 2003 - EN - cp1252

The scanner process runs non-stop when MusicMagic is enabled and MUSICMAGIC RELOAD INTERVAL is left at the default value (60 I believe).

Killing the scanner AND MusicMagicService from task manager alleviates the issue, also you can set the MUSICMAGIC RELOAD INTERVAL to 0 and the scanner will process normally.
Comment 1 Siduhe 2006-09-08 04:59:57 UTC
(In reply to comment #0)
Slimserver also works as expected if you set the MIP reload interval to a much longer period - 86400 (once a day).  Perhaps the problem happens because a new scan is triggered by the reload interval before the old one has finished ?

Comment 2 jeff 2006-09-08 05:04:25 UTC
(In reply to comment #1)
> (In reply to comment #0)
> Slimserver also works as expected if you set the MIP reload interval to a much
> longer period - 86400 (once a day).  Perhaps the problem happens because a new
> scan is triggered by the reload interval before the old one has finished ?
> 

There have been no recent changes to the music library since A) my last update and validation to the MusicIP Library, and B) My last dump and rescan.  Yet, if I change the MUSICMAGIC RELOAD INTERVAL to a non-zero value, it will kick off a scan.

Comment 3 KDF 2006-09-08 08:14:02 UTC
see bug 4056.  problem is basically the same.
Comment 4 Dan Sully 2006-09-08 08:39:14 UTC

*** This bug has been marked as a duplicate of 4056 ***