PDA

View Full Version : Rescan vs. wipe cache - Once more, with feeling!



dbls
2005-01-23, 08:46
The FAQ item 'What is the difference between the "Rescan" and
"Wipe Cache" buttons?' reads:

The Rescan button should find any changes made to you [sic]
music library. When the MP3 Tag Database is being used, it
is possible that data in the cache can be corrupt. If that
is the case, the "Wipe Cache" button can be used to make
the server rebuild everything from scratch.

The first sentence is simply untrue. My server is set to
rescan at midnight, and a CD I added three days ago still
hasn't shown up. (I have deliberately chosen not to wipe
cache yet out of a perverse curiosity about whether Rescan
will ever find the new CD.) And since "Browse Music Folder"
doesn't actually read the folder contents in real time, but
apparently relies on the cache to follow the directory tree, I
can't find it that way either.

As far as needing to wipe cache to correct corrupt tag data,
when I changed some track titles in the tags for an album
recently, the new titles appeared almost instantaneously,
without doing a rescan.

So it looks to me like SlimServer is reading the tags in real
time, which is not what I would expect. It does *not* read
the music folder in real time when I "Browse Music Folder",
as I would expect. Rescan...does what? Checks to see whether
the physical files for tracks that are in the database are
still there? The FAQ statement implies that it doesn't
correct tags (you must wipe cache for that), so what *does* it
do?

One hopes that this confusion will be cleared up with the
advent of the SQL backend.

(Server: Win98SE, 400MHz Pentium II, 384MB ram, SlimServer
5.4.1)

-:- dbls

Jack Coates
2005-01-23, 10:22
> The FAQ item 'What is the difference between the "Rescan" and
> "Wipe Cache" buttons?' reads:
>
> The Rescan button should find any changes made to you [sic]
> music library. When the MP3 Tag Database is being used, it
> is possible that data in the cache can be corrupt. If that
> is the case, the "Wipe Cache" button can be used to make
> the server rebuild everything from scratch.
>
> The first sentence is simply untrue. My server is set to
> rescan at midnight, and a CD I added three days ago still
> hasn't shown up. (I have deliberately chosen not to wipe
> cache yet out of a perverse curiosity about whether Rescan
> will ever find the new CD.) And since "Browse Music Folder"
> doesn't actually read the folder contents in real time, but
> apparently relies on the cache to follow the directory tree, I
> can't find it that way either.

How odd. It generally works for me, though I'm only doing the nightly
automated refresh to pick up any album cover art that the amazon-image
script might have pulled in. I usually kick off a rescan on my own after
adding albums. Every now and then the rescan doesn't pull in the new stuff
(rare) or I start getting weirdness like an album showing up in the artist
list or an artist showing up three times in the artist list. That's when I
wipe cache and rebuild.

>
> As far as needing to wipe cache to correct corrupt tag data,
> when I changed some track titles in the tags for an album
> recently, the new titles appeared almost instantaneously,
> without doing a rescan.
>

I've changed tags on the fly before, but I haven't seen them update like
you're describing. Then, I wasn't looking either. However, lemme go change
the tag on the song that's playing right now...

[jack@felix Krishna_Lila]$ id3tool 03_Maname_Diname.mp3
Filename: 03_Maname_Diname.mp3
Song Title: Maname Diname
Artist: DJ Cheb i Sabbah
Album: Krishna Lila
Note: Created by Grip
Track: 3
Year: 2002
[jack@felix Krishna_Lila]$ id3tool -t "testing this out" 03_Maname_Diname.mp3
[jack@felix Krishna_Lila]$ id3tool 03_Maname_Diname.mp3
Filename: 03_Maname_Diname.mp3
Song Title: testing this out
Artist: DJ Cheb i Sabbah
Album: Krishna Lila
Note: Created by Grip
Track: 3
Year: 2002

The SliMP3 to my right still says "Maname Diname (DJ Cheb i Sabbah)", as
does the web interface.


> So it looks to me like SlimServer is reading the tags in real
> time, which is not what I would expect. It does *not* read
> the music folder in real time when I "Browse Music Folder",
> as I would expect. Rescan...does what? Checks to see whether
> the physical files for tracks that are in the database are
> still there? The FAQ statement implies that it doesn't
> correct tags (you must wipe cache for that), so what *does* it
> do?
>
> One hopes that this confusion will be cleared up with the
> advent of the SQL backend.
>

I'd expect it to make things more real-time, though I haven't had a chance
to try it out yet.



--
Jack At Monkeynoodle.Org: It's A Scientific Venture...
"Believe what you're told; there'd be chaos if everyone thought for
themselves." -- Top Dog hotdog stand, Berkeley, CA

Jack Coates
2005-01-23, 10:31
> Actually I can always use "browse music folder" to find stuff that I just
> added. It sure acts like it is doing it in real time to me.
>

Yup:
[jack@felix jack]$ cd /mnt/music/miscellaneous/
[jack@felix miscellaneous]$ wget
http://www.djriko.org/music/DJ%20Riko%20-%20Whistler%27s%20Delight%20\(Full%20version\).mp3
--09:09:37--
http://www.djriko.org/music/DJ%20Riko%20-%20Whistler's%20Delight%20(Full%20version).mp3
=> `DJ Riko - Whistler's Delight (Full version).mp3'
Resolving www.djriko.org... 66.195.242.57
Connecting to www.djriko.org[66.195.242.57]:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 8,196,096 [audio/mpeg]

100%[====================================>] 8,196,096 81.51K/s ETA
00:00

09:11:21 (78.94 KB/s) - `DJ Riko - Whistler's Delight (Full version).mp3'
saved [8,196,096/8,196,096]

And browse music folder in the web interface gets me here:

Song Info for Whistler's Delight (Full Version)

Play this song

Add this song to the playlist

Title: Whistler's Delight (Full Version)
Artist: DJ Riko
Genre: Whistledelia
File Format: MP3
Duration: 6:49
Year: 2004
Comment: More tunes at www.djriko.com.
File Length: 8,196,096 Bytes
Bitrate: 160kbps CBR
ID3 Tag Version: ID3v1 / ID3v2.3.0
Date Modified: Monday, December 13, 2004, 4:02:10 AM
Location: file:///mnt/music/miscellaneous/DJ Riko - Whistler's Delight
(Full version).mp3 (Download)

--
Jack At Monkeynoodle.Org: It's A Scientific Venture...
"Believe what you're told; there'd be chaos if everyone thought for
themselves." -- Top Dog hotdog stand, Berkeley, CA

Damon Riley
2005-01-23, 11:54
I'm seeing something similar with the slimserver running on Linux.
Neither rescan nor wipe cache seems to be able to get rid of the
misspelled Fleetwook Mac directory, although rescanning does find new
artitsts. I dunno what's going on. I'm using slimserver 5.4.0.

Here's what I see using the command line:

smb: \mp3\> ls fleetwoo*
fleetwood_mac D 0 Wed Jan 12 15:18:47
fleetwood_mac-rumors.m3u 431 Wed Jan 12 15:20:48
fleetwood_mac-say_you_will.m3u A 835 Wed Jan 12 14:56:49


As you can see, there is no fleetwook_mac, but I find it when I use the
web interface.

If I play a track from "fleetwook_mac" then I can see that the path to
the file is correct-- that it uses fleetwood_mac. But no matter how
many times I have rescanned and wiped, the non-existent artist
"fleetwook_mac" persists. This is what I get for not proofreading the
freedb disc info.

And I don't even LIKE Fleetwood Mac that much! It's my wife's disk. OH
THE INJUSTICE! :-)

-- Damon

dbls wrote:
> The FAQ item 'What is the difference between the "Rescan" and
> "Wipe Cache" buttons?' reads:
>
> The Rescan button should find any changes made to you [sic]
> music library. When the MP3 Tag Database is being used, it
> is possible that data in the cache can be corrupt. If that
> is the case, the "Wipe Cache" button can be used to make
> the server rebuild everything from scratch.
>
> The first sentence is simply untrue. My server is set to
> rescan at midnight, and a CD I added three days ago still
> hasn't shown up. (I have deliberately chosen not to wipe
> cache yet out of a perverse curiosity about whether Rescan
> will ever find the new CD.) And since "Browse Music Folder"
> doesn't actually read the folder contents in real time, but
> apparently relies on the cache to follow the directory tree, I
> can't find it that way either.
>
> As far as needing to wipe cache to correct corrupt tag data,
> when I changed some track titles in the tags for an album
> recently, the new titles appeared almost instantaneously,
> without doing a rescan.
>
> So it looks to me like SlimServer is reading the tags in real
> time, which is not what I would expect. It does *not* read
> the music folder in real time when I "Browse Music Folder",
> as I would expect. Rescan...does what? Checks to see whether
> the physical files for tracks that are in the database are
> still there? The FAQ statement implies that it doesn't
> correct tags (you must wipe cache for that), so what *does* it
> do?
>
> One hopes that this confusion will be cleared up with the
> advent of the SQL backend.
>
> (Server: Win98SE, 400MHz Pentium II, 384MB ram, SlimServer
> 5.4.1)
>
> -:- dbls
>
>
> ------------------------------------------------------------------------
>
>

Aaron Zinck
2005-01-23, 12:36
Damon, I know this was discussed at some length in an earlier thread. I
never heard definitively if you repaired the id3 tag info. Slimserver
gathers its data primarily from the id3 tags. If freedb looked up the
(incorrect) info and that's how you got the fleetwook mac directory to begin
with then it's highly likely that it tagged each of those files as having
the artist fleetwook mac. Have you fixed the tags?


"Damon Riley" <damonriley (AT) alumni (DOT) umass.edu> wrote in
message news:41F3F2C9.5020107 (AT) alumni (DOT) umass.edu...
> I'm seeing something similar with the slimserver running on Linux.
> Neither rescan nor wipe cache seems to be able to get rid of the
> misspelled Fleetwook Mac directory, although rescanning does find new
> artitsts. I dunno what's going on. I'm using slimserver 5.4.0.
>
> Here's what I see using the command line:
>
> smb: \mp3\> ls fleetwoo*
> fleetwood_mac D 0 Wed Jan 12 15:18:47
> fleetwood_mac-rumors.m3u 431 Wed Jan 12 15:20:48
> fleetwood_mac-say_you_will.m3u A 835 Wed Jan 12 14:56:49
>
>
> As you can see, there is no fleetwook_mac, but I find it when I use the
> web interface.
>
> If I play a track from "fleetwook_mac" then I can see that the path to
> the file is correct-- that it uses fleetwood_mac. But no matter how
> many times I have rescanned and wiped, the non-existent artist
> "fleetwook_mac" persists. This is what I get for not proofreading the
> freedb disc info.
>
> And I don't even LIKE Fleetwood Mac that much! It's my wife's disk. OH
> THE INJUSTICE! :-)
>
> -- Damon
>
> dbls wrote:
> > The FAQ item 'What is the difference between the "Rescan" and
> > "Wipe Cache" buttons?' reads:
> >
> > The Rescan button should find any changes made to you [sic]
> > music library. When the MP3 Tag Database is being used, it
> > is possible that data in the cache can be corrupt. If that
> > is the case, the "Wipe Cache" button can be used to make
> > the server rebuild everything from scratch.
> >
> > The first sentence is simply untrue. My server is set to
> > rescan at midnight, and a CD I added three days ago still
> > hasn't shown up. (I have deliberately chosen not to wipe
> > cache yet out of a perverse curiosity about whether Rescan
> > will ever find the new CD.) And since "Browse Music Folder"
> > doesn't actually read the folder contents in real time, but
> > apparently relies on the cache to follow the directory tree, I
> > can't find it that way either.
> >
> > As far as needing to wipe cache to correct corrupt tag data,
> > when I changed some track titles in the tags for an album
> > recently, the new titles appeared almost instantaneously,
> > without doing a rescan.
> >
> > So it looks to me like SlimServer is reading the tags in real
> > time, which is not what I would expect. It does *not* read
> > the music folder in real time when I "Browse Music Folder",
> > as I would expect. Rescan...does what? Checks to see whether
> > the physical files for tracks that are in the database are
> > still there? The FAQ statement implies that it doesn't
> > correct tags (you must wipe cache for that), so what *does* it
> > do?
> >
> > One hopes that this confusion will be cleared up with the
> > advent of the SQL backend.
> >
> > (Server: Win98SE, 400MHz Pentium II, 384MB ram, SlimServer
> > 5.4.1)
> >
> > -:- dbls
> >
> >
> > ------------------------------------------------------------------------
> >
> >

Damon Riley
2005-01-23, 12:56
Hi, Aaron. Before I could reply to your question, I had to look up id3.
I'm still a greenhorn when it comes to digital music. No, I hadn't
altered the tags, I had only altered the m3u playlist and file structure.

Can I just pry open each .ogg file with emacs and replace Fleetwook with
Fleetwood and then save? That sounds tedious, so perhaps I'd be better
off re-ripping the disc, being careful to proofread the data, no?

-- Damon

Aaron Zinck wrote:
> Damon, I know this was discussed at some length in an earlier thread. I
> never heard definitively if you repaired the id3 tag info. Slimserver
> gathers its data primarily from the id3 tags. If freedb looked up the
> (incorrect) info and that's how you got the fleetwook mac directory to begin
> with then it's highly likely that it tagged each of those files as having
> the artist fleetwook mac. Have you fixed the tags?
>
>
> "Damon Riley" <damonriley (AT) alumni (DOT) umass.edu> wrote in
> message news:41F3F2C9.5020107 (AT) alumni (DOT) umass.edu...
>
>>I'm seeing something similar with the slimserver running on Linux.
>>Neither rescan nor wipe cache seems to be able to get rid of the
>>misspelled Fleetwook Mac directory, although rescanning does find new
>>artitsts. I dunno what's going on. I'm using slimserver 5.4.0.
>>
>>Here's what I see using the command line:
>>
>>smb: \mp3\> ls fleetwoo*
>> fleetwood_mac D 0 Wed Jan 12 15:18:47
>> fleetwood_mac-rumors.m3u 431 Wed Jan 12 15:20:48
>> fleetwood_mac-say_you_will.m3u A 835 Wed Jan 12 14:56:49
>>
>>
>>As you can see, there is no fleetwook_mac, but I find it when I use the
>>web interface.
>>
>>If I play a track from "fleetwook_mac" then I can see that the path to
>>the file is correct-- that it uses fleetwood_mac. But no matter how
>>many times I have rescanned and wiped, the non-existent artist
>>"fleetwook_mac" persists. This is what I get for not proofreading the
>>freedb disc info.
>>
>>And I don't even LIKE Fleetwood Mac that much! It's my wife's disk. OH
>>THE INJUSTICE! :-)
>>
>>-- Damon
>>
>>dbls wrote:
>>
>>>The FAQ item 'What is the difference between the "Rescan" and
>>>"Wipe Cache" buttons?' reads:
>>>
>>> The Rescan button should find any changes made to you [sic]
>>> music library. When the MP3 Tag Database is being used, it
>>> is possible that data in the cache can be corrupt. If that
>>> is the case, the "Wipe Cache" button can be used to make
>>> the server rebuild everything from scratch.
>>>
>>>The first sentence is simply untrue. My server is set to
>>>rescan at midnight, and a CD I added three days ago still
>>>hasn't shown up. (I have deliberately chosen not to wipe
>>>cache yet out of a perverse curiosity about whether Rescan
>>>will ever find the new CD.) And since "Browse Music Folder"
>>>doesn't actually read the folder contents in real time, but
>>>apparently relies on the cache to follow the directory tree, I
>>>can't find it that way either.
>>>
>>>As far as needing to wipe cache to correct corrupt tag data,
>>>when I changed some track titles in the tags for an album
>>>recently, the new titles appeared almost instantaneously,
>>>without doing a rescan.
>>>
>>>So it looks to me like SlimServer is reading the tags in real
>>>time, which is not what I would expect. It does *not* read
>>>the music folder in real time when I "Browse Music Folder",
>>>as I would expect. Rescan...does what? Checks to see whether
>>>the physical files for tracks that are in the database are
>>>still there? The FAQ statement implies that it doesn't
>>>correct tags (you must wipe cache for that), so what *does* it
>>>do?
>>>
>>>One hopes that this confusion will be cleared up with the
>>>advent of the SQL backend.
>>>
>>>(Server: Win98SE, 400MHz Pentium II, 384MB ram, SlimServer
>>>5.4.1)
>>>
>>>-:- dbls
>>>
>>>
>>>------------------------------------------------------------------------
>>>
>>>

Jack Coates
2005-01-23, 13:40
....
>
> And I don't even LIKE Fleetwood Mac that much! It's my wife's disk. OH
> THE INJUSTICE! :-)
>
> -- Damon
> ...

Like Camper Van Beethoven? They did a very wacked out and bizarre cover of
Tusk (the whole double-album). The tapes were stored, and recently got
edited/mixed/funkified by some nutball kid with a Mac and a soundboard.

http://www.bbc.co.uk/music/rockandalt/reviews/campervanb_tusk.shtml

Bought it from emusic :) It's weird and cool and I generally like it,
though some of it is forgettable. The thing I like most about it is that
it doesn't sound like CvB or Fleetwood Mac -- it's a new and enjoyably
bizarre album.

--
Jack At Monkeynoodle.Org: It's A Scientific Venture...
"Believe what you're told; there'd be chaos if everyone thought for
themselves." -- Top Dog hotdog stand, Berkeley, CA

Aaron Zinck
2005-01-23, 17:38
You can simply use one of the many tag editors that are available (most
music managers/players also have tag editing functionality to some
extent)--almost all will let you change single fields across many files en
masse (so you can select all your "fleetwook mac" and change it to
"fleetwood mac" in one fell swoop. As I'm a Windows user I don't know that
I can point you in the right direction as to the best Linux software to use.
I'm sure you can find many recommendations already on this mailing list, or
maybe someone wants to offer a suggestion? I just did a quick search on the
mailing list and saw someone recommended easytag for Linux--so that'll get
you pointed in the right direction.

"Damon Riley" <damonriley (AT) alumni (DOT) umass.edu> wrote in
message news:41F40162.7000502 (AT) alumni (DOT) umass.edu...
> Hi, Aaron. Before I could reply to your question, I had to look up id3.
> I'm still a greenhorn when it comes to digital music. No, I hadn't
> altered the tags, I had only altered the m3u playlist and file structure.
>
> Can I just pry open each .ogg file with emacs and replace Fleetwook with
> Fleetwood and then save? That sounds tedious, so perhaps I'd be better
> off re-ripping the disc, being careful to proofread the data, no?
>
> -- Damon
>
> Aaron Zinck wrote:
> > Damon, I know this was discussed at some length in an earlier thread. I
> > never heard definitively if you repaired the id3 tag info. Slimserver
> > gathers its data primarily from the id3 tags. If freedb looked up the
> > (incorrect) info and that's how you got the fleetwook mac directory to
begin
> > with then it's highly likely that it tagged each of those files as
having
> > the artist fleetwook mac. Have you fixed the tags?
> >
> >
> > "Damon Riley" <damonriley (AT) alumni (DOT) umass.edu> wrote
in
> > message
news:41F3F2C9.5020107 (AT) alumni (DOT) umass.edu...
> >
> >>I'm seeing something similar with the slimserver running on Linux.
> >>Neither rescan nor wipe cache seems to be able to get rid of the
> >>misspelled Fleetwook Mac directory, although rescanning does find new
> >>artitsts. I dunno what's going on. I'm using slimserver 5.4.0.
> >>
> >>Here's what I see using the command line:
> >>
> >>smb: \mp3\> ls fleetwoo*
> >> fleetwood_mac D 0 Wed Jan 12 15:18:47
> >> fleetwood_mac-rumors.m3u 431 Wed Jan 12 15:20:48
> >> fleetwood_mac-say_you_will.m3u A 835 Wed Jan 12
14:56:49
> >>
> >>
> >>As you can see, there is no fleetwook_mac, but I find it when I use the
> >>web interface.
> >>
> >>If I play a track from "fleetwook_mac" then I can see that the path to
> >>the file is correct-- that it uses fleetwood_mac. But no matter how
> >>many times I have rescanned and wiped, the non-existent artist
> >>"fleetwook_mac" persists. This is what I get for not proofreading the
> >>freedb disc info.
> >>
> >>And I don't even LIKE Fleetwood Mac that much! It's my wife's disk. OH
> >>THE INJUSTICE! :-)
> >>
> >>-- Damon
> >>
> >>dbls wrote:
> >>
> >>>The FAQ item 'What is the difference between the "Rescan" and
> >>>"Wipe Cache" buttons?' reads:
> >>>
> >>> The Rescan button should find any changes made to you [sic]
> >>> music library. When the MP3 Tag Database is being used, it
> >>> is possible that data in the cache can be corrupt. If that
> >>> is the case, the "Wipe Cache" button can be used to make
> >>> the server rebuild everything from scratch.
> >>>
> >>>The first sentence is simply untrue. My server is set to
> >>>rescan at midnight, and a CD I added three days ago still
> >>>hasn't shown up. (I have deliberately chosen not to wipe
> >>>cache yet out of a perverse curiosity about whether Rescan
> >>>will ever find the new CD.) And since "Browse Music Folder"
> >>>doesn't actually read the folder contents in real time, but
> >>>apparently relies on the cache to follow the directory tree, I
> >>>can't find it that way either.
> >>>
> >>>As far as needing to wipe cache to correct corrupt tag data,
> >>>when I changed some track titles in the tags for an album
> >>>recently, the new titles appeared almost instantaneously,
> >>>without doing a rescan.
> >>>
> >>>So it looks to me like SlimServer is reading the tags in real
> >>>time, which is not what I would expect. It does *not* read
> >>>the music folder in real time when I "Browse Music Folder",
> >>>as I would expect. Rescan...does what? Checks to see whether
> >>>the physical files for tracks that are in the database are
> >>>still there? The FAQ statement implies that it doesn't
> >>>correct tags (you must wipe cache for that), so what *does* it
> >>>do?
> >>>
> >>>One hopes that this confusion will be cleared up with the
> >>>advent of the SQL backend.
> >>>
> >>>(Server: Win98SE, 400MHz Pentium II, 384MB ram, SlimServer
> >>>5.4.1)
> >>>
> >>>-:- dbls
> >>>
> >>>
>
>>>------------------------------------------------------------------------
> >>>
> >>>

