Home of the Squeezebox™ & Transporter® network music players.
Results 1 to 6 of 6

Thread: rescan time

  1. #1
    Senior Member
    Join Date
    Apr 2005
    Location
    UK
    Posts
    164

    rescan time

    I know this is the $64,000 question but how long should a rescan take?
    I am using ss 6.2 on an imac 800 mhz with around 13,000 tracks on a fw hd and using itunes.
    I just added a new album and did a rescan looking for new music. The rescan is taking hours.
    with d_info set I am seeing this sort of output to the console:

    2005-11-10 16:08:32.6720 _checkValidity: Checking to see if file:///Volumes/media/itunes/Archies/Lince%20Dance%20cd/Sugar%20Sugar.mp3 has changed.
    2005-11-10 16:08:32.6744 _hasChanged: Checking for [/Volumes/media/itunes/Archies/Lince Dance cd/Sugar Sugar.mp3] - size & timestamp.

    I have the lazy search plug-in and superdatetime plugin as well.
    Could it be the lazy search plugin or would it be anything else?

  2. #2
    Senior Member hickinbottoms's Avatar
    Join Date
    Apr 2005
    Location
    Wokingham, UK
    Posts
    544

    rescan time

    The lazy search does not get involved at any point *during* the scan (and
    it's not showing the messages you see there - all its messages are prefixed
    with LazySearch2), but it does process the database contents when the full
    scan has finished.

    If you're seeing the "scan in progress" in the web UI then it's definitely
    just the normal core SlimServer scan that's taking the time as the lazy
    database work only starts when that message disappears.

    Stuart

    -----Original Message-----
    From: discuss-bounces (AT) lists (DOT) slimdevices.com
    [mailto:discuss-bounces (AT) lists (DOT) slimdevices.com] On Behalf Of Steven Moore
    Sent: 10 November 2005 5:32 PM
    To: discuss (AT) lists (DOT) slimdevices.com
    Subject: [slim] rescan time


    I know this is the $64,000 question but how long should a rescan take?
    I am using ss 6.2 on an imac 800 mhz with around 13,000 tracks on a fw
    hd and using itunes.
    I just added a new album and did a rescan looking for new music. The
    rescan is taking hours.
    with d_info set I am seeing this sort of output to the console:

    2005-11-10 16:08:32.6720 _checkValidity: Checking to see if
    file:///Volumes/media/itunes/Archies/Lince%20Dance%20cd/Sugar%20Sugar.mp3
    has changed.
    2005-11-10 16:08:32.6744 _hasChanged: Checking for
    [/Volumes/media/itunes/Archies/Lince Dance cd/Sugar Sugar.mp3] - size &
    timestamp.

    I have the lazy search plug-in and superdatetime plugin as well.
    Could it be the lazy search plugin or would it be anything else?


    --
    Steven Moore
    ------------------------------------------------------------------------
    Steven Moore's Profile: http://forums.slimdevices.com/member.php?userid=104
    View this thread: http://forums.slimdevices.com/showthread.php?t=18072


  3. #3
    Senior Member
    Join Date
    Apr 2005
    Location
    UK
    Posts
    164
    Thanks that narrows it down a bit. I tried the latest night-lies with the same result, long rescan times, in fact I had to stop the server (after 2.5 hrs) as it was going on so long.
    The strange thing was when I reinstalled ss 6.2 and did a wipe scan it took about 40 mins and actually finished.
    But again the rescan for new music never seems to end. iTunes perhaps?
    I'll try clearing everything slim out, prefs etc and if it's still the same and anyone else can confirm this I can submit a bug report.

  4. #4
    Senior Member
    Join Date
    Apr 2005
    Location
    UK
    Posts
    164
    I just tried rescanning for new music after doing a wipe/scan and after clearing all things slim from the computer and re-installing ss, the rescan works now. Something must have happened to a file when upgrading to 6.2.1 nightly.
    For reference I deleted:
    slimserver.prefpane
    slimdevices folder
    slimserver folder in caches
    com.slimdevices.slim.plist

    I still think the rescan (for new music) time is very long > 50mins even on my comparatively slow computer.

    imac 800mhz, 10.4.3, ss 6.2, 13,000 tracks on ex fw hd, using itunes.

  5. #5
    Senior Member ceejay's Avatar
    Join Date
    Apr 2005
    Location
    Worcestershire, UK
    Posts
    2,314

    Stop scan ?

    Slightly relevant to this thread - is there any way to stop a scan, other than stopping slimserver?

    For some reason my regular overnight rescan is still running after 6 hours (usually more like 30 mins). Running 6.2.1 nightly 2005-11-10.

    Ceejay

  6. #6
    Senior Member
    Join Date
    Apr 2005
    Location
    UK
    Posts
    164
    I think the only way to stop a scan is by stopping the server.
    I added a couple of cd's today and did a rescan for new music and 1.5 hours later it was still going, I filed a bug report number : 2542
    http://bugs.slimdevices.com/show_bug.cgi?id=2542
    I'm not sure if the server is still scanning but I can hear the ex fw drive being continually accessed.

    On a similar theme does anyone know when doing a rescan for new music if ss checks every file?
    If it does I was looking at the music folder and thought that it may faster to just check each folder of each artist to see if it has been modified since the last rescan and if it hasn't just skip that folder.
    In my case ~13,000 track tests against ~1000 artist tests, an obvious performance gain. Just an idea.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •