Flexible Tag Mapping
Re: Album release version
It just doesn't look right like this.
- Attachments
-
- Clipboard09.jpg (64.67 KiB) Viewed 26887 times
Re: Album release version
I can't hard-code that since it may not suit others. This is why we need the formatting control in the configuration I think.Morbeas wrote:Thank you so much! But can I have the release info in parenthesis please? (I know, the nerve!).
How are you getting this in there? I thought your release info was in the standard Comment tag.
Re: Album release version
It is in the standard COMMENT tag.musoware wrote:How are you getting this in there? I thought your release info was in the standard Comment tag.
- Attachments
-
- Clipboard09.jpg (54.31 KiB) Viewed 26882 times
Re: Album release version
That's probably OK for FLAC tags, but not for id3v2tags where comment is not a custom/extended tag.Morbeas wrote:It is in the standard COMMENT tag.musoware wrote:How are you getting this in there? I thought your release info was in the standard Comment tag.
Re: Album release version
That's OK for you then! I still want to do my Import Actions idea - basically it's just turning the existing custom tag mechanism round so that it is driven by the Muso Track field - so this column would be first, Tag ID would be renamed "Format Value" and in here you'd have "[BONUS]" for the first and "([COMMENT])" for the second - the items in square brackets just tell it to fetch the custom tag of that ID - this will then put brackets around your comment and store the result in Album Subheader. I'd allow standard fields to be referred to with a different syntax in the format value.
Re: Album release version
You know I'm game, bub. Sounds good to me!
Re: Flexible Tag Mapping
MERGED 3 TOPICS INTO ONE - all 3 are related. I am implementing import actions as described above as an extended replacement for custom tag mappings.
Re: Flexible Tag Mapping
1.5.24 has this change:
Custom Tag mechanism changed to Import Actions (which incorporates custom tags)
Custom Tag mechanism changed to Import Actions (which incorporates custom tags)
- custom tags prefixed by #, eg. #BONUS (spaces in tag IDs not currently supported)
- standard fields to be copied into target field prefixed by @, eg. @AlbumArtist (these available via autocomplete)
- can add fixed text, eg. (@Comment) copies standard comment field into target field and surrounds with brackets
- "Conditional" checkbox only applies rule if all inputs (custom tags and field references) are non-blank, this is important for the (@Comment) example above since we do not want () in the target field when there is no comment.
- Actions are applied in the order defined (can be important).
- Can now define "Tags are Master" as an option to specify that tags will overwrite Muso field values even if the Muso field value exists and is different.
Re: Flexible Tag Mapping
That seems to work nicely. Now I can map "Arranger" into "Performer" as "(Arr. Arranger's name)".
Am I right in assuming that only one tag should be included in each format value?
Am I right in assuming that only one tag should be included in each format value?