# \[X\] minor imperfection in Vobris Tag editor

**URL:** https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724
**Category:** No Bugs
**Created:** [August 5, 2009, 6:57am UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724 "2009-08-05T06:57:13Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![\_shadowman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/_/ecae2f/32.png) [@\_shadowman](https://community.mp3tag.de/u/_shadowman)
#### Post date: [August 5, 2009, 6:57am UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/1 "2009-08-05T06:57:13Z")

</div>

Mp3tag 2.43c doesn't correct vobris field names to uppercase.  
[http://www.xiph.org/vorbis/doc/v-comment.html](http://www.xiph.org/vorbis/doc/v-comment.html)  
Mp3tag (like most software players) can read vobris field name in any case, but it didn't correct vobris field according to vobris standard filed name examples to uppercase.  
I notice this problem when my iRiver LPlayer didn't read some tags.  
Primary tags were created by unknown software.(I downloaded that album).

Example from file "Anima Noir.flac":  
TITLE=Anima Noir \<-- recognize  
ALBUM=Anima Noir \<-- recognize  
Artist=Theatres Des Vampires \<-- not recognize (should be ARTIST)  
Genre=Gothic Black Metal \<-- not recognize (should be GENRE)  
Date=2008 \<-- not recognize (should be DATE)

But in case of recreation(not edition) of tag field - everything works fine.

However vobris spec claims case-insensitive but standard tags placed in uppercase.  
Possible this is not bug, but mp3tag creates filed names in uppercase so it should also correct field names to uppercase. (and for better hardware compatibility)

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 10, 2009, 5:34pm UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/2 "2009-08-10T17:34:46Z")

</div>

There have been many discussions on this before (mainly because the Vorbis Comments specification does not restrict you to using upper-case field names only). Some users prefer upper-case field names while other like the capitalized naming scheme (especially when using programs that directly displays those field names).

I decided for flexibility and created an additional option for the Case Conversion action that allows for case conversion also on field names.

Kind regards,  
Florian

---

<div class="post-metadata">

### Author: ![\_shadowman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/_/ecae2f/32.png) [@\_shadowman](https://community.mp3tag.de/u/_shadowman)
#### Post date: [August 10, 2009, 6:30pm UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/3 "2009-08-10T18:30:42Z")

</div>

Thanks.

But then another problem.  
"extended tags" shows every tag in uppercase, so I don't know, are they in uppercase for real or not.  
Example with the same track(using Mp3tag2.43d and WinAmp):

 ![](https://community.mp3tag.de/uploads/default/original/2X/1/1ef853c69ad4f27380aaeb8e2c851660816e3c0d.gif)  

Or should I start another topic for this?

 ![](https://community.mp3tag.de/uploads/default/original/2X/1/1ef853c69ad4f27380aaeb8e2c851660816e3c0d.gif)  

 ![](https://community.mp3tag.de/uploads/default/original/2X/0/0767664c8a74ac2663c4eabb27b1783047a68d4b.gif)

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 10, 2009, 6:53pm UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/4 "2009-08-10T18:53:04Z")

</div>

Just run the action to be sure that all field names are stored in upper case.

---

<div class="post-metadata">

### Author: ![\_shadowman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/_/ecae2f/32.png) [@\_shadowman](https://community.mp3tag.de/u/_shadowman)
#### Post date: [August 10, 2009, 6:57pm UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/5 "2009-08-10T18:57:09Z")

</div>

And also, after executing "Case Conversion action", case conversion didn't influence "Date" and "Tracknumber" filelds.

 ![](https://community.mp3tag.de/uploads/default/original/2X/0/0767664c8a74ac2663c4eabb27b1783047a68d4b.gif)  
  
while "artist" and "genre" were successfully converted.

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [August 11, 2009, 4:17am UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/6 "2009-08-11T04:17:19Z")

</div>

Mm, yes. These fields are mapped to their Vorbis equivalent at another layer -- I'll see if I find a way to address this.

---

<div class="post-metadata">

### Author: ![\_shadowman](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/_/ecae2f/32.png) [@\_shadowman](https://community.mp3tag.de/u/_shadowman)
#### Post date: [August 11, 2009, 7:31am UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/7 "2009-08-11T07:31:13Z")

</div>

I used "Case Conversion action" to all vobris tag fileds listed  
[http://www.xiph.org/vorbis/doc/v-comment.html](http://www.xiph.org/vorbis/doc/v-comment.html)  
and in addition to "Date" and "Tracknumber" there is same problem for "Organization".  
For the rest fields "Case Conversion action" works fine.

Waiting for Mp3tag 2.43e 🙂

---

<div class="post-metadata">

### Author: ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)
#### Post date: [December 28, 2018, 2:26pm UTC](https://community.mp3tag.de/t/x-minor-imperfection-in-vobris-tag-editor/8724/8 "2018-12-28T14:26:23Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
