INTERACT FORUM

I've spent close to a month and a lot more hours that I hoped to changing and improving Metadata tags for my CD files, renaming composers, artists (which I define as performers), album names, genres, and standardizing language and naming conventions used in my classical library so that everything is comparable.  I notice that Metadata usually comes up short and there seems to be no consistency with naming conventions and how tags are used.

There is probably no answer to this but just wondering why there can't be common conventions for Metadata that would help reduce the need for this?

This is an age old question without a solid answer to be perfectly honest. One of the places I started when I really started thinking about this seriously was by looking at the DDEX standards and how they've laid stuff out.

I mean, if we want to get really into the weeds, even something as simple as the catch all term "Album" is semantically, f*cking useless. Why we're still using it, I have no clue.

... you're assuming it's not self-ripped

Mr. Swordfish uses JRiver so it's not possible he created bad rips.

How about we try this in a coming build:
NEW: Skins look for a ContinuousStopButton image and use it for the stop mode if found.
NEW: Skins look for a ShuffleAutoButton button and use it for the auto shuffle mode.

Sounds great (both "if found").

I will reveal my button images after testing!   

How about we try this in a coming build:
NEW: Skins look for a ContinuousStopButton image and use it for the stop mode if found.
NEW: Skins look for a ShuffleAutoButton button and use it for the auto shuffle mode.

Thanks for the help.

Yeah, compared to other audio playback formats, Atmos is not well established and at least for me, it's been an adventure to figure out the best way to handle it both for playback and tagging. 

With JRiver, I've tried MKA, MKV, MP4, BDMV backup, cue sheet, sidecars and it all mostly works, but there always seems to be a gotcha.

Not possible today.  We could add support but no skins made yet support them.

Not a problem if I can now add them to my own custom skin.  That is what I am looking for.

Maybe others will add them later once they become available.  So you will have to maintain the current behavior as default if image is not specified, but allow for distinct images going forward.

Next build we'll do this:
NEW: An option to show the image Action Window is presented in the menu on the image in the tag window.

I have this option on and with the default skin it looks right.  Could you post a screenshot showing the problem?  Thanks.

Not possible today.  We could add support but no skins made yet support them.

Wow! Yes, that's it exactly... a nice simple fix. Thanks so much. Now I'll read through all the posts this question generated...always interesting!

Your welcome. As for all the other replies, it was mainly just me hi-jacking your thread to push for a request that was directly related your question - hopefully Matt incorporates it (crossing my fingers).