In my mp3s I see an ID3v1 field
"ENCODERSETTINGS"
with the value
"LAME v3.96"
Is it possible to add a user definable ID3 header field? I wish I could add a field like:
"Settings" // "-V 5 -b 112 --athaa-sensitivity 1 --vbr-mtrh"
Full Version: Lame 3.96 - User def. tag field?
There's no ENCODERSETTINGS field defined in ID3v1.
ID3v1 has no support for custom fields, while ID3v2 and APEv2 do.
The LAME header as such a field, indicating the lame version used to create the MP3:
http://gabriel.mp3-tech.org/mp3infotag.html
ID3v1 has no support for custom fields, while ID3v2 and APEv2 do.
The LAME header as such a field, indicating the lame version used to create the MP3:
http://gabriel.mp3-tech.org/mp3infotag.html
I always write the used settings in short form in the comment field presents in ID3v1 tags. that's of course only a good idea if you actually use ID3 tags, and don't have any other use for the comment field...
QUOTE(dev0 @ May 24 2004, 04:09 AM)
There's no ENCODERSETTINGS field in ID3v1 or ID3v2.
ID3v1 and ID3v2 have no support for custom fields; another reason to use APEv2.
ID3v1 and ID3v2 have no support for custom fields; another reason to use APEv2.
Wrong.
ID3v2 has the following standard fields:
TENC = Encoded by
TSSE = Software/Hardware and settings used for encoding
and of course User defined fields
TXXX = User defined text information frame
QUOTE
This frame is intended for one-string text information concerning the audiofile in a similar way to the other "T"-frames. The frame body consists of a description of the string, represented as a terminated string, followed by the actual string. There may be more than one "TXXX" frame in each tag, but only one with the same description.
<Header for 'User defined text information frame', ID: "TXXX">
Text encoding $xx
Description <text string according to encoding> $00 (00)
Value <text string according to encoding>
<Header for 'User defined text information frame', ID: "TXXX">
Text encoding $xx
Description <text string according to encoding> $00 (00)
Value <text string according to encoding>
QUOTE(dev0 @ May 24 2004, 01:09 PM)
There's no ENCODERSETTINGS field in ID3v1 or ID3v2.
You can use the TXXX frame of ID3v2 to create a ENCODERSETTINGS field (so does foo_id3v2 and my tagger).
~ Florian
Edit: Dimitris was faster
I didn't think about TXXX fields. Sorry.
QUOTE(jtclipper @ May 24 2004, 04:22 AM)
ID3v2 has the following standard fields:
TENC = Encoded by
TSSE = Software/Hardware and settings used for encoding
But as far as I can see theres no possibility setting such tags with EAC/lame...
TENC = Encoded by
TSSE = Software/Hardware and settings used for encoding
foo_id3v2 maps TSSE to %ENCODERSETTINGS% and TENC to %ENCODEDBY%.
Mystery solved.
I'm pretty sure that EAC sets at least TENC when using its ID3v2 tagging.
Mystery solved.
I'm pretty sure that EAC sets at least TENC when using its ID3v2 tagging.
QUOTE(dev0 @ May 24 2004, 04:50 AM)
foo_id3v2 maps TSSE to %ENCODERSETTINGS% and TENC to %ENCODEDBY%.
Mystery solved.
Mystery solved.
So AFAICS Lame 3.96 is doing wrong, as it sets TSSE to "Lame 3.96"?
What settings are you using in EAC?
Are you using lame_enc.dll by any chance?
Are you using lame_enc.dll by any chance?
QUOTE(dev0 @ May 24 2004, 04:55 AM)
What settings are you using in EAC?
Are you using lame_enc.dll by any chance?
Are you using lame_enc.dll by any chance?
I'm using lame.exe. I have never used lame_enc.dll.
for my car audio:
-V 5 -b 112 --athaa-sensitivity 1 --vbr-mtrh --id3v1-only --ignore-tag-errors --tc "V5 b112 vbr-mtrh athaa-sens1" --tt "%t" --ta "%a" --tl "%g" --tn "%n" --ty "%y" --tg "%m" %s %d
idv1 cause my car player does only support v1.
And EAC's ID3 tagging is set disabled?
QUOTE(Squeller @ May 24 2004, 02:51 PM)
QUOTE(dev0 @ May 24 2004, 04:50 AM)
foo_id3v2 maps TSSE to %ENCODERSETTINGS% and TENC to %ENCODEDBY%.
Mystery solved.
Mystery solved.
So AFAICS Lame 3.96 is doing wrong, as it sets TSSE to "Lame 3.96"?
Well, depends on how you see it. Encoded by can also be interpreted by the person who encoded the file, not the software which did it.
The ID3v2 committee define TSSE as "Software/Hardware and settings used for encoding", whereas "and settings used for encoding" can be ommited. In that case, LAME is allowed to write "LAME 3.96" inside a TSSE frame, as it is the "Software used for encoding".
QUOTE(dev0 @ May 24 2004, 05:03 AM)
And EAC's ID3 tagging is set disabled?
Yes of course.
Now, I'm puzzled... Guess a LAME dev has to come in and answer. I'd be really worried if LAME added ID3v2 tags when forcing it not to.
QUOTE(dev0 @ May 24 2004, 05:18 AM)
Now, I'm puzzled... Guess a LAME dev has to come in and answer. I'd be really worried if LAME added ID3v2 tags when forcing it not to.
QUOTE
-V 5 -b 112 --athaa-sensitivity 1 --vbr-mtrh --id3v1-only --ignore-tag-errors --tc "V5 b112 vbr-mtrh athaa-sens1" --tt "%t" --ta "%a" --tl "%g" --tn "%n" --ty "%y" --tg "%m" %s %d
The above command line DOES NOT WRITE ID3v2 tags.
He should check again.
LAME works fine period.
Either check EAC or the validity of his statements.
QUOTE(dev0 @ May 24 2004, 05:18 AM)
Now, I'm puzzled... Guess a LAME dev has to come in and answer. I'd be really worried if LAME added ID3v2 tags when forcing it not to.
Ah, this is why you're asking!!! No need for confusion! When I mentioned "So AFAICS Lame 3.96 is doing wrong, as it sets TSSE to 'Lame 3.96'?" I wasn't refering to the command line I mentioned! No need for a lame dev.
No, the question is, if Lame does IDv2, why is TSSE set to "lame v3.96"? Lame should set TENC to "lame v3.96"..
Sorry for the confusion
QUOTE(Squeller @ May 24 2004, 03:33 PM)
No, the question is, if Lame does IDv2, why is TSSE set to "lame v3.96"? Lame should set TENC to "lame v3.96"..
Please read my post above.
Lame devs should add more info IMHO to the Id3v2 frame including all the command line switches.
QUOTE(jtclipper @ May 24 2004, 03:46 PM)
Lame devs should add more info IMHO to the Id3v2 frame including all the command line switches.
True!
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.