|
|
|
12-19-2013, 10:00 AM
|
#81
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
While we wait for such functions to make it in to Reaper, here's the commandline tool I use from inside Reaper for measuring the loudness of an audio file:
https://dl.dropboxusercontent.com/u/...Batchfiles.zip
4.2 MB ZIP file, containing a Windows compile of Libebur128 commandline scanner that accepts almost any audio file you throw at it, including Flac and Wavpack.
The included batchfiles need to be edited for the path that accesses the commandline scanner. Then simply copy those batch files to your desktop if you like to drag'n'drop things as well. Just point to the batch file as an external editor and bind a shortcut to calling it with the selected item.
Instant loudness scanner report for any item in the session. Be aware that the commandline scanner will scan the complete source file.
An example output of the first batch file: -11.0 LUFS, LRA: 4.2 LU, true peak: -0.0 dBTP, O:\Music\Artists\Foo Fighters\The Colour And The Shape\12 Walking After You.flac
--------------------------------------------------------------------------------
-11.0 LUFS, LRA: 4.2 LU, true peak: -0.0 dBTP
An example output for the same file of the second batchfile, which outputs one short-term LUFS value for every one second of the input file:
-71.722174
-56.136062
-45.747217
-38.939586
-33.161381
-28.480704
-26.355175
-19.519088
-16.398726
-14.781386
-13.941349
-13.843931
-13.567894
-13.635767
-13.233924
-12.763224
-12.374143
-12.276689
-11.795848
-11.420928
-11.375100
-11.912118
-12.434327
-12.666390
-12.841908
-13.584219
-14.267049
-14.523090
-14.128098
-13.500027
-13.101151
-12.911705
-13.039845
-12.623121
-12.449279
-12.309577
-12.761239
-13.010826
-13.181515
-13.645444
-13.017868
-12.636479
-12.117614
-12.706861
-13.005634
-13.062361
-12.802032
-13.114542
-13.197083
-12.941920
-12.507913
-12.923591
-13.820242
-14.548925
-13.446276
-12.619393
-12.173555
-12.391398
-12.472334
-12.368895
-12.322363
-12.197626
-11.796390
-11.048082
-10.635746
-10.755152
-10.719618
-10.837749
-10.610324
-10.427020
-10.935250
-11.157469
-11.812261
-11.085651
-10.955085
-11.352365
-12.036500
-12.236641
-12.058595
-11.767200
-11.007579
-10.752413
-10.542368
-10.750635
-11.193271
-11.093873
-11.275651
-10.631905
-10.716222
-10.848652
-11.015322
-10.896874
-11.009008
-11.590644
-12.476820
-13.037433
-13.433072
-13.774546
-13.897924
-14.039890
-13.954944
-14.264741
-13.836052
-13.348303
-12.931164
-12.864489
-12.785768
-12.405890
-12.350526
-12.642577
-13.094188
-12.895901
-12.818396
-13.088155
-12.803873
-12.102168
-11.784479
-11.889465
-12.297334
-12.196033
-12.689752
-13.288136
-13.498276
-13.295194
-12.591783
-12.894739
-12.899263
-13.540315
-12.903315
-12.337519
-12.107786
-11.913557
-12.053556
-11.487149
-11.906973
-11.777666
-11.436473
-10.725677
-10.681703
-10.714031
-10.666724
-10.442490
-10.401369
-10.823956
-10.822638
-11.215990
-10.793350
-10.906385
-10.780850
-11.142166
-11.333800
-11.801191
-11.532301
-11.206301
-10.923183
-10.670483
-10.796963
-11.104998
-11.172373
-11.081629
-10.258369
-10.126204
-10.337170
-10.679832
-10.365657
-10.199091
-10.416851
-11.521720
-11.523811
-11.010575
-10.337329
-10.436635
-10.466393
-10.521084
-10.185935
-10.330061
-10.883313
-11.189068
-10.461546
-9.881678
-9.755471
-10.139155
-10.200931
-10.355076
-10.541234
-10.927255
-10.522153
-10.508425
-10.127485
-10.279969
-10.428367
-10.899996
-11.235546
-11.405112
-11.564038
-11.495844
-11.254420
-10.398724
-10.132240
-10.200413
-10.172577
-10.193829
-10.231135
-10.339240
-9.889165
-9.501205
-9.386253
-9.425139
-9.541529
-9.865755
-10.439286
-10.423002
-10.133835
-10.062933
-9.990717
-9.655057
-9.299624
-9.070800
-9.617181
-9.625997
-9.606131
-9.251909
-9.206900
-9.438345
-9.777124
-10.260656
-10.938636
-10.977176
-10.088953
-9.606978
-9.124183
-9.614304
-9.580134
-9.640638
-9.443807
-9.215667
-9.597922
-9.879857
-10.197514
-10.241467
-10.127300
-9.577417
-9.405089
-8.990478
-9.346775
-9.258930
-9.299012
-9.096883
-8.925690
-9.017288
-9.331001
-9.371192
-9.487474
-9.443050
-9.543587
-9.961879
-9.560059
-9.330597
-9.155713
-9.099272
-9.121012
-8.984282
-9.288953
-9.751941
-9.955945
-9.990422
-9.871253
-9.766373
-9.975119
-9.517947
-9.786911
-9.812513
-10.515429
-10.205830
-9.554891
-9.231090
-9.295165
-9.981727
-10.258617
-10.906195
-12.010597
-14.435467
-17.373280
-20.354216
-24.222297
-28.855445
-33.908733
-41.881186
-47.399119
-50.782257
-43.791804
-43.790285
-43.791009
-50.091333
-51.113172
-51.219279
-54.273732
-53.994061
-54.552375
-55.027998
-55.020273
-52.808576
-52.391642
Last edited by airon; 12-27-2013 at 02:15 AM.
|
|
|
12-22-2013, 08:07 AM
|
#82
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
Reaper 5 needs this
This is the one from Nuendo.. Justin and Scwha could easily add this I reckon! I have faith in them!
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
12-24-2013, 08:28 PM
|
#83
|
Human being with feelings
Join Date: Jul 2008
Location: Athens / Greece
Posts: 625
|
Wow Airon, thanks! This is very helpful :-)
|
|
|
12-28-2013, 12:52 AM
|
#84
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Quote:
Originally Posted by musicbynumbers
Reaper 5 needs this
This is the one from Nuendo.. Justin and Scwha could easily add this I reckon! I have faith in them!
|
It looks a little like the Nuendo folks may have copied the idea from the FR, but I don't think that's the case.
Plenty of engineers were asking for a timecode locked loudness history before that. In fact, a guy from RTW made a presentation here in Berlin about loudness metering, pimping their produces along the way of course, and mentioned that it was the most-requested feature.
Reaper however is not in the habit of doing anything but one type of track, which is why a dockable, arrangement-view-syncable view is proposed in the feature request.
Along with that the loudness scanning functions of source files could actually be implemented at the time the peak-files are generated.
We're talking 400ms RMS with two bands of filtering, which could easily be bolted to the end of the actual peak file for easy reference, so trimmed items could still easily have their loudness measurement calculated from the data. I am assuming of course that with a 75% overlap, the RMS scan only needs to produce data every 100 ms, so one float for eash of that and it's just 40 bytes per second of audio.
The game audio folks certainly should be clawing for this. Loudness-normalizing dialogue would give you an excellent starting point to work from.
|
|
|
12-30-2013, 10:53 AM
|
#85
|
Human being with feelings
Join Date: Jul 2008
Location: Athens / Greece
Posts: 625
|
Quote:
Originally Posted by airon
The game audio folks certainly should be clawing for this. Loudness-normalizing dialogue would give you an excellent starting point to work from.
|
You are spot-on here Airon, game audio would be far easier especially with the way many designers work these days, producing content and either getting it to the developers or selling it online as stock content.
Dialogue, effects and ambiance would work great directly from render.
If this feature is developed I also have a recommendation to propose, regarding a different method of measuring data that seems to fit even better on the modern game audio design practices many people use and allows for fr better loudness control specific in sound with tiny duration like the ones used in many mobile games and apps.
Oh, and I believe the dock-able and sync-able view of the curve and also the exporting of the measurement data or even the statistics of many files would be great for control after the production and before implementation.
|
|
|
12-30-2013, 11:10 AM
|
#86
|
Human being with feelings
Join Date: Jun 2009
Posts: 2,763
|
Still hoping for something to come of this without workarounds. Great job to all involved in defining the requirements.
|
|
|
02-10-2014, 12:41 AM
|
#87
|
Human being with feelings
Join Date: Jan 2013
Posts: 2
|
Another vote for LUFS.
Dave.
|
|
|
03-26-2014, 06:49 AM
|
#88
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Ok, looks like we're getting some loudness normalization functions via the SWS extension. Breeder is hammering that stuff out right now and first beta tests have been positive.
In the first release it, at a minimum it looks like we're getting normalization actions based on EBU R128 recommendations. That's ITU-R.BS 1770 loudness measurement with a -10 gate. The test files all check out so far, apart from a slight departure in the LRA measurement for one file, but that's fixable if it hasn't been already.
Breeder's still hashing out details and adding/changing things but it hopefully won't be long.
|
|
|
03-26-2014, 02:05 PM
|
#89
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
Indeed guys.. Its going to be awesome!
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
04-03-2014, 03:22 AM
|
#90
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Functions to scan items and tracks for loudness values, and normalize to -23 LUFS or a value of your choice, are now available in the latest beta, v2.4.0 #5.
The functions were implemented by Breeder with the library libebur128. The beta version is available at http://www.standingwaterstudios.com/reaper
To quote from the changelog:
Analyze and normalize loudness
Functionality in general:- Loudness is measured according to EBU 3342 standard thanks to excellent libebur128 by Jan Kokemuller
- Due to limitations in Reaper API, we can extract audio data only from certain parts of the audio chain. Chart can be found here. A few gotchas:
- You can't use item fades for extensive volume control
- If you need to use FX, current workaround is to put one item with needed FX in an empty track and measure that track
Added actions:- SWS/BR: Normalize loudness of selected items/tracks...
- SWS/BR: Normalized loudness of selected items/tracks to -23 LUFS
- SWS/BR: Analyze loudness...
Analyze loudness dialog:- Accessible from the Action list or Main menu > Extensions > Loudness...
- Right-click on the dialog or just click "Options" button for various settings
- Measures integrated, range, short-term and momentary loudness of selected items and tracks
- To normalize items or tracks, right-click analyzed targets in the list view - often faster than using separate actions because data for already analyzed targets in the dialog is cached (to prevent needles reanalyzing before normalization if nothing changed)
- Draw momentary and short-term loudness graph to selected envelope. Right-clicking analyzed item should reveal the feature. You can use dummy JS effects from here as a canvas for loudness graphs
- After the target is analyzed, it's possible to position edit cursor over maximum short-term and momentary loudness interval by double-clicking cells holding their measurements. There is also an option to create time selection over that part of the item/track.
- Dialog is designed to follow project state. If you rename or delete analyzed target, the change will get reflected in the dialog. For various settings relating to this, check dialog options
- Analyzing happens in a separate thread so user is free to keep on using Reaper while it's happening.
|
|
|
04-04-2014, 05:03 AM
|
#91
|
Human being with feelings
Join Date: Jun 2009
Location: South, UK
Posts: 14,214
|
Quote:
Originally Posted by ned
What programs are there that have a loudness normalization function at the moment? (...automated like peak normalization.)
|
Apart from the Beta version of the SWS extension you mean?
http://sws.mj-s.com/index.php
It's just come out and it's some great work done by "Breeder". Does what you need but if it doesn't, let the SWS guys know
__________________
subproject FRs click here
note: don't search for my pseudonym on the web. The "musicbynumbers" you find is not me or the name I use for my own music.
|
|
|
06-17-2014, 10:09 PM
|
#92
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
Added a small list of tools that help out the Loudness Normalization-seeking user to the main request.
While we wait patiently for Cockos to implement this, there are several free or inexpensive measurement plugins you can use to at least get basic measurements done and some analysis.
None of these tools have all this request asks for.
|
|
|
06-19-2014, 03:20 AM
|
#93
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
|
|
|
09-01-2014, 12:00 AM
|
#94
|
Human being with feelings
Join Date: May 2010
Location: Norway
Posts: 7,318
|
Any LUFS metering in Reaper yet?
Or should I just insert a vst LUFS-meter?
__________________
Reaper x64, win 11
Composer, text-writer, producer
Bandcamp
|
|
|
06-05-2015, 01:40 PM
|
#96
|
Human being with feelings
Join Date: Jun 2012
Location: Spain
Posts: 7,239
|
Hello
I've created this REAPER 5 script
HeDa Loudness Graph
Right now it is in pre-release stage.
It uses dpMeter v1.1 by TBProAudio
more info here http://forum.cockos.com/showthread.php?t=159603
|
|
|
06-06-2015, 08:04 AM
|
#97
|
Human being with feelings
Join Date: Aug 2006
Location: Berlin
Posts: 11,817
|
That is very promising indeed.
|
|
|
06-07-2015, 10:44 AM
|
#98
|
Human being with feelings
Join Date: Jun 2012
Location: Spain
Posts: 7,239
|
Quote:
Originally Posted by airon
That is very promising indeed.
|
Thank you airon
It covers your feature request in your signature, with the added feature of being able to compare multiple sources at the same time if needed.
There are still some things to do as I mention here
if you have any question or suggestion I will look at it carefully.
|
|
|
08-05-2018, 03:38 AM
|
#99
|
Human being with feelings
Join Date: Dec 2012
Posts: 13,333
|
Maybe it will happen in 2018? I hope it's not really hard to implement.
|
|
|
08-06-2018, 01:26 PM
|
#100
|
Human being with feelings
Join Date: Apr 2018
Posts: 33
|
+1
More LUFS support would be tremendous. Nuendo still has an edge over Reaper in this arena. I suspect that gap will be quickly narrowed.
Nuendo has a "Normalize to Integrated Loudness" function as part of its exporter. Would love to see something similar in Reaper.
|
|
|
05-22-2019, 04:06 AM
|
#101
|
Human being with feelings
Join Date: Mar 2013
Posts: 181
|
+1000000
When will the Reaper finally have LUFS measurements implemented? In 2019, this should be a standard feature ... thanks
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 03:40 AM.
|