How can I use this tool to normalize mpeg-2 and h.264 files?
Quote from: westis on 27 April, 2013, 06:03:49 AMHow can I use this tool to normalize mpeg-2 and h.264 files?You may consider re-wrapping them into a MKV container by choosing the MKV format.
echo offclsecho Script by http://1024.grcd /d %~dp0 echo Extracting audio to "%~1_clean.wav"..r128gain-1.0-beta-2\r128gain-tools\ffmpeg.exe -i "%~1" -ac 2 -y "%~1_clean.wav" echo Getting max amplitude and normalizing to "%~1_clean.wav"..r128gain-1.0-beta-2\r128gain.exe --in-place "%~1_clean.wav" echo Extracting video to "%~1_clean.avi"..r128gain-1.0-beta-2\r128gain-tools\ffmpeg.exe -i "%~1" -map 0:0 -vcodec copy -y "%~1_clean.avi" echo Creating new video file into "%~1_new.avi"..r128gain-1.0-beta-2\r128gain-tools\ffmpeg.exe -i "%~1_clean.avi" -i "%~1_clean.wav" -vcodec copy "%~1_new.avi" :clearecho Cleaning..del "%~1_clean.wav"del "%~1_clean.avi"pause
I tried separating audio and video, to normalize the audio and then merge audio and video together.
But the audio doesn't change.
r128gain "--command=sox %TRACK% %BN%-norm.wav gain %TGDB%" C:\Windows\Media\chord.wav -o .
Crashes on 2 different computers for me after I click OK using default settings, no log files are written.I'm guessing this needs SSE2... both computers I tried are PIII.
Unfortunately, there was a build problem in the 14.4.1 release leading to libflac and libsndfile being left out of the Windows binary.
I noticed that the 14.4.1 windows build of SoX doesn't include FLAC or W64 support.
I did some searching and found this posted on their project forum:QuoteUnfortunately, there was a build problem in the 14.4.1 release leading to libflac and libsndfile being left out of the Windows binary.
I decided to give R128Gain (latest RC2 build) a try last night after reading about it here and hearing good things about it. At first, I couldn't get it to work on my MP3s, but as directed I updated FFmpeg and then it was able to do so. However, the R128Gain-modified MP3s seem to be missing all the ID3 and other metatags. Is there any simple way to tell R128Gain to simply pass through all tags other than the original ReplayGain one?
ffmpeg -i "in.mp3" -c copy -y "out.mp3"
ffmpeg -i "in.mp3"
ffmpeg -i "out.mp3"
They will not be re-encoded.
Sorry, but what do you mean? These algorithms just analyse the entire stream, determine the peak and average perceptual loudness
The two data are stored in separate fields. The player should provide options to (A) normalise average perceptual loudness and also (B) override the adjustment invoked by step A if it would result in clipping according to the specified peak, thus preventing clipping.
as I'm using iTunes and it will rely on a single value.
The two data are stored in separate fields. The player should provide Regarding the maximum (inter-sample) peak: Having applied the gain in order to achieve the loudness as defined by the mentioned standards (-23 dBFS or -24 dBFS, respectively)
On the user interface it is possible to specify an offset value ('ReplayGain Calibration') defaulting to -18. However, after running the loudness scanner it does seem hold on the Reference Loudness (default -23 LUFS), regardless of the calibration value (default -18 LUFS). If I compare a loudness scan on the same file with Foobar2000 (v1.2.9), which uses -18 by default I get a different value.
(1) I'm confused because I can modify both Reference Level AND Calibration value for both options "EBU R128" and "Replaygain"I would have assumed that the replaygain value is calculated as RG = (Reference Value) - (Loudness), with Loudness measured according ITU-1770-2. For EBU-R128 compliance, the reference value is -23 LUFS to offset content for normalized loudness. For use with music files on portable devices, the recommended reference value is -18 dB for normalized loudness (Wolters et al. (2010), page 11). Can you help me out?
$ r128gain --rg2 --overwrite input/Track01.flac -o outputSoX sucessfully loaded.FFmpeg sucessfully loaded.analyzing ... [1/1] "Track01.flac": 96.2 dBFS (-7.2 dB) peak: 0.2 dBFS, range: 3.9 dB [ALBUM]: 96.2 dBFS (-7.2 dB) peak: 0.2 dBFS, range: 3.9 dBwriting ... [1/1] "Track01.flac" ... done.done.
$ r128gain --rg --overwrite input/Track01.flac -o outputSoX sucessfully loaded.FFmpeg sucessfully loaded.ReplayGain sucessfully loaded.analyzing ... [1/1] "Track01.flac": 96.9 dBFS (-7.9 dB) [ALBUM]: 96.9 dBFS (-7.9 dB)writing ... [1/1] "Track01.flac" ... done.done.
(2) How could I afterward inspect the meta-date of a file to see which calibration value was used?
$ r128gain-tools/ffmpeg -i output/Track01.flacffmpeg version 2.0 Copyright (c) 2000-2013 the FFmpeg developers built on Jul 14 2013 13:18:11 with gcc 4.7.3 (rubenvb-4.7.4-release) libavutil 52. 39.100 / 52. 39.100 libavcodec 55. 18.102 / 55. 18.102 libavformat 55. 12.102 / 55. 12.102 libavdevice 55. 3.100 / 55. 3.100 libavfilter 3. 80.101 / 3. 80.101 libswscale 2. 3.100 / 2. 3.100 libswresample 0. 17.102 / 0. 17.102 libpostproc 52. 3.100 / 52. 3.100Input #0, flac, from 'Track01.flac': Metadata: REPLAYGAIN_ALGORITHM: EBU R128 REPLAYGAIN_REFERENCE_LOUDNESS: 89.00 dBFS REPLAYGAIN_TRACK_GAIN: -7.25 dB REPLAYGAIN_TRACK_PEAK: 1.023053 REPLAYGAIN_TRACK_RANGE: 3.94 dB REPLAYGAIN_ALBUM_GAIN: -7.25 dB REPLAYGAIN_ALBUM_PEAK: 1.023053 REPLAYGAIN_ALBUM_RANGE: 3.94 dB ENCODER : Lavf55.12.102 Duration: 00:05:44.49, bitrate: 838 kb/s Stream #0:0: Audio: flac, 44100 Hz, stereo, s16At least one output file must be specified
As far as I can see, you're looking for ITU BS1770 algorithm with metrics taken from RG world. That's what is called RG2 in "r128gain".