Print

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

[tseipel]

Hello,

I encode my media in ALAC/AIFF (iOS devices) and have employed the Album Artist Sort Order field in iTunes such that Bob Dylan is alphabetized in "D" as opposed to "B." Is there a way to enable this field (ALBUMARTISTSORTORDER or TSO2) in MC? Anyone's help in this matter would be greatly appreciated.

Thanks,
Tim

[MrC]

Howdy - have a read here:

   http://yabb.jriver.com/interact/index.php?topic=75896.0

[tseipel]

Thank you so much for your prompt (and very helpful) reply. I am officially a MC convert.

Tim

[tseipel]

I apologize for my ignorance, but I am still unable to view (and thus sort by) Album Artist Sort Order. I have created the new field, naming it Album Artist Sort Order. I have made acceptable value "albumartistsortorder" and have placed "albumartistsortorder=" in the search field.

Any other ideas?

Thanks,
Tim

[MrC]

The Acceptable Value area is where you'd configure a set of values to which Album Artist Sort Order would be restricted.  So you'd want to leave this area of the field definition blank.  In other words, any value is acceptable.

There is probably no reason to add a value to the search field, as the Artist fields will probably cover any searches.  But it is safe to leave it - if so, consider making it an abbreviation so you can enter it in Search more quickly.

Once you've made the changes, then you can select the file(s), and perform Library Tools > Update Library (from tags) to re-read the tags and have this field populated with the file's tags.  Check this by looking at the field in the Tag Action Window.  You'll probably need to add the field in the TAW's view - right click the view to see the options.

More info about the Manage Fields dialog:

    http://wiki.jriver.com/index.php/File_Properties_(tags)

[Matt]

Should we be thinking about making these sort fields standard, reading / writing them from tags, and using them?

[MrC]

Probably.  I know a number of people have asked about them, and workarounds, over the years.

AlexB will probably have the best understanding of all the details - he always does a spectacularly thorough job.

I know vagskal has expressed interest too.

[Link]

Should we be thinking about making these sort fields standard, reading / writing them from tags, and using them?

Yes.  No one currently does a good job explaining this to users - I think it would be a commendable step.

I myself have battled thru years of tweaking and learning to get my huge library to play nicely in both the MC and Squeezebox world..... took me awhile to figure out the secret recipe of fields - would like to think that everyone wouldn't need to learn what I did.

(My main views are built around an assumption that I want things viewed/sorted just like they used to be in Record store bins....I have ARTISTSORT and ALBUMARTISTSORT set correctly and sort on a CUSTOMSORT field defined as If(IsEmpty([ALBUMARTISTSORT]),[ARTISTSORT],[ALBUMARTISTSORT]))

[vagskal]

Should we be thinking about making these sort fields standard, reading / writing them from tags, and using them?

By all means. Some sort fields are included in the ID3v2.4 "standard" (artist, album artist and title, but not composer and album, I think). I think many Squeezebox users use these tags since Logitech Media Server supports them. And you could build cool tools to automatically populate those fields, or just let MrC show us the magic of Regex. If you support those fields you might want to revise the default sort order so that sorting is done by those fields if available. And you would have to consider if those fields should override the ignore "the" etc option (I think they should).

(I am used to finding Bob Dylan under B on my computer so I do not bother with these tags. My vote for extended tag support goes instead to the original year tags, TORY etc.)

[Stopeter44]

Should we be thinking about making these sort fields standard, reading / writing them from tags, and using them?

I moved from iTunes to JRiver and it was the bugbear that took me time to work around. Now I'm doing it again, because I've decided to use  squeezebox again, where ARTISTSORT and ALBUMARTISTSORT are used for sorting. THe hint (CUSTOMSORT) earlier in this thread has been a great help to help me get things the way I want.

So, yes, I vote for standard sort fields in JRiver

[6233638]

My vote for extended tag support goes instead to the original year tags, TORY etc.

It looks like TORY was replaced with TDOR:

TDOR
   The 'Original release time' frame contains a timestamp describing
   when the original recording of the audio was released. Timestamp
   format is described in the ID3v2 structure document [ID3v2-strct].

But official support for this would be nice - I just added a custom field to achieve that recently. (using [Date] to sort by the original release, and adding [Release Date] for that version's release)

[vagskal]

It looks like TORY was replaced with TDOR:

Yes, I know but I am still using ID3v2.3.

Like you I am using a custom TXXX field in MC (actually two fields, one for the original release date and one for the date when the audio was recoded), but since I want the standard TORY tag written to the music files I have to use MP3Tag to keep the tags in sync.