# Encoder Version/Brand

**URL:** https://community.mp3tag.de/t/encoder-version-brand/4146
**Category:** General Discussion
**Created:** [December 4, 2006, 8:08pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146 "2006-12-04T20:08:26Z")
**Posts on this page:** 13
**Page:** 1

<div class="post-metadata">

### Author: ![paulskinner](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/p/dbc845/32.png) [@paulskinner](https://community.mp3tag.de/u/paulskinner)
#### Post date: [December 4, 2006, 8:08pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/1 "2006-12-04T20:08:26Z")

</div>

I would love to have a field that knows what version of encoder was used to create a file.  
It would of course be un-editable.

Some examples: Lame 3.97, FHG, Xing, Lame 3.92

[MediaTagger](http://www.volny.cz/media-tagger/eng/) has it, but unfortunately that can't do batch conversion so I've moved over to Mp3tag.  
This is the one thing missing and I'd love to see it implemented in the near future.

This is helpful because I occasionally go back and re-encode some of my files with a newer version of an encoder, and it is handy to know which files are encoded with the old version.

---

<div class="post-metadata">

### Author: ![noroom](https://community.mp3tag.de/user_avatar/community.mp3tag.de/noroom/32/132_2.png) [@noroom](https://community.mp3tag.de/u/noroom)
#### Post date: [December 5, 2006, 10:56pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/2 "2006-12-05T22:56:19Z")

</div>

I would very much like to see this too, as it would save me from having to use Mr. Questionman or Audio Identifier, but sadly, it's been said in the [feature roadmap](https://community.mp3tag.de/t/968/1) that this won't be included. ☹

---

<div class="post-metadata">

### Author: ![Tigerix](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/439d5e/32.png) [@Tigerix](https://community.mp3tag.de/u/Tigerix)
#### Post date: [March 17, 2007, 2:06pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/3 "2007-03-17T14:06:24Z")

</div>

I am using MP3Tag and also the Total Commander Plugin since a short while, but I have the same urge/wish as the other guys here. I really think the encoder field shouldn't be missing in a good tagger.

Is there any technical or personal reason why this feature is in the blacklist of features, Florian?

Anyways: Thanks for this great program. Its so useful to me! Especially the Amazon and Freeddb function is something I have been wishing for since a long time 🙂

---

<div class="post-metadata">

### Author: ![Sebastian\_Mares](https://community.mp3tag.de/user_avatar/community.mp3tag.de/sebastian_mares/32/9285_2.png) [@Sebastian\_Mares](https://community.mp3tag.de/u/Sebastian_Mares)
#### Post date: [March 17, 2007, 4:20pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/4 "2007-03-17T16:20:09Z")

</div>

An accurate detection would take too much time for processing and it's also pretty difficult to implement since there are several factors to consider in order to determine an MP3 encoder. With Vorbis it's not that difficult since you can rely on the vendor string - same applies to MP4 files because most encoders leave a signature. As for FLAC, Musepack, Monkey's Audio or WavPack - there is only one encoder that encodes to those formats (I mean, one encoder per codec). Maybe the encoder version could be interesting, but to be honest, I have no idea if you can find that out.

---

<div class="post-metadata">

### Author: ![Tigerix](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/439d5e/32.png) [@Tigerix](https://community.mp3tag.de/u/Tigerix)
#### Post date: [March 19, 2007, 6:46pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/5 "2007-03-19T18:46:02Z")

</div>

Thanks for your post Sebastian.  
Unfortunately I don't really agree. Have a look at The Godfather MP3 catalog: [http://users.forthnet.gr/the/jtclipper/](http://users.forthnet.gr/the/jtclipper/)  
This software scans for everything it can find in an mp3/or whatever audio file. And is even very fast.

---

<div class="post-metadata">

### Author: ![Sebastian\_Mares](https://community.mp3tag.de/user_avatar/community.mp3tag.de/sebastian_mares/32/9285_2.png) [@Sebastian\_Mares](https://community.mp3tag.de/u/Sebastian_Mares)
#### Post date: [March 20, 2007, 5:10am UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/6 "2007-03-20T05:10:32Z")

</div>

I did not test the software, but does it accurately tell apart MP3s encoded by Blade from ones created by Xing or the various FhG "flavors"?

---

<div class="post-metadata">

### Author: ![Tigerix](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/t/439d5e/32.png) [@Tigerix](https://community.mp3tag.de/u/Tigerix)
#### Post date: [March 20, 2007, 9:33am UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/7 "2007-03-20T09:33:40Z")

</div>

I am not sure if I understand your question. Maybe this helps:  
 ![](http://img201.imageshack.us/img201/8972/shot00076qm0.jpg)

---

<div class="post-metadata">

### Author: ![funta](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/f/8e7dd6/32.png) [@funta](https://community.mp3tag.de/u/funta)
#### Post date: [April 29, 2007, 9:01am UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/8 "2007-04-29T09:01:18Z")

</div>

Also ich hätte auch diesen Feature-Wunsch.  
Ich lösche nämlich immer von Hand das entsprechende Feld in WinAmp.  
Wenn dies automatisiert mit MP3Tag ginge würde mir das ne Menge Zeit ersparen.

Danke + Gruss  
funta

---

<div class="post-metadata">

### Author: ![Sebastian\_Mares](https://community.mp3tag.de/user_avatar/community.mp3tag.de/sebastian_mares/32/9285_2.png) [@Sebastian\_Mares](https://community.mp3tag.de/u/Sebastian_Mares)
#### Post date: [April 29, 2007, 9:05am UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/9 "2007-04-29T09:05:16Z")

</div>

Please stick to English on the International forums!

---

<div class="post-metadata">

### Author: ![JEdwardP](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/j/ba9def/32.png) [@JEdwardP](https://community.mp3tag.de/u/JEdwardP)
#### Post date: [April 29, 2007, 11:10pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/10 "2007-04-29T23:10:03Z")

</div>

AudioShell displays encoder details so well and so conveniently, that I've never missed this feature in mp3tag. And like mp3tag, AudioShell is lightweight, regularly updated freeware. As Sebastian has said however, it's difficult for ANY such program to RELIABLY detect MP3 encoders.

---

<div class="post-metadata">

### Author: ![paulgj](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/p/b5e925/32.png) [@paulgj](https://community.mp3tag.de/u/paulgj)
#### Post date: [August 8, 2007, 3:35am UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/11 "2007-08-08T03:35:23Z")

</div>

I agree it would be nice to see for MP3 files what the encoder was and the version. Foobar will show this info if you right click a file select properties and then the next properties tag under the tool and codec profile fields

[![](http://img235.imageshack.us/img235/4600/foobarcp7.jpg)](http://imageshack.us)

No problem though, I can also fire up Foobar if I want to see

---

<div class="post-metadata">

### Author: ![paulskinner](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/p/dbc845/32.png) [@paulskinner](https://community.mp3tag.de/u/paulskinner)
#### Post date: [August 8, 2007, 6:02am UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/12 "2007-08-08T06:02:33Z")

</div>

We seem to have now reasonably debunked the theory that it would be impossible/very hard to implement encoder detection. Many others have implemented it with high levels of success.

There are many people here who would like it to be present.

It would mean people can differentiate between old rips of their audio and the ones they've ripped with the new encoder version.

Surely this is reason alone to consider implementing it now.

It will mean better quality audio for all!

Go on, go on, go on, go on, go on, go on, go on!

---

<div class="post-metadata">

### Author: ![khjart](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/k/ccd318/32.png) [@khjart](https://community.mp3tag.de/u/khjart)
#### Post date: [August 11, 2007, 8:06pm UTC](https://community.mp3tag.de/t/encoder-version-brand/4146/13 "2007-08-11T20:06:26Z")

</div>

I'd just like to add my vote to this. It should be like like with Foobar2000, as demonstrated above, a codec profile and tool variable.
