View Issue Details

IDProjectCategoryView StatusLast Update
0006513MediaMonkey (current)Framework: Taggingpublic2010-10-20 03:51
Status resolvedResolutionno change required 
Product Version 
Target VersionFixed in Version 
Summary0006513: MP3 tagging: Encoder is stored to wrong tag field
DescriptionDuring debugging 0006499 I found that we write/read encoder to the ID3v2 field:

 { TSSE } ID3FID_ENCODERSETTINGS, //< Software/Hardware and settings used for encoding */

but the other apps like iTunes stores it to the field:

 { TENC } ID3FID_ENCODEDBY, //< Encoded by */

Shouldn't we change this to be compatible?
TagsNo tags attached.
Fixed in build



2010-09-29 15:00

developer   ~0020623

Assign to me for fix (if you agree).


2010-09-29 15:16

administrator   ~0020624

I don't know whether any other software does it differently, but I think that we do it absolutely right, given description of these frames from

   The 'Software/Hardware and settings used for encoding' frame
   includes the used audio encoder and its settings when the file was
   encoded. Hardware refers to hardware encoders, not the computer on
   which a program was run.

   The 'Encoded by' frame contains the name of the person or
   organisation that encoded the audio file. This field may contain a
   copyright message, if the audio file also is copyrighted by the

So, I don't think we should do anything about it.


2010-09-29 15:52

developer   ~0020628

I would expect the Encoder field in MediaMonkey to show "Encoded by" info rather than "encoder settings"

for sample file including fields
TENC: iTunes 6.0.3
TSSE: Variable Bit Rate 269 kbps

I would expect MM to show "iTunes 6.0.3" instead fo "Variable Bit Rate 269 kbps".

Maybe we could somehow concatenate the values to the Encoder field?
But this is probably a low priority issue.


2010-09-29 17:24

administrator   ~0020629

I think that description is pretty clear - TENC is for _person_, while TSSE is both for software and its settings. I.e., iTunes filled in values are clearly wrong. We could consider some changes, but only in case we find out the more applications take this (incorrect) approach.