Print

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

[Vlad]

Matt, the last time we spoke (late last year I think) you couldn't understand why I would want some of the custom viewing features avalable in Siren (R.I.P.).  Well, how about this.  I've been listening to and cataloguing operatic stuff over the last few days.  For my classical stuff, I rename the Custom 1 & 2 fields to Composer and Work.  I also set the columns to make these 2 fields prominent.

Tonight I'm still cataloguing operatic stuff, but listening to more contemporary music.  What's been annoying me all evening is that when I am searching for something to play, I am loosing valuable, prime real-estate to 2 unused fields.  

Getting back to the classical, I'd also like to know the Conductor and Orchestra for each track and construct views according to them, but I must choose between them because there are only 3 custom fields and I'm already using 2.

Next I want to move on to my jazz vocals and record the songwriter for each track.  I could use the renamed custom field, "Composer" but it would be nice to use "Songwriter".

These are very simple examples but they illustrate the point.  You want to view the data in different ways depending on what kind of music you are looking at.  That boils down to independently configurable views by Playlist/Smartlist membership.

Ideally each Playlist or Smartlist should have an unlimitted number of uniquely named custom fields.  Each should have independently configurable column sequences and at least a 3 key sort sequence.

How about it for MJ9?  Your new APE metadata means you can support any number of custom fields.  You store them all as "custom n" so you have to translate them anyway.  Why not store a  custom translation for each view?

I noticed a discussion recently about the ecplorer view in Siren that does not rely on importing.  I think it's a pretty cool feature too.

On the subject of custom views, I just can't work out how the sequencing works on the Playing Now view.  Can someone please explain the philosophy?

[JimH]

Vlad,
For play order, please check how you have your sorting set.  It's in MJ settings.

On creating custom views for different types of music, it's a reasonable thing to do, but we are already fighting complexity.  Many new users are overwhelmed with what MJ does now.

There will be some additional flexibility in the database for v9.

Did you try dragging the separator for the field titles?  You can make most fields disappear if you don't want to see them.

[Vlad]

JimH, the MJ sorting is global.  Siren allows independent sorting for every view.  The equivalent of MJ's Playlists and Smartlists (and Media Liabrary View Schemes for that matter).

All the column adjusting features are fine, but they too are global.

I understand the complexity issue.  Are you familiar with the Siren interface for customising views?  It's simple and intuitive but VERY powerfull.  It takes very little real-estate and if you don't want to use it, you don't even need to know that it's there.  It really is very neat.

How about more custom fields, even if only for APE files?  Any chance of that for MJ9?

[Matt]

How about more custom fields, even if only for APE files? Any chance of that for MJ9?

Version 9 will have totally flexible fielding.

Also, remembering sorting and columns on a per view or per root basis is something we're considering.

Take care.

-Matt

[Vlad]

Oh Matt, you tease.  You're giving me false hope, aren't you?

I long to see MJ transcend mere excellence and attain perfection