also, (again, newbie question) can I pass the full -sox comand line to the program (through windows .bat file or shortcut)? I tried --command=sox "%TRACK%" "%DN%\%BN%.wav" gain "%TGDB%" but all thouse quotes seem to confuse the .bat fileYou should surround it by quotes, i.e. either[blockquote]'--command=sox "%TRACK%" "%DN%\%BN%.wav" gain "%TGDB%"'[/blockquote]or[blockquote]"--command=sox '%TRACK%' '%DN%\%BN%.wav' gain '%TGDB%'"[/blockquote]
Managed to get"C:\Users\Roj\Desktop\r128gain-0.9.6-3\r128gain.exe" --preamp=-1.0 --command="sox %%TRACK%% %%DN%%\%%BN%%-24db.wav gain %%TGDB%%" %1 -o convertedto-24dbworking for files with no spaces in their filenames, but bombs when long filenames are used for example "test file - Copy.wav"Thanks again for any insights - bat files are not my speciality!
Any other suggestions, let me know.
@echo offr128gain --preamp=-1.0 "--command=sox \"%%TRACK%%\" \"%%DN%%\%%BN%%-24db.wav\" gain %%TGDB%%" %1 -o "H:\tmp\Folder with Space in Name\Output Subfolder with Space in Name"
H:\>r "H:\tmp\Folder with Space in Name\Input Subfolder with Space in Name\*"SoX successfully loaded.FFmpeg successfully loaded.analyzing ... 01 Track 1 with Space in Name.flac (1/8): -12.7 LUFS, -11.3 LU (peak: 0.956400: -0.4 dBFS, range: 2.6 LU) 02 Track 2 with Space in Name.flac (2/8): -12.7 LUFS, -11.3 LU (peak: 0.867426: -1.2 dBFS, range: 2.9 LU) 03 Track 3 with Space in Name.flac (3/8): -13.4 LUFS, -10.6 LU (peak: 0.987564: -0.1 dBFS, range: 6.5 LU) 04 Track 4 with Space in Name.flac (4/8): -12.7 LUFS, -11.3 LU (peak: 0.987406: -0.1 dBFS, range: 2.3 LU) 05 Track 5 with Space in Name.flac (5/8): -12.7 LUFS, -11.3 LU (peak: 0.919231: -0.7 dBFS, range: 2.3 LU) 06 Track 6 with Space in Name.flac (6/8): -12.5 LUFS, -11.5 LU (peak: 0.829128: -1.6 dBFS, range: 3.6 LU) 07 Track 7 with Space in Name.flac (7/8): -13.0 LUFS, -11.0 LU (peak: 0.976282: -0.2 dBFS, range: 4.2 LU) 08 Track 8 with Space in Name.flac (8/8): -14.5 LUFS, -9.5 LU (peak: 0.899243: -0.9 dBFS, range: 3.1 LU) ALBUM: -12.9 LUFS, -11.1 LU (peak: 0.987564: -0.1 dBFS, range: 3.8 LU)writing ... 01 Track 1 with Space in Name.flac (1/8) ... done. 02 Track 2 with Space in Name.flac (2/8) ... done. 03 Track 3 with Space in Name.flac (3/8) ... done. 04 Track 4 with Space in Name.flac (4/8) ... done. 05 Track 5 with Space in Name.flac (5/8) ... done. 06 Track 6 with Space in Name.flac (6/8) ... done. 07 Track 7 with Space in Name.flac (7/8) ... done. 08 Track 8 with Space in Name.flac (8/8) ... done.H:\>dir "H:\tmp\Folder with Space in Name\Output Subfolder with Space in Name" Datenträger in Laufwerk H: ist DATA Volumeseriennummer: B4EC-4972 Verzeichnis von H:\tmp\Folder with Space in Name\Output Subfolder with Space in Name31.03.2012 08:52 <DIR> .31.03.2012 08:52 <DIR> ..31.03.2012 08:51 38.984.444 01 Track 1 with Space in Name-24db.wav31.03.2012 08:51 40.007.564 02 Track 2 with Space in Name-24db.wav31.03.2012 08:51 47.204.684 03 Track 3 with Space in Name-24db.wav31.03.2012 08:51 74.810.108 04 Track 4 with Space in Name-24db.wav31.03.2012 08:51 47.282.300 05 Track 5 with Space in Name-24db.wav31.03.2012 08:51 44.563.388 06 Track 6 with Space in Name-24db.wav31.03.2012 08:52 53.362.220 07 Track 7 with Space in Name-24db.wav31.03.2012 08:52 33.897.068 08 Track 8 with Space in Name-24db.wav 8 Datei(en), 380.111.776 Bytes 2 Verzeichnis(se), 206.937.473.024 Bytes freiH:\>_
millions of thanks to Mr. Belkner for his efforts with this project, most appreciated.
would be possible to use BWF (Broadcast Wave Format) Tags alternatively.
I was wondering if it would be possible to use BWF (Broadcast Wave Format) Tags alternatively.
We use BWF (and RF64 for multichannel files >2GB) for all our mpeg1LayerII and linear files, and this tool could be a tremendous help for many applications across a broadcast workflow (analysis/corrected on playout/corrected in the file directly)
PS: a small observation in the dropdown-box for the output metadata format: It should read "BWF" and not "BFW"
OMG Mr. Belkner you are incredible!!!I do not want to think about how long it would have taken a commercial software company to implement BWF loudness Tags, and you are able to pull this off within 24 hours as a "side project"!!! Congratulations and thank you so much!As the chairman from the EBU R128 working group is a good friend and colleague of mine, I will communicate your efforts to this EBU group and additionally to all the public broadcasters in germany which are currently searching for tools to implement R128. I know that you are doing this in your free time and really hope there are some broadcasters placing commercial orders for further adaptions and integrations with you, to give you some kind of compensation for everything you are doing for the R128 loudness standard.Thanks and respect, karl.
I'm interested in trying R128 volume for my lossless collection (ripped CDs, stereo @ 44100 Hz). However, I want to discover the reported "gain" and "range" values for each track, not a copy of the file with some tags applied. So I need some help here. This post is mostly directed to pbelkner and since it was written in a hurry, it's dense and probably incomprehensible; I'll gladly explain everything if asked to....
If you like to embed "lib1770" into a program you should have a look at "example1.c" provided with the source of "lib1770".
Quote from: pbelkner on 02 May, 2012, 12:02:47 PMIf you like to embed "lib1770" into a program you should have a look at "example1.c" provided with the source of "lib1770".Thank you. I did that and had success (I changed RATE to 44100, made buf into static short array multiplying each sample by 1.0/32768.0). However, I obviously get only the suggested gain, not the loudness range. I perused the source of r128gain and found the commented-out BWF_AR defines, but no other mentions. Can I assume that the loudness range functionality is not yet implemented? I'm not pressuring; I'm asking to stop looking for it if it isn't there.Again, thank you very much for both spending time to develop r128gain/lib1770 and answering here to all of us.
If you look at "exampel1.c" you'll find a symbol "LRU" defined:If the symbol is defined, the example program calculates the loudness range in LU.If the symbol is undefined, the example program calculates the (absolute) loudness in LUFS (not a gain).
I create two contexts, one for the loudness range and one for the absolute loudness (each with the suggested values for gate, block and partition) and at the end I report both.
Version 1.0-alpha-1 released:
For the peak finder, the files are additionally resampled to 192 kHz, right?
For the loudness analysis, all input files are resampled to 48 kHz, right?
The way I understand R128 is:Pass 1: analyze entire file/album, compute loudness taking into account the absolute gate of -70 LUFS.Pass 2: analyze entire file/album again, this time also taking into account the relative loudness gate derived from the result of pass 1. Is that how you implemented it?
Calling the new alpha ('r128gain-1.0-alpha-1-win32-native') directly from the commandline gives the Windows error popup:[blockquote]'r128gain.exe hat ein Problem festgestellt und muss beendet werden.' (encountered a problem and has to be closed.)AppName: r128gain.exe AppVer: 0.0.0.0 ModName: msvcrt.dllModVer: 7.0.2600.5512 Offset: 0000ee96[/blockquote]
Is it possible to pipe audio data to r128gain? I checked the commandline switches but couldn't find any hints.
When I pass a file path with spaces and without "enclosing quotes", or a file which doesn't exist, it prints an assert and crashes.