PDA

View Full Version : Playlist db or tags are read from where? I'm lost......



Robert_W
2006-07-21, 15:56
OK just when I think I'm fairly computer literate I can’t seem to find the answer to what seems to me should be simple.

IE, I have SS pointed to C:/Music which contains all of my files. I’m using EAC to FLAC and am very happy with the results. Here’s my dilemma and forgive if this has been asked and answered…..I looked but couldn’t find…..

When ever I scan, or “clear and scan” my library both of my Squeezeboxes read old information. In other words if I go into windows explorer and manually change files so that “Al DiMeola” and “Al DiMeola Project” and “Al Di Meola, Paco De Lucia, John McLaughlin” and all of the corresponding albums are then moved to be just under a folder called “Al DiMeola” , all of the old information is still there. So when I go to my squeezebox…… "Al DiMeola” and “Al DiMeola Project” and “Al Di Meola, Paco De Lucia, John McLaughlin”…….is what I see even though the directory structure has changed, folders have been deleted etc.

I know that SS saves a file in the Cache folder called “slimserversql.db” and I have deleted it, cleared and rescanned without success.

So my question is where the heck is SS pulling this information from? Are there tags hidden some where that are created by EAC that I can’t find and SS is reading them? I know that when EAC stores database info it does so into a file called “CDDB.DAT” but can’t find anywhere that SS would be pulling / or calling this info from.

It’s probably something very simple and easy that I have overlooked as happens so often with issues like this but any help would be appreciated before I go nuts!

Thank you.

aubuti
2006-07-21, 16:54
You don't say how you are looking at the information. If you make changes to filenames, file locations, directory names, etc. then you should see these changes if you use Browse > Music Folder. BUT, viewed in any other way, slimserver is using metadata from tags that are part of the file. You probably created the tags when you ripped the CDs, as most configurations of EAC --> FLAC have the option of writing tags when encoding to FLAC.

There are a lot of packages available for editing and managing your tags. Check out the tagging section in the SD wiki (http://wiki.slimdevices.com/index.cgi?BeginnersGuideToTagging). On Windows I like mp3tag, which despite the name, also handles FLAC tags. If you're like most people, you'll find that almost all of the tinkering and refining you do with your music information is via the tags, and not via filenames or directories.

JJZolx
2006-07-21, 18:25
So my question is where the heck is SS pulling this information from? Are there tags hidden some where that are created by EAC that I can’t find and SS is reading them?
Tag data is stored within the audio files themselves. While you should keep your music library's directory structure as logically organized as possible, this is mostly for your own benefit, not SlimServer's. Avoid using the folder structure as data for SlimServer.


I know that when EAC stores database info it does so into a file called “CDDB.DAT” but can’t find anywhere that SS would be pulling / or calling this info from.
CDDB.DAT is EAC's own database. No, SlimServer won't see this information.


It’s probably something very simple and easy that I have overlooked as happens so often with issues like this but any help would be appreciated before I go nuts!
Well, you can't view the tags without using some software that can read them, so no wonder you're a little confused.

Get a good tag editing program. You'll need it to make corrections that will be seen in SlimServer (following a library rescan). I use and highly recommend Mp3tag.

http://www.mp3tag.de/en/

JJZolx
2006-07-21, 18:28
One other thing I should mention... If you move or rename your audio files after SlimServer has scanned the library, then it won't be able to find or play them until you rescan.

Robert_W
2006-07-21, 20:20
Thank you guys, it makes much more sense now. I always thought that the tag info was stored in a seperate file some where. Big Duh on my part but I'm fairly new to this ripping and encoding thing.

I'll try mp3tag.