# Vorbis/Flac Comments field case modification

**URL:** https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819
**Category:** General Discussion
**Created:** [August 30, 2012, 6:47pm UTC](https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819 "2012-08-30T18:47:16Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![Casper](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/b4bc9f/32.png) [@Casper](https://community.mp3tag.de/u/Casper)
#### Post date: [August 30, 2012, 6:47pm UTC](https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819/1 "2012-08-30T18:47:16Z")

</div>

Hi all

I would like to know if it is possible to have all fields for vorbis comments capitalized.  
Meaning "Artist" would be "ARTIST"; "Album" would be "ALBUM"; "Title" would be "TITLE", and so on and so forth.

I've previously owned a portable music player, and it would not read the tags if they were not capitalized; and ever since, I have kept all my tags formatted the same. Sometimes I need to work on the tags but Mp3tag reverts them back to mixed-case.

I'm sure there should be something that can be done.

Any assistance is welcome.

---

<div class="post-metadata">

### Author: ![JJ\_Johnson](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jj_johnson/32/67_2.png) [@JJ\_Johnson](https://community.mp3tag.de/u/JJ_Johnson)
#### Post date: [August 30, 2012, 7:07pm UTC](https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819/2 "2012-08-30T19:07:57Z")

</div>

You can use a case conversion action with the field specified as \_FIELDNAME. This will rewrite all field names with the designated case conversion. What I recommend is creating an action group to do this, and making sure that it is the last action group that is executed whenever you manipulate any tags. You can also run it by itself using the quick actions button.

You should also find Mp3tag's file view (columns) definition file, named columns.ini and make sure that all of the field names are written in upper case. There will be many column definitions in the file looking something like:

[#18]  
width=246  
numeric=0  
name=Title  
value=%title%  
sort=  
field=%title%  
enabled=1

Make sure all of the 'field' entries are all upper case. For example:

field=%TITLE%

Also, any custom fields that you've created in the tag panel, which are defined in usrfields.ini. Make sure all of the 'value' names are all upper case.

[#2]  
value=ALBUMARTISTSORT  
name=Album Artist Sort:  
multiline=0

---

<div class="post-metadata">

### Author: ![Casper](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/c/b4bc9f/32.png) [@Casper](https://community.mp3tag.de/u/Casper)
#### Post date: [August 30, 2012, 7:13pm UTC](https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819/3 "2012-08-30T19:13:28Z")

</div>

Thanks for the prompt reply.

I will take a look at your suggestions.

Kind regards

---

<div class="post-metadata">

### Author: ![HansBKK](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/h/5daacb/32.png) [@HansBKK](https://community.mp3tag.de/u/HansBKK)
#### Post date: [August 31, 2012, 2:47am UTC](https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819/4 "2012-08-31T02:47:34Z")

</div>

> [@JJ Johnson](#):
>
> You can use a case conversion action with the field specified as \_FIELDNAME. This will rewrite all field names with the designated case conversion.

That's a great tip thanks, my OCD has been bugged by the seemingly random capitalization of my fields where the UIs don't universally UPPER or lower-case them.

I've successfully lower-cased them all within MP3Tag, leaving only my mapped ones as UPPER as a reminder that they don't match the canonical string.

However I've found in some cases this causes other (probably misbehaving) tagdata-scraping software to miss matching up already existing tags, so want to selectively re-ProperCase some fields.

I tried using the weirdly labeled field in that Action ("from or after"?) but that seemed to affect the case of ALL field labels, but just certain letters.

Is there a way to change the case of a specific tag label?

---

<div class="post-metadata">

### Author: ![JJ\_Johnson](https://community.mp3tag.de/user_avatar/community.mp3tag.de/jj_johnson/32/67_2.png) [@JJ\_Johnson](https://community.mp3tag.de/u/JJ_Johnson)
#### Post date: [August 31, 2012, 3:07am UTC](https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819/5 "2012-08-31T03:07:10Z")

</div>

> [@HansBKK](#):
>
> I tried using the weirdly labeled field in that Action ("from or after"?) but that seemed to affect the case of ALL field labels, but just certain letters.

Do you mean 'Words begin from/after any of'? I believe that's only applicable when doing mixed or sentence case conversion.

_Action type:_ **Case conversion**  
_Field:_ **\_FIELDNAME**  
_Case conversion:_ **Mixed Case**  
_Words begin from/after any of:_ **\_-**

This would change REPLAYGAIN\_TRACK\_GAIN to Replaygain\_Track\_Gain. Without designating the underscoree it would be Replaygain\_track\_gain.

> [@](#):
>
> Is there a way to change the case of a specific tag label?

You can use a 'Replace with regular expression' action. The following would change ISRC and UPC. You could add additional field names separated by vertical bars (pipes).

_Action type:_ **Replace with regular expression**  
_Field:_ **\_FIELDNAME**  
_Regular expression:_ **^(ISRC|UPC)$**  
_Replace matches with:_ **$upper($1)**  
 _case-sensitive comparison_

---

<div class="post-metadata">

### Author: ![HansBKK](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/h/5daacb/32.png) [@HansBKK](https://community.mp3tag.de/u/HansBKK)
#### Post date: [August 31, 2012, 8:44am UTC](https://community.mp3tag.de/t/vorbis-flac-comments-field-case-modification/13819/6 "2012-08-31T08:44:02Z")

</div>

> [@JJ Johnson](#):
>
> Do you mean 'Words begin from/after any of'? I believe that's only applicable when doing mixed or sentence case conversion.
> 
> _Action type:_ **Case conversion**  
> _Field:_ **\_FIELDNAME**  
> _Case conversion:_ **Mixed Case**  
> _Words begin from/after any of:_ **\_-**
> 
> This would change REPLAYGAIN\_TRACK\_GAIN to Replaygain\_Track\_Gain. Without designating the underscoree it would be Replaygain\_track\_gain.
> 
> You can use a 'Replace with regular expression' action. The following would change ISRC and UPC. You could add additional field names separated by vertical bars (pipes).
> 
> _Action type:_ **Replace with regular expression**  
> _Field:_ **\_FIELDNAME**  
> _Regular expression:_ **^(ISRC|UPC)$**  
> _Replace matches with:_ **$upper($1)**  
> _case-sensitive comparison_

Brilliant stuff, obviously your knowing and sharing the knowledge, but also a special tip of the hat to the developer(s)!
