hi jezbo!
i find this issue also mightily irritating, so i opened an enhancement
request in bugzilla at:
http://bugs.slimdevices.com/show_bug.cgi?id=6208
if you are in the same camp, you may want to vote for the enhancement.
more votes = more people want this = higher likelyhood of it being
snarlydwarf;259953 Wrote:
It would be much easier to modify the scanner to do as you want. Then
it would work consistently across the web and remote interfaces.
How would I go about doing that ?
--
jezbo
jezbo's
jezbo;260251 Wrote:
... but I also like to collect tracks together and tag it with the same
Album name so that it will appear as an album eg. Mozart is the
artist, Concertos is the album - and these are rarely if ever in the
same folder (and I don't want to have to move them - iTunes
Forget genre - that turned out not to be the issue, but the folder
location of the files is.
I doubt I'm in a 1% minority. True enough, most of my real albums are
stored in the same directory (except when I have downloaded one or two
tracks then later downloaded the rest of the album on the
2) Can you think of two compilation albums with exactly the same
title?
Lady Sings the Blues
--
amcluesent
amcluesent's Profile: http://forums.slimdevices.com/member.php?userid=10286
View this thread:
1) So make it an option - everyone's happy.
2) Can you think of two compilation albums with exactly the same title?
--
jezbo
jezbo's Profile: http://forums.slimdevices.com/member.php?userid=9888
View this thread:
radish;259538 Wrote:
EAC, for example, doesn't have a way of setting COMPILATION.
No, but you can pass the tag to an encoder using the additional command
line options, at least for something like FLAC. I explicitly set the
compilation tag to 0 for all albums, and then manually change it when I
jezbo;259793 Wrote:
1) So make it an option - everyone's happy.
some, not everyone. for example:
-QA who have to test every option
-Support who have to keep track of every option and it's effects when
helping customers diagnose an issue
-Developers who have to continually track each
Whole-heartedly disagree.
I'm a developer myself, and our happiness is not the issue, a product
must be flexible enough to satisfy the majority of customers. Making
some rule rigid so that it only satisfies half the customers, even if
it makes things simpler, is not good practice. And the rule
jezbo;259946 Wrote:
Whole-heartedly disagree.
I'm a developer myself, and our happiness is not the issue, a product
must be flexible enough to satisfy the majority of customers. Making
some rule rigid so that it only satisfies half the customers, even if
it makes things simpler, is not
snarlydwarf wrote:
A ton of customers Just Work with the dropping of Common Album Names
and the must-be-same-album-if-in-same-directory code. Common Album
Names sucked.
Agreed. I don't think it's an unreasonable requirement that tracks from
the same album are in the same directory.
R.
jezbo;259946 Wrote:
I'm a developer myself, and our happiness is not the issue
Depends on whether you're paying said developers ;)
As it is, I won't be using the SlimServer web interface since browsing
of albums is such a pain; I'm writing my own interface that builds it's
own
jezbo wrote:
Whole-heartedly disagree.
I'm a developer myself, and our happiness is not the issue,
Correct. The customers much be happy, which most are.
a product must be flexible enough to satisfy the majority of
customers.
Which it does.
Making some rule rigid so that it only
Oh hang on, it may be breaking it because the files are split across
directories - I've seen some other threads on this. Is there any
resolution to this yet ?
--
jezbo
jezbo's Profile:
I can think of two problems:
1) Your suggestion requires COMPILATION to be correctly set. I would
expect that to be less commonly done in most people's libraries than
keeping to a 1 album per directory model. EAC, for example, doesn't
have a way of setting COMPILATION.
2) What if I have two
15 matches
Mail list logo