Remove all tags except album art and..., help requested. Options

[DetlevD]

that method also does not seem to remove the replaygain_track_gain im assuming because mp3tag is not designed to modify the headers. ...

Did you really try it out to remove all the Tag Types ID3v1, ID3v2, APE from the music file?
If so, then you will be left alone with the music data only.
You will not see any tag-field data in Mp3tag's dialog "Extended Tags...".

Because replaygain data are never stored in the mp3 header area (I never heard anything about this ...), there will be no extra data anymore in the music file after removing all the entire Tag Types!

Sometimes, when bad things have been going on before to the file, and different Tag Types have been stacked multiple on to each other, then the process of removing the Tag Types has to be applied repeatedly. At end Mp3tag displays an empty field in the list view column "TagRead (TagTypes)".

... although overall the first method posted by JJ Johnson seems to be the most efficient and easiest. thanks for the help everyone i guess ill have to live with the replaygain_track_gain being there for now.

JJ Johnson's proposal from above does not remove the Tag Types, but only the tag-fields.
This might leave a possible bad structured Tag-Type stack as is - and the music file will stay corrupted as is.

DD.20110612.1744.CEST

Edit.
It is not correct, that I never heard about technical data in the mp3 header, read there ...
http://forums.mp3tag.de/index.php?showtopi...ost&p=40405
DD.20110614.1111.CEST

This post has been edited by DetlevD: Jun 14 2011, 10:10

[JJ Johnson]

Because replaygain data are never stored in the mp3 header area (I never heard anything about this ...), there will be no extra data anymore in the music file after removing all the entire Tag Types!

By default LAME (since, I think, version 3.94) always computes track ReplayGain and stores it in the LAME tag that it writes to files. The following LAME switches affect ReplayGain analysis:

--replaygain-fast compute RG fast but slightly inaccurately (default)
--replaygain-accurate compute RG more accurately and find the peak sample
--noreplaygain disable ReplayGain analysis

Mp3tag doesn't read, write, or remove the LAME tag from Mp3 files.

This is the output of lametag.exe on one of my Mp3 files, showing the RG values:

CODE

F:\Mp3\Santana\Milagro>lametag 01 Milagro.mp3
LameTag - Reads the LAME tag from an mp3 file
Copyright (c) 2005 phwip
Release 0.4.1, compiled 2005-09-09

F:\Mp3\Santana\Milagro\01 Milagro.mp3
Tag revision:       0
Encoder string:     LAME
Version string:     3.98r
Quality:            80 (V2 and q0)
Encoding method:    vbr new / vbr mtrh
Lowpass:            18,500Hz
RG track peak:      1.011433
RG track gain:      -3.4dB (determined automatically)
RG album gain:      <not stored>
nspsytune:          yes
nssafejoint:        yes
nogap continued:    no
nogap continuation: no
ATH type:           4
Bitrate:            minimal (-b) bitrate 32
Encoder delay:      576 samples
Padded at end:      840 samples
Noise shaping:      1
Stereo mode:        joint
Unwise settings:    no
Source sample freq: 44.1kHz
MP3Gain change:     <none>
Preset:             V2: preset standard (fast mode)
Surround info:      none
Music length:       11,728,958 bytes
Music CRC:          E881
Actual Music CRC:   E881
Info tag CRC:       7A1D
Actual InfoTag CRC: 7A1D

[DetlevD]

By default LAME (since, I think, version 3.94) always computes track ReplayGain and stores it in the LAME tag that it writes to files. The following LAME switches affect ReplayGain analysis: ...

Hmm, yes, JJ Johnson, you are showing me the content of a LAME tag using the latest lametag.exe.
Oh yes, I was rather blind for a moment, and have simply forgotten the history of the LAME versions in my music collection.
Obviously lametag.exe does not work with "LAME 32bits version 3.98.4".
Lametag simply says: LAME tag not found.

I suspect, that the LAME tag can only be removed by re-compiling the mp3 file with the " --id3v2-only" option.

Edit:
Although using the option " --id3v2-only" the LAME Tag is written too, as reported in my log files:

CODE

