Old 08-21-2017, 05:27 PM   #1
cjunekim
Human being with feelings
 
Join Date: Dec 2016
Posts: 255
Default Loudness Meter?

Hi

I've been experimenting with SWS extension's Loudness Analyzer/Normalizer to check LUFS of my tracks. It seemed to be great at first but I am disappointed. It seems to analyze the track's loudness pre-fx. I use compressors and limiters to adjust the level and dynamics but it is not reflected in the Loudness Analyzer's result. What I want is loudness post-fx.

Of course I can render the track and then analyze on it. However, it is unnecessarily slow.

Any ways to analyzing loudness post-fx in Reaper? Do I have to use a third-party plug-ins? Any recommendations? (BTW, my main work with reaper is podcast producing)
cjunekim is offline   Reply With Quote
Old 08-21-2017, 08:57 PM   #2
trevlyns
Human being with feelings
 
trevlyns's Avatar
 
Join Date: Dec 2011
Location: Rhode Island, New England
Posts: 1,665
Default

Sorry, have to state the obvious: is the analyser the last plugin in your train? If it's placed before compressors etc you would get the kind of results you mention.
__________________
Retired Home Music Producer
Sample Projects https://soundcloud.com/trevs_audio
trevlyns is offline   Reply With Quote
Old 08-21-2017, 09:07 PM   #3
cjunekim
Human being with feelings
 
Join Date: Dec 2016
Posts: 255
Default

Quote:
Originally Posted by trevlyns View Post
Sorry, have to state the obvious: is the analyser the last plugin in your train? If it's placed before compressors etc you would get the kind of results you mention.
I mean the Loudness Analyzer/Normalizer in the SWS extension kit. It is not a VST plug-in. You access it from "Extension" menu.
cjunekim is offline   Reply With Quote
Old 08-21-2017, 10:09 PM   #4
bobobo
Human being with feelings
 
bobobo's Avatar
 
Join Date: Oct 2014
Posts: 1,369
Default

you can examine loudness on items or tracks .. set it in the options

(not sure if it works. the results seem to be the same)

maybe it works best on stems

Last edited by bobobo; 08-21-2017 at 10:17 PM.
bobobo is offline   Reply With Quote
Old 08-22-2017, 04:02 AM   #5
nofish
Human being with feelings
 
nofish's Avatar
 
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,110
Default

SWS loudness analysis is offline analysis, meaning it only works with existing files and not realtime FX.


If you want post-fx loudness analysis rather use a plugin, e.g
https://forum.cockos.com/showthread.php?t=140881
nofish is offline   Reply With Quote
Old 08-22-2017, 09:41 AM   #6
heda
Human being with feelings
 
heda's Avatar
 
Join Date: Jun 2012
Location: Spain
Posts: 7,269
Default

Quote:
Originally Posted by cjunekim View Post
Of course I can render the track and then analyze on it. However, it is unnecessarily slow.
It's the opposite. Render is usually faster than real-time.
So render it to a new take or track. And use SWS loudness to analyse it. Overall time will be less than using a plugin and playback in real-time if it is a large item.
heda is offline   Reply With Quote
Old 08-22-2017, 09:56 AM   #7
karbomusic
Human being with feelings
 
karbomusic's Avatar
 
Join Date: May 2009
Posts: 29,269
Default

Quote:
Originally Posted by heda View Post
It's the opposite. Render is usually faster than real-time.
So render it to a new take or track. And use SWS loudness to analyse it. Overall time will be less than using a plugin and playback in real-time if it is a large item.
Correct, and the SWS extension is similar to what one would get with render (minus creating a new file) as it has to analyze/scan the entire item (which is still much faster than allowing the song to play through) meaning.... Real-time LUFs has the disadvantage that you need to allow the song to play from beginning to end, or the readout is useless for long-term/intergrated which is what many need it for.

It's fine to use in real-time for short term etc. but if one wants to meet some LUFS integrated target, it's better to render and use something like Orban Loudness Meter to get a true readout of what the render ends up being. What I do is spot check with something like YouLean loudness meter in real-time (loaded as a monitoring FX) but use Orban when I'm ready to Render in order to meet any "official" target LUFS.
__________________
Music is what feelings sound like.
karbomusic is offline   Reply With Quote
Old 08-22-2017, 10:05 AM   #8
Bri1
Banned
 
Join Date: Dec 2016
Location: England
Posts: 2,432
Default

Quote:
Any recommendations? (BTW, my main work with reaper is podcast producing)
Once you have final render-split into short sections--analyze each section separately--then simply heal the splits (do not move audio if no need to.)
You basically need a fast machine here> my older computer is also very very slow on whole renders.K?
=)
Bri1 is offline   Reply With Quote
Old 08-22-2017, 01:55 PM   #9
skippertag
Human being with feelings
 
Join Date: Jun 2015
Posts: 474
Default

Quote:
Originally Posted by cjunekim View Post
Hi

I've been experimenting with SWS extension's Loudness Analyzer/Normalizer to check LUFS of my tracks. It seemed to be great at first but I am disappointed. It seems to analyze the track's loudness pre-fx. I use compressors and limiters to adjust the level and dynamics but it is not reflected in the Loudness Analyzer's result. What I want is loudness post-fx.

Of course I can render the track and then analyze on it. However, it is unnecessarily slow.

Any ways to analyzing loudness post-fx in Reaper? Do I have to use a third-party plug-ins? Any recommendations? (BTW, my main work with reaper is podcast producing)
Hey!
You may want to try the free but great Youlean Loudness Meter
https://youlean.co/youlean-loudness-meter/
skippertag is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:46 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.