----- Original Message -----
From: "kdf"
> you must be careful to have your matching patterns in the order
> that bet fits. The server does actually guess very well given
> the right patterns. However, if the server can manage to match
> the first pattern then it will, even if the whole path isn't
> involved.
>
> if you have a better way, and can provide a patch, that would be
> more than welcome.
>
> -kdf
What really baffles me is that Slimserver is even looking
at the part of the file name that contains the music
library. My top two Guess Tag formats are:
ARTIST/ALBUM/TRACKNUM TITLE
ARTIST/ALBUM/TITLE
and yet Slimserver insists upon using the server name for
ARTIST and the main folder name for ALBUM, with every
track title being the artist name, and is throwing away
the most significant part of the file name.
I'd love to write a patch, but I don't know Perl (yet); I
could write what's needed in about ten minutes in APL.
Frankly, I don't understand how "Guess Tags" can work any
other way than what I've stated; the last part of the file
name (after the last / or \) would, with my formats, be
matched with either TRACKNUM TITLE or TITLE, and parsing
would proceed upward from there. Why does Slimserver seem
to start at the highest folder level, when the most
pertinent information is at the end of the name?
I originally had my formats with a leading slash, but in
that case the untagged WAV files weren't found at all,
though I could navigate to them via Browse Music Folder.
Given my library structure, what Guess Tag formats would
work?
-:- dbls
_______________________________________________
Discuss mailing list
[email protected]
http://lists.slimdevices.com/lists/listinfo/discuss