Damon Riley
2005-01-24, 06:06
OK. At the command line I tried: easytag

The program is apparently installed (you get so much with a Linux distro
that it's hard to know what it all does). It launched and scanned my
mp3 folder automatically. I found the offending tags and changed them.
I used "wipe cache" and now Fleetwook Mac is just a memory. Thanks,
Aaron and everyone else who tried to make me understand!

-- Damon

Aaron Zinck wrote:
> You can simply use one of the many tag editors that are available (most
> music managers/players also have tag editing functionality to some
> extent)--almost all will let you change single fields across many files en
> masse (so you can select all your "fleetwook mac" and change it to
> "fleetwood mac" in one fell swoop. As I'm a Windows user I don't know that
> I can point you in the right direction as to the best Linux software to use.
> I'm sure you can find many recommendations already on this mailing list, or
> maybe someone wants to offer a suggestion? I just did a quick search on the
> mailing list and saw someone recommended easytag for Linux--so that'll get
> you pointed in the right direction.
>
> "Damon Riley" <damonriley (AT) alumni (DOT) umass.edu> wrote in
> message news:41F40162.7000502 (AT) alumni (DOT) umass.edu...
>
>>Hi, Aaron. Before I could reply to your question, I had to look up id3.
>> I'm still a greenhorn when it comes to digital music. No, I hadn't
>>altered the tags, I had only altered the m3u playlist and file structure.
>>
>>Can I just pry open each .ogg file with emacs and replace Fleetwook with
>>Fleetwood and then save? That sounds tedious, so perhaps I'd be better
>>off re-ripping the disc, being careful to proofread the data, no?
>>
>>-- Damon
>>
>>Aaron Zinck wrote:
>>
>>>Damon, I know this was discussed at some length in an earlier thread. I
>>>never heard definitively if you repaired the id3 tag info. Slimserver
>>>gathers its data primarily from the id3 tags. If freedb looked up the
>>>(incorrect) info and that's how you got the fleetwook mac directory to
>
> begin
>
>>>with then it's highly likely that it tagged each of those files as
>
> having
>
>>>the artist fleetwook mac. Have you fixed the tags?
>>>
>>>
>>>"Damon Riley" <damonriley (AT) alumni (DOT) umass.edu> wrote
>
> in
>
>>>message
>
> news:41F3F2C9.5020107 (AT) alumni (DOT) umass.edu...
>
>>>>I'm seeing something similar with the slimserver running on Linux.
>>>>Neither rescan nor wipe cache seems to be able to get rid of the
>>>>misspelled Fleetwook Mac directory, although rescanning does find new
>>>>artitsts. I dunno what's going on. I'm using slimserver 5.4.0.
>>>>
>>>>Here's what I see using the command line:
>>>>
>>>>smb: \mp3\> ls fleetwoo*
>>>> fleetwood_mac D 0 Wed Jan 12 15:18:47
>>>> fleetwood_mac-rumors.m3u 431 Wed Jan 12 15:20:48
>>>> fleetwood_mac-say_you_will.m3u A 835 Wed Jan 12
>
> 14:56:49
>
>>>>
>>>>As you can see, there is no fleetwook_mac, but I find it when I use the
>>>>web interface.
>>>>
>>>>If I play a track from "fleetwook_mac" then I can see that the path to
>>>>the file is correct-- that it uses fleetwood_mac. But no matter how
>>>>many times I have rescanned and wiped, the non-existent artist
>>>>"fleetwook_mac" persists. This is what I get for not proofreading the
>>>>freedb disc info.
>>>>
>>>>And I don't even LIKE Fleetwood Mac that much! It's my wife's disk. OH
>>>>THE INJUSTICE! :-)
>>>>
>>>>-- Damon
>>>>
>>>>dbls wrote:
>>>>
>>>>
>>>>>The FAQ item 'What is the difference between the "Rescan" and
>>>>>"Wipe Cache" buttons?' reads:
>>>>>
>>>>> The Rescan button should find any changes made to you [sic]
>>>>> music library. When the MP3 Tag Database is being used, it
>>>>> is possible that data in the cache can be corrupt. If that
>>>>> is the case, the "Wipe Cache" button can be used to make
>>>>> the server rebuild everything from scratch.
>>>>>
>>>>>The first sentence is simply untrue. My server is set to
>>>>>rescan at midnight, and a CD I added three days ago still
>>>>>hasn't shown up. (I have deliberately chosen not to wipe
>>>>>cache yet out of a perverse curiosity about whether Rescan
>>>>>will ever find the new CD.) And since "Browse Music Folder"
>>>>>doesn't actually read the folder contents in real time, but
>>>>>apparently relies on the cache to follow the directory tree, I
>>>>>can't find it that way either.
>>>>>
>>>>>As far as needing to wipe cache to correct corrupt tag data,
>>>>>when I changed some track titles in the tags for an album
>>>>>recently, the new titles appeared almost instantaneously,
>>>>>without doing a rescan.
>>>>>
>>>>>So it looks to me like SlimServer is reading the tags in real
>>>>>time, which is not what I would expect. It does *not* read
>>>>>the music folder in real time when I "Browse Music Folder",
>>>>>as I would expect. Rescan...does what? Checks to see whether
>>>>>the physical files for tracks that are in the database are
>>>>>still there? The FAQ statement implies that it doesn't
>>>>>correct tags (you must wipe cache for that), so what *does* it
>>>>>do?
>>>>>
>>>>>One hopes that this confusion will be cleared up with the
>>>>>advent of the SQL backend.
>>>>>
>>>>>(Server: Win98SE, 400MHz Pentium II, 384MB ram, SlimServer
>>>>>5.4.1)
>>>>>
>>>>>-:- dbls
>>>>>
>>>>>
>>
>>>>------------------------------------------------------------------------
>>>>
>>>>>