Support and General Use > Audio Playback, Database and Playlists
ReplayGain Implementation
saratoga:
--- Quote from: Carson Dyle on December 15, 2010, 12:22:03 AM --- Are you talking about the raw value of the PEAK fields or some computed value?
--- End quote ---
The raw value. The peak is exactly what it sounds like. The amplitude of the largest sample relatively full scale (1.000000). Hence its a little odd of you to ask if the peak information is used to determine the peak.
--- Quote from: Carson Dyle on December 15, 2010, 12:22:03 AM --- The RG track and album PEAK values can't be greater than 1.
--- End quote ---
Looking at my player, something like 80% of the songs on my player have peaks > 1. Pretty much any modern music will come out well over 1 if MP3 compressed because lossy compression is only approximate and need not have anywhere near the same amplitude as the input signal.
Carson Dyle:
--- Quote from: saratoga on December 15, 2010, 12:36:57 AM ---Looking at my player, something like 80% of the songs on my player have peaks > 1. Pretty much any modern music will come out well over 1 if MP3 compressed because lossy compression is only approximate and need not have anywhere near the same amplitude as the input signal.
--- End quote ---
Interesting. I know that 1.0 is the maximum possible value for Flac files, but I'm not sure I understand why being Mp3 encoded makes a difference, or why the peak amplitude would differ significantly.
What software do you use to do the RG analysis and tagging of the Mp3 files?
My Mp3 library is transcoded from my Flac library, to which I've run RG tags using metaflac. I'll have to set up a test and compare the values computed on the Flac files to those computed on the transcoded Mp3 versions.
Buschel:
Following simple example from signal theory: Take a full scale (+/- 1.0) square wave signal and cut the upper frequencies. In effect you will see overshooting/ringing (so-called Gibbs-phenomenon) that has a higher amplitude than full scale.
Just think of a lossy encoder as a tool to remove signal parts and (often) higher frequencies. When decoding/synthesizing the signal again it may have higher peak scale as the original waveform -- the overall scaling keeps the same.
As most current productions use high amplitude combined with dynamic compression (to achieve high volume/loudness), such peaks >1.0 will appear quite regularly when using lossy codecs. Generally speaking each peak>1.0 will result in clipping during playback. To avoid clipping and to keep the overall scaling constant during playback replay gain can scale all samples with 1/peak, if peak is >1.0
Lear:
--- Quote from: Carson Dyle on December 14, 2010, 09:41:00 PM ---Right, I'm aware of the available settings. I was just wondering whether the other RG values are used in the implementation or if they were ignored.
--- End quote ---
REPLAYGAIN_REFERENCE_LOUDNESS is ignored; the others are used. I hadn't heard about REPLAYGAIN_REFERENCE_LOUDNESS before, but according to this post (at Hydrogenaudio, by the author of the ReplayGain standard) it shouldn't be used.
Chronon:
--- Quote from: Buschel on December 15, 2010, 02:12:23 AM ---Following simple example from signal theory: Take a full scale (+/- 1.0) square wave signal and cut the upper frequencies. In effect you will see overshooting/ringing (so-called Gibbs-phenomenon) that has a higher amplitude than full scale.
--- End quote ---
What a concise and clear example. Thank you! :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version