# Mp3tag Make "nfo" files

**URL:** https://community.mp3tag.de/t/mp3tag-make-nfo-files/2244
**Category:** General Discussion
**Created:** [August 29, 2005, 3:26am UTC](https://community.mp3tag.de/t/mp3tag-make-nfo-files/2244 "2005-08-29T03:26:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Altobere](https://community.mp3tag.de/user_avatar/community.mp3tag.de/altobere/32/84_2.png) [@Altobere](https://community.mp3tag.de/u/Altobere)
#### Post date: [August 29, 2005, 3:26am UTC](https://community.mp3tag.de/t/mp3tag-make-nfo-files/2244/1 "2005-08-29T03:26:22Z")

</div>

Hello Florian:  
I read your comments in [/t/968/1](https://community.mp3tag.de/t/968/1) about the **Features which are not planned**.  
I understand it. 🙂  
But, I was thinking that Mp3tag is an excellent way to create the famous "nfo files", very common in the "Newsgroups".  
In the Newsgroup where I is, all work with mp3tag.  
But, we cannot create the "nfo" files, why mp3tag don't have **Encoder Detection**.  
Is very hard to incorporate to mp3tag this feature ?  
I'm sure, that with this feature, mp3tag win many users more.  
Thanks by reading my idea, and maybe can think about her.  
Sorry for my english.  
Thanks! 🙂

---

<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: [August 29, 2005, 5:55am UTC](https://community.mp3tag.de/t/mp3tag-make-nfo-files/2244/2 "2005-08-29T05:55:52Z")

</div>

Accurately detecting an MP3 encoder is very hard. Not even programs which are specialized for this task (EncSpot, MrQuestionMan, etc.) are accurate.

Not only it would take a considerable time to implement near-accurate detection capabilities, but MP3Tag would also spend much more time reading and parsing the MP3 frames

The only thing which _might_ be easy to do would be detecting the LAME version which is stored in the LAME header. It could then display something like "Encoder: LAME 1.23" or "Encoder: GOGO 1.23" and "Encoder: Non-LAME / Non-GOGO".

---

<div class="post-metadata">

### Author: ![Altobere](https://community.mp3tag.de/user_avatar/community.mp3tag.de/altobere/32/84_2.png) [@Altobere](https://community.mp3tag.de/u/Altobere)
#### Post date: [August 30, 2005, 2:23am UTC](https://community.mp3tag.de/t/mp3tag-make-nfo-files/2244/3 "2005-08-30T02:23:59Z")

</div>

Understand.  
Thanks for answer my idea.

---

<div class="post-metadata">

### Author: ![Nighted](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/n/ce73a5/32.png) [@Nighted](https://community.mp3tag.de/u/Nighted)
#### Post date: [September 5, 2005, 9:00am UTC](https://community.mp3tag.de/t/mp3tag-make-nfo-files/2244/4 "2005-09-05T09:00:39Z")

</div>

There's already a program that does this. It's called NFO Sighting.

Google it.