PDA

View Full Version : Browse Albums for the title 'The'



dfk
2005-10-28, 12:08
Hi

My apologies if this has been asked a million times already.

When browsing by album is it possible to group albums that have the title 'The' under T? For example I have an album entitled 'The Singles' which is being filed under 'S' and an album called 'The very Best Of' being filed under 'V'

I have removed the word 'The' from the servers behaviour section (Articles To Ignore When Sorting) but this made no difference.

Thanks

dfk

MrC
2005-10-28, 12:17
Go to Server Settings->Behavior. Remove the "The" from Articles To Ignore When Sorting and press Change. I'm not sure if you need to rescan, or if this setting is dynamic. Perhaps you can report back which it is.

dfk
2005-10-28, 12:21
Go to Server Settings->Behavior. Remove the "The" from Articles To Ignore When Sorting and press Change. I'm not sure if you need to rescan, or if this setting is dynamic. Perhaps you can report back which it is.


Just done a 'Look for new and changed music' rescan and that did not work so now doing a full 'Clear library' rescan I will let you know if that works :-)

Thanks

dfk
2005-10-28, 12:34
Doing a full rescan after removing 'The' from the Articles To Ignore When Sorting section of the server did not resolve this either.... Still being filed the same way.

SlimServer Version: 6.2.1 - 4900 - Windows XP - EN - cp1252

MrC
2005-10-28, 12:48
Its working for me. Make sure your setting is indeed changed.

Try stopping your server, and then deleting the server\Cache folder, and then restart the server.

dfk
2005-10-28, 13:34
Its working for me. Make sure your setting is indeed changed.

Try stopping your server, and then deleting the server\Cache folder, and then restart the server.

MrC

Your suggestion worked for me, thanks very much. Does the program need to be changed so that this works without having to delete the cache folder?

MrC
2005-10-28, 15:45
Glad it worked out.

You know, it is very difficult to know when clearing the .db file or cache is required, since this is primarly up to what changes the developers have made. I tend not spend much time trying to get ontop of such transient details. I think my brain has filled to capacity! :-) Sometimes I think its just best to hit something with a hammer, and be done with it.

dean
2005-10-28, 16:07
We should automatically trigger the rescan when the user makes a
change to a setting that requires it.

That said, it would be even better to make all the options dynamic,
so rescanning can be a fond memory.

On Oct 28, 2005, at 3:45 PM, MrC wrote:

>
> Glad it worked out.
>
> You know, it is very difficult to know when clearing the .db file or
> cache is required, since this is primarly up to what changes the
> developers have made. I tend not spend much time trying to get ontop
> of such transient details. I think my brain has filled to capacity!
> :-) Sometimes I think its just best to hit something with a hammer,
> and be done with it.
>
>
> --
> MrC
>

MrC
2005-10-28, 16:15
We should automatically trigger the rescan when the user makes a
change to a setting that requires it.

By "should", do you mean "currently are", or do you mean "to be implemented"? Experience indicates the latter, or a bug.



That said, it would be even better to make all the options dynamic,
so rescanning can be a fond memory.

Agreed - that would be best. It seems like all these tags and metadata should be scanned once, and carved-up as per user-settings on the fly.

kolepard
2005-10-28, 16:17
>it would be even better to make all the options dynamic, so
>rescanning can be a fond memory.

Ooooo. You wouldn't tease us, would you?

Kevin
--
Kevin O. Lepard
kolepard (AT) charter (DOT) net

Happiness is being 100% Microsoft free.

kdf
2005-10-28, 16:53
Quoting MrC <MrC.1xmxvb (AT) no-mx (DOT) forums.slimdevices.com>:

>
> dean Wrote:
>> We should automatically trigger the rescan when the user makes a
>> change to a setting that requires it.
>>
> By "should", do you mean "currently are", or do you mean "to be
> implemented"? Experience indicates the latter, or a bug.

some features to trigger one, like activating musicmagic, itunes,
moodlogic, or
changing the music folder. Its not hard to trigger a rescan in
reaction to the
pref change. The warning in text would be critical, so that users know
that IF
they change it they WILL cause a rescan. Some users will be upset anyway.
(just wait for the requests that all operations must have a
confirmation dialog
;)

>>
>> That said, it would be even better to make all the options dynamic,
>> so rescanning can be a fond memory.
>>
> Agreed - that would be best. It seems like all these tags and metadata
> should be scanned once, and carved-up as per user-settings on the fly.

some are easier than others. ideally, one scan would be great. but, how much
extra memory is then required to hold all the extra data 'just in case' a user
changes their prefs down the line. What about the users who just want to set
and forget without having to suffer the added resources to appease the
user who
wants to shift between grouped and multi-disks on a daily basis :)

There may be easy answers to this. I'm no db expert, so I can't say. I
tend to
just put up with however it works. Sometimes the annoyances go away (with or
without my help), sometimes I'm 'forced' to accept new ones (even writing code
doesn't mean I get everything the way I want). What does bother me is that
once a change is made, there will be those who will come out screaming if we
don't think about those questions ahead of time.

I am hesitant to say all of this, becuase there are those who will
claim to see
blame in all of this. I assure you all, there is none. These are general
concerns of mine that really address the entire project and not just this
specific topic. Case in point, slimserver used to be 'read on-the-fly' and
store everything in memory. Users complained and we now have a db. Now, you
start seeing requests to not have to be tied to a db and be able to
read on the
fly and store everything in memory. I'm over-simplifying to highlight the
symmetry :)

well, thats my rant. If I'm full of crap...just ignore me :)
-k

MrC
2005-10-28, 17:34
These are all good points KDF, and appreciate as always you're taking the time to provide excellent feedback.

I have not spent time learning the current implementation. It feels like scanned data is manipulated then stored vs stored as found and then manipulated prior to presentation. My thinking for these preferences settings, such as ignored articles (the, a, las, los, etc.), is that the full title would be stored in the DB as found on disk, but then filtered and manipulated per user-preference when presented on the page. No need to re-scan the music folders. I certainly wouldn't want to hold this in RAM.

Anyway, i'm sure this things have been discussed time and again by all, and there are good plans in the works.