Printable View
Well, if this doesn't limit the playing field of thread participants I don't know what will. I was almost with you until it drifted into command line tools, syntax, and compiled binaries, at which point it made Adobe Audition seem like child’s play. Yep, its over my head but I admire those willing to work at this level.
I measured the file:Quote:
Originally Posted by Donovan
Peak Amplitude: +0.27 dBFS (Clipped)
True Peak: +1.02 dBTP
Total Intersample Peaks: 144
Program Loudness: -17.4 LUFS (Mono)
* * *
I'm not sure what tools you have access to. Fill me in and I'll make some suggestions. As far as the Program Loudness, it's slightly hotter than what's slowly becoming the recommended standard. But that's ok. As long as you produce consistent results on a show to show basis, we'll save that discussion. There are variables, mainly the differences in how to handle processing Mono files vs. Stereo. And there are various aspects of "Loudness Normalization" that we can discuss. Note that it's not the same as Peak Normalization or RMS Normalization.
Like I said we can get into this after we solve the clipped audio issue ...
Keep me posted.
In any case I know this stuff may be a bit complex. However - if you (not you personally Donovan :) ) want to learn how to get it done right, there's no way around the complexities. Otherwise the space will continue to be occupied by people giving bad advice and "students" not realizing that they are being misinformed.
-paul.
Thanks, Paul! I have Adobe Audition, ffmeg, etc. If I don't have a program I need, I can possibly get my hands on it.Quote:
Originally Posted by ptfigg
Can you share the command line parameters you're using to measure these stats?
Thanks.
I scanned my processed .wav file from last night's episode in Audition. This is what it told me -
https://s3.amazonaws.com/amn_shows/m...Statistics.PNG
You're very welcome and I'm happy to help.Quote:
Originally Posted by Donovan
For the comprehensive SoX analysis:
At the prompt:
sox --show-progress Your_Input_File.wav -n stats
For Loudness Specification Analysis using FFmpeg:
At the prompt:
ffmpeg -nostats -i Your_Input_File.wav -filter_complex ebur128=peak=true -f null –
You should be good to go in Audition by accessing Amplitude Statistics and running "Scan."
If you are interested in learning how to use a Loudness Meter, we can open a discussion. Keep in mind if you are running an up to date version of Audition, a scaled down version of TC Electronic Loudness Meter is bundled:
Effects/Special/Loudness Radar Meter
There are many other meters. I own most of them and I'm happy to offer anyone assistance.
"afclip" is part of the "Mastered for iTunes" toolkit, and only available for Mac.
Again, keep us posted ...
-paul.
It looks like you're running an older version of Audition that lacks True Peak analysis and Loudness stats ...Quote:
Originally Posted by Donovan
Here's what I get in Audition CC:
Attachment 278
-paul.
Yeah, I'm still using 5.5. Adobe gave me a year of everything when an article was written on me and my process using their software, but after the year was up, I couldn't justify the $50 per month. I realize that Audition is just $19.95 per month, but I haven't felt the need to upgrade. Maybe it's time. I like statistics. :)Quote:
Originally Posted by ptfigg
Great conversation guys and I'm on-board. However, it would be helpful if you actually pointed out who you were referring to if you are going to call out others. At a very minimum it would be respectful to exclude people you are not talking about. Painting a broad stoke over "consultant" is damaging to those of us who are perceived as consultants whether we actually promote ourselves that way or not.
In my case, I'm working hard to help podcasters understand the issue and process of Loudness Normalization. If I'm doing something wrong in your opinion it would be very helpful to know that. I am aware of who this thread is mostly calling out but there are some very broad statements in here that don't let anyone else know who is or isn't giving out "bad" information.
Again, all this info is very helpful and I'm excited to help those podcasters who care enough about their production values understand what loudness is about and how it works.
Hey Ray! Love the service you provide for the Podcasting industry! You are one of the good ones for sure!Quote:
Originally Posted by rayortega
I personally would not want to call anyone out by name. The bad is out there and most people know who they are.
Welcome to the site Rey,
I didn't read this thread as calling out anyone in particular. While there is a real problem with people who call themselves podcasting "consultants", they're not all bad. It's the 98% that give the other 2% a bad rap. But that's another thread lol