LAME 3.98.4 32bits (http://www.mp3dev.org/)
Using polyphase lowpass filter, transition band: 19383 Hz - 19916 Hz
Encoding O:\IMPORT\Juliane Werding\Jenseits Der Nacht\06=Jenseits der Nacht=Juliane Werding=Jenseits Der Nacht=1987=Schlager=920A3B0A.wav
      to O:\IMPORT\Juliane Werding\Jenseits Der Nacht\MP3\06=Jenseits der Nacht=Juliane Werding=Jenseits Der Nacht=1987=Schlager=920A3B0A.mp3
Encoding as 44.1 kHz j-stereo MPEG-1 Layer III VBR(q=0)
Writing LAME Tag...done
ReplayGain: -3.5dB
The waveform does not clip and is less than 0.1dB away from full scale.
Scale: 1.39636836

CODE

LAME 3.98.4 32bits (http://www.mp3dev.org/)
Using polyphase lowpass filter, transition band: 19383 Hz - 19916 Hz
Encoding O:\IMPORT\Bro'Sis\Never Forget (Where You Come From)\14=Let Me Know=Bro'Sis=Never Forget (Where You Come From)=2002=Pop=E50C7C0F.wav
      to O:\IMPORT\Bro'Sis\Never Forget (Where You Come From)\MP3\14=Let Me Know=Bro'Sis=Never Forget (Where You Come From)=2002=Pop=E50C7C0F.mp3
Encoding as 44.1 kHz j-stereo MPEG-1 Layer III VBR(q=0)
Writing LAME Tag...done
ReplayGain: -8.5dB
The waveform does not clip and is at least 0.1dB away from full scale.
Scale: 0.84262666

I must have closer look into my last compile session, I have just detected, that there are files with and without lametag.exe info. For now I suspect, that foobar's "Repair VBR header" changes the header, so that lametag.exe cannot see the LAME tag anymore. ???

DD.20110613.0540.CEST

This post has been edited by DetlevD: Jun 13 2011, 04:40

[JJ Johnson]

Obviously lametag.exe does not work with "LAME 32bits version 3.98.4".
Lametag simply says: LAME tag not found.

That's the version of LAME that I'm currently using, and was used to encode the file shown above. I think the only files that LAME doesn't write a LAME tag to by default are <64kbps CBR encoded files.

I suspect, that the LAME tag can only be removed by re-compiling the mp3 file with the " --id3v2-only" option.

No, these LAME options are used to control it:

-t disable writing LAME Tag
-T enable and force writing LAME Tag

I wouldn't disable it, though. If you don't want RG information computed and stored, use the --noreplaygain option shown in a previous post.

[JJ Johnson]

For now I suspect, that foobar's "Repair VBR header" changes the header, so that lametag.exe cannot see the LAME tag anymore. ???

That sounds feasible. I believe the LAME tag is an evolution of the Xing VBR header.

http://gabriel.mp3-tech.org/mp3infotag.html

[emielll]

Hi guys - this was exactly the funcionality i was looking for.

Just wondering what you should do if you want to keep the tag label aswell.

would it be:

Remove fields except "PICTURE;%label%"

Or something like that?

[dano]

No % signs:

PICTURE;label

[TestTubePuppy]

Hey pyro, this should remove the track volume and album volume tags (it will give you a menu option to do so within Media Monkey):

Save the code below as "Menu_UndoAnalyzeVolume.vbs" using Notepad and make sure the file path matches the one described in the comment header.

As shown, DiddleLeeDoo created this script (not me), but I added the part that removes the album volume.

'-------------------------------------------------------------------
' \Program Files\MediaMonkey\Scripts\Auto\Menu_UndoAnalyzeVolume.vbs
'
' Version: 1.01
' Date: 24 September 2006
' By DiddeLeeDoo
'-------------------------------------------------------------------

Sub OnStartup
Set Mnu=SDB.UI.AddMenuItem(SDB.UI.Menu_Tools,4,2)
Mnu.Caption=SDB.Localize("Undo Analyze Volume")
Mnu.IconIndex=39
Mnu.UseScript=Script.ScriptPath
Mnu.OnClickFunc="UndoVol"
End Sub

Sub UndoVol(o)
If SDB.SelectedSongList.Count>0 Then
Set dbT=SDB.SelectedSongList
Set Prg=SDB.Progress
Prg.MaxValue=dbT.Count-1
Prg.Text=SDB.Localize("Undoing Volume Analyzing...")
For i=0 To dbT.Count-1
Set Sng=dbT.Item(i)
Sng.Leveling=-999999
Sng.LevelingAlbum=-999999
Sng.UpdateDB
Sng.WriteTags
Prg.Value=i
If Prg.Terminate Then Exit For
Next
Set Prg=Nothing
Set dbT=Nothing
Else
SDB.MessageBox SDB.Localize("Please select the tracks to be processed"), mtError, Array(mbOk)
End If
End Sub