Skip to main content
RenTenTen
RenTenTen
Participating Frequently
June 9, 2017
Answered

Hard Limiter creating unwanted silence and fade-ins during Batch Process

  • June 9, 2017
  • 1 reply
  • 1029 views

Hello everyone,

I have been using Audition two years back to work on Voice Overs, for example for making multiple files louder with Batch Process.

So was I doing today for another project, with the following settings:


Most files (around 50) worked fine, but some in particular were suddenly silent.
I processed the same files without batch processing, just a single Hard Limiter, and there they were correctly 2dB louder, not completely silent.

Also, some files showed long and harsh attacks or fade ins, where actually there was voice before and should still be:
One single file after batch processing hard limiter with above settings:

Before:

So the frequencies in the beginning of the file suddenly disappeared.

Same file with same hard limiter settings, but not in batch processing:


Correctly 2dB louder.

Conclusion:
To me this looks like a bug, but I would not know how to work around this, as it is very much effort to check each file after batch processing, if the bug hopefully did not appear and make the beginning of the file or even the whole file silent.

Has anyone of you experienced the same issue with Hard Limiter in Batch Processing or has an idea how to fix or work around this?
Fast help is very much appreciated, as a deadline in the project is coming up.

Kind regards,
Philipp

This topic has been closed for replies.
Correct answer stefan_gru

Thanks for your reply.

Unfortunately right now I am the only one in the team working with Audition, so I don't have another machine to test on.

I noticed however, that my issue also concerns the Match Loudness function, this time tested with different files on the same machine.
Probably every batch export I will make will show the same results.


Log it as a bug: Feature Request/Bug Report Form

1 reply

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
June 9, 2017

RenTenTen  wrote

Conclusion:
To me this looks like a bug, but I would not know how to work around this, as it is very much effort to check each file after batch processing, if the bug hopefully did not appear and make the beginning of the file or even the whole file silent.

I have a question. If you run the same batch twice, do you get the same problem in the same place? I'm not saying that it isn't a bug, but if it is, it won't be fixable until there are reproducible steps, and the same thing happening in the same place would be a good starting point for that, if you see what I mean...

RenTenTen
RenTenTenAuthor
Participating Frequently
June 9, 2017

Good point.

I made 5 test runs of the same 48 files.
First run had 4 files affected with the problem written in my first post.

Second run it was 8, of which 1 was the same file than in the first run.
Third run it was 9 files affected, fourth run 10, fifth run 9 again.

For the last three runs (number 3, 4 and 5) I did not check again if files were affected, which had been affected before. I assume however that this is just by chance.

After that I tried the same thing with 29 different files.
First run had 5 files affected, Second run 6 and third run 7.

All in all, I have this problem every time now when I batch process export with hard limiter.

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community Expert
Community Expert
June 9, 2017

I think at this point it's worth getting somebody else to try the same thing (or similar). If it's reproducible, then it's worth proceeding with it as a bug. But...

Do you by any chance have another machine you can test this on to see if you get the same result with the same files?

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices