Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Why is my audio distorted at -3 dbs?

Explorer ,
Sep 26, 2019 Sep 26, 2019

I'm editing dialogue in Audition and hearing distortion at some parts, even though it's peaking around only -3.

 

My client had the remote recording done at a studio. The studio sent us a file that had an ITU loudness of -16, a total RMS of -20.00 db and a true peak of +0.77 db. The even numbers makes me think the studio normalized it before sending it to us.

 

I normalized it again so that it has a total loudness of -16 and a true peak of -1 db. I also did two passes of DeClipper, both times helping to smooth out a few problem spots, but there are still others that are pretty ugly. 

 

Adobe Audition build 12.1.3.0 

Intel i5-4200U @ 1.6 Gh 2.30 Ghz

8 GB RAM

Win 10 Version 1809

OS build 17763.737

324
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Sep 27, 2019 Sep 27, 2019

I think your client should ask the studio where this was recorded to provide unprocessed files. If they've provided pre-processed ones, then by the time they've been edited there's a good chance that the numbers will be 'inappropriate' in any case.

 

The thing about normalizing is that all it does is set the peak value of a file to a number you've specified. If you have specified that the absolute peak value in Audition is -1dB and a file distorts, then it must have been distorted in the first place, as that's under 0dB.

 

The normal way that this stuff happens (indeed has to happen if the results are to be valid) is that no overall level and compression should be done until you have the edit completed. Only at this point can you sensibly set it to the target values and have a consistent result throughout. Now, you may well know all this already - but if this has been pre-processed, then the studio doing it clearly doesn't. And now you have a bit of ammunition...!

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 02, 2019 Oct 02, 2019
The studio apologized and offered a partial refund. Apparently the pre-amps were too hot? I don't even know. If they're monitoring before pre-amps (the only way I can imagine they didn't catch this crunchy distortion) then not sure what they're doing at all.
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
Oct 03, 2019 Oct 03, 2019
If it's all useless (which it sounds as though it might be) then go for a full refund, or a free re-record. Why should you or your client pay for anything at all that's useless?
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Explorer ,
Oct 03, 2019 Oct 03, 2019
LATEST
It was usable, just problematic. But you're right: I don't charge clients for work that ends up being half-good due to my own error. That said, it was a client of my client. So not my decision!
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines