Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[michel]

Let me kiss you guys !
No ? Why ?
My name is michele...  

What they do ? A fantastic thing I (and may be others) asked some weeks/months ago. Let describe what I can do with MJ9:

As AMG, I am using 'genre' and 'style' (custom2) fields to set music genre. Again as AMG I set one value for genre ("rock", "jazz", "folk",...) and many values for style (for example: "indie rock, punk").

I create a smartlist per style value (indie/punk/...) and I group these smartlist into a smartlist group called Style.

Then I create a new view scheme this way

GENRE/Style (the smartlist group)/ARTIST/...

The result is very nice. For example, if I set a track with
style=indie, punk
it will appear under rock/indie/artist/... but also under rock/punk/artist/... !

For me it is very cool..

Nice work MJ team.

Just a concern: why the name of the playlist group doesn't appear in the view scheme when it is automatically named ? (now it appears as "playlist")

[michel]

Another little concern (well, return back the kisses ;-)

genre expands only for genre values which exist in the set

artist expands only for artist values which exist in the set

the same for album.

It could be nice if my smartlist group Style would expand also only for style which exist in the set

For example, if I have 3 styles (so 3 smartlists) punk, pop, dance grouped in the smartlist group Style, I get

rock
   punk
         artist1
         artist2
   dance
   pop
         artist3
         artist4

even if dance subset is empty.

I would prefer not to have dance in the tree in this case.

[michel]

Hum... finally two things:

- I think I was wrong thinking it is a new thing of MJ9 (but you can keep the kisses, you deserve anyway ;-)

- it could be a much more powerfull way to do what I would like

Indeed, to use the previous method to browse styles through view scheme you need to create manually as much as smartlists as possible styles. Even without to follow AMG plethora of styles, it could be a lot of styles so it will be paintfull to create and maintain this list of smartlists.

A more powerfull way to do could be to be able to match not only the full string inside a field but also a substring of the field. The more powerful way to match a substring into a string is regexp (regular expression). So MJ would display a view scheme according to the existing values (full value or substring matched by a regexp) of the selected fields.

For example the following view scheme:

genre/style/artist

genre
a particular regexp to extract each substring preceding a ","(custom2)
artist

will display automatically
rock
    punk
    indie
    dance

if I have tracks with these style values:
genre=rock / style=punk, indie
genre=rock / style=dance, punk

=> No more need to create dozen of "style" smartlists and maintain them.

[michel]

That could be useful also for artist. Indeed I many album with several artists (they are not compilation, they are collective artist albums such as "les enfoirés" in France). So it would be as for style:

artist=balavoine, goldman, ...

and a view scheme with the right regexp ARTIST

[Matt]

It could be nice if my smartlist group Style would expand also only for style which exist in the set

It doesn't for speed reasons.  It could be quite slow running through a group of 10's (or in Lise's case 100's) of smartlists to see which ones a set of files belongs to.

I know -- make it optional  

Anyway, thanks Michel and glad you like the view scheme system.