Skip to main content
J
Jonas5E41
Participant
August 6, 2021
Answered

DeClipper erkennt geclippte stellen nicht - audio "retten"

  • August 6, 2021
  • 1 reply
  • 745 views

Hallo,

ich habe zusammen mit Freunden bei einem Casting Filmaufnahmen gemacht. Leider ist uns hierbei ein kleiner Fehler unterlaufen und wir haben die Kamera auf Mic und nicht auf Line für den Toneingang gestellt.

Der Fehler ist uns allerdings erst am Abend aufgefallen und wir können die Aufnahen nicht wiederholen.

 

Jetzt zu meinem eigentlichen Problem. Wenn ich die Audiodatei in Audition öffne und den DeClipper nach geclippten stellen suchen lasse, dann findet dieser keine geclippten stellen, obwohl man das Clipping deutlich hört.

 

Hat vielleicht jemand eine Idee wie ich die Audio möglichst gut retten kann? Mir ist bewusst, dass die Audio niemals mehr perfekt werden kann es geht auch nur darum noch das bestmöglichste rauszuholen.

 

Ich habe mal einen Ausschnitt unten beigefügt (Minute 1-2) und einen Screenshot aus Auditon.

 

Vielen Dank für eure Hilfe schoneinmal im Vorraus

 

Grüße

Jonas

This topic has been closed for replies.
Correct answer SteveG_AudioMasters_

I'm sorry, but I don't think that you will really be able to do anything to rescue this. Distortion is the one thing that nobody will ever be able to fix, as there's no original undistorted reference point to clean it up from. Obviously if there was, you wouldn't have a problem! But your sample has gone well beyond clipping, I'm afraid - that's a complete overload. The reason that the declipper won't find any clipped samples is because your waveform doesn't reach 0dB - but if you amplified it so that it did, it would report every single peak as a clip, and if you attempted to 'fix' that, it would inevitably make everything even worse, not better. The de-clipper only really works on short clipped samples, and only then if the clip isn't excessive - it needs to calculate the slope of the waveform either side of the clip and extrapolate where it should have gone to. With massively overloaded audio there really isn't enough reliable information to go on, so it guesses - and makes even louder mistakes as a consequence.

1 reply

SteveG_AudioMasters_
Community Expert
SteveG_AudioMasters_Community ExpertCorrect answer
Community Expert
August 6, 2021

I'm sorry, but I don't think that you will really be able to do anything to rescue this. Distortion is the one thing that nobody will ever be able to fix, as there's no original undistorted reference point to clean it up from. Obviously if there was, you wouldn't have a problem! But your sample has gone well beyond clipping, I'm afraid - that's a complete overload. The reason that the declipper won't find any clipped samples is because your waveform doesn't reach 0dB - but if you amplified it so that it did, it would report every single peak as a clip, and if you attempted to 'fix' that, it would inevitably make everything even worse, not better. The de-clipper only really works on short clipped samples, and only then if the clip isn't excessive - it needs to calculate the slope of the waveform either side of the clip and extrapolate where it should have gone to. With massively overloaded audio there really isn't enough reliable information to go on, so it guesses - and makes even louder mistakes as a consequence.

    J
    Jonas5E41Author
    Participant
    August 15, 2021

    Thanks for your quick response. 

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