Hi all,

Nice work, Amarok shows much promise.

One suggestion however. It would be great if there was a more hierarchical means to browse the collection. I would love to have something like sub-genres. For example, Classical->ChamberMusic, Classical->Opera, Rock->Punk, etc. Ideally such a hierarchy would allow any degree of sub-branches, and for extra points, would allow different default sorting methods to be defined for each branch (which would help address the single-artist album/compilation album problem).

I tried to simulate this with a playlist hierarchy, but this was too clunky, undynamic and fragile (esp. with a large collection)

I can see this goes somewhat outside the ID3 paradigm, and is perhaps incompatable with the Amarok Collection paradigm (unless the collection manager allowed a more flexable tree definition). Maybe it could be a smart playlist type situation, with the collection DB remembering sub-genre (or super-genres).

Cheerio

Hi...

I've posted a similar idea some time ago on the german forum.

My idea was to create smart playlist as parents and children. So the child playlists are given the ability to inherit parts of their parent playlist.
For example the parent playlist filters out all rock music (by genre: rock). Now my mp3 files have subgenres entered in their comment field (like: classic, garage, punk, etc.). The child playlist could inherid the genre:rock from its parent and define an additional filter comment:classic. So this would give me only classic rock music. The next child could define a range year:from-to and so on... So you could get a tree structure of you music without much typing.

Hope i could make clear what i mean

greets oC