Title says it all really.
I want to display the REPLAYGAIN_TRACK_PEAK in db similar to the REPLAYGAIN_TRACK_GAIN.
The gain automatically shows in db, but not the peak. I have changed Foobar to display both in dB (for no better reason than I prefer it that way) and want the same values displayed in MP3Tag.
Is there a simple solution to convert the display to db?
regards and thanks
BTW great product; I no longer use Zoltam despite having paid for a lifetime license!
I think you are missing the point of my enquiry and that is how to get MP3Tag to calculate and display that calculation.
In Foobar dB is a calculation of the track value as is track peak.
So, as MP3Tag does this calculation for track value automatically how do I go about applying a calculation the track peak value and displaying the result.
I have trawled through the information provided and in the absence of the obvious found a way to edit the displayed field:
Customise Columns | Change Field | Functions
As my first check to see what was going on I used 'right(x,n)' and used the formula right(%ReplayGain_Track_Peak%,2)
This gave me a revised two character field, so good start!
But when I changed the file back to %ReplayGain_Track_Peak% the original gain value is no longer displayed, instead it remains as two characters. I then created a second column with a different name but the same value %ReplayGain_Track_Peak% and I get the same truncated two characters!
Mp3tag does not do this calculation for track value automatically.
Mp3tag may report and display Replay Gain values but it does not analyze audio data to calculate track value or any other value associated with Replay Gain.
Replay Gain is metadata, and Mp3tag can edit it, but that is done by user input and not by analyzing the audio payload.
Even if you knew a formula to make the calculations, it would normally require knowledge of the audio waveform and that is not available via Mp3tag.
There is no log function listed in the standard mathematical calculations, however I believe MP3Tag must use log in order to calculate and display other dB values. It would appear to be an omission that needs adding.