6 Dec
2007
6 Dec
'07
1:34 p.m.
I've this WAV file that contains an interview. It was recorded with a
cell phone, so the quality is not that great, plus the phone got bumped
a few times resulting in annoying peaks.
I was thinking to load the file in Audacity and run it through a
compressor and tweak the settings until it sounds acceptable. But before
I do that, does anyone have a better idea?
What's your usual way to deal with this kind of records?
Thanks,
--
Florin Andrei
http://florin.myip.org/
6 Dec
6 Dec
1:44 p.m.
On Thu, Dec 06, 2007 at 09:34:40AM -0800, Florin Andrei wrote:
I've this WAV file that contains an interview. It
was recorded with a
cell phone, so the quality is not that great, plus the phone got bumped
a few times resulting in annoying peaks.
I was thinking to load the file in Audacity and run it through a
compressor and tweak the settings until it sounds acceptable. But before
I do that, does anyone have a better idea?
What's your usual way to deal with this kind of records?
Difficult to say without hearing / seeing the actual recording.
If the 'peaks' are short you could have a good result by just
editing them out (with a xfade between the remaining parts).
--
FA
Laboratorio di Acustica ed Elettroacustica
Parma, Italia
Lascia la spina, cogli la rosa.
1:49 p.m.
On 6 December 2007 at 9:34, Florin Andrei <florin(a)andrei.myip.org> wrote:
I've this WAV file that contains an interview. It
was recorded with a
cell phone, so the quality is not that great, plus the phone got bumped
a few times resulting in annoying peaks.
I was thinking to load the file in Audacity and run it through a
compressor and tweak the settings until it sounds acceptable. But before
I do that, does anyone have a better idea?
What's your usual way to deal with this kind of records?
I agree with Fons about editing out the peaks, as possible. Make
sure your start/end cut points are at zero crossings and the
crossfade will be smooth.
If the big peak contains sounds you need to keep, then you can
select the offending section, again with start/end at zero
crossings, and just reduce the gain of that section.
Usually I attend to the very worst abnormalities individually.
After that I apply a fast look ahead limiter to deal with the
remaining peaks, if needed. Following that I might compress the
track, if needed, or I might try to level the volume, if needed.
I use Audacity for all of this.
Good luck....
--
Kevin
2:41 p.m.
On Thursday 06 December 2007 10:49:27 Kevin Cosgrove wrote:
On 6 December 2007 at 9:34, Florin Andrei
<florin(a)andrei.myip.org> wrote:
----------------------> question for Kevin:
Could you clarify the "zero crossings". And what does one do to know where
that point is? Zoom function?
Thanks
Tom
I've this WAV file that contains an
interview. It was recorded with a
cell phone, so the quality is not that great, plus the phone got bumped
a few times resulting in annoying peaks.
I was thinking to load the file in Audacity and run it through a
compressor and tweak the settings until it sounds acceptable. But before
I do that, does anyone have a better idea?
What's your usual way to deal with this kind of records?
I agree with Fons about editing out the peaks, as possible. Make
sure your start/end cut points are at zero crossings and the
crossfade will be smooth. If the big peak contains sounds you need to keep, then
you can
select the offending section, again with start/end at zero
crossings, and just reduce the gain of that section.
Usually I attend to the very worst abnormalities individually.
After that I apply a fast look ahead limiter to deal with the
remaining peaks, if needed. Following that I might compress the
track, if needed, or I might try to level the volume, if needed.
I use Audacity for all of this.
Kevin
2:50 p.m.
On 6 December 2007 at 11:41, thomas fisher <studio1(a)commspeed.net> wrote:
----------------------> question for Kevin:
Could you clarify the "zero crossings". And what does one do
to know where that point is? Zoom function?
Yes, zoom in as far as you can and you will see the audio signal
waveform as a squiggly line. At some points in time it will
cross through the straight horizontal line that runs through it;
this line is the zero (no signal) line. The points where the
audio signal crosses the zero line are the zero crossings. If
you do your edits where the start and ends of the edited region
are both on zero crossings, then the changes being made will have
minimum disturbances, and it's possible to make the transitions
into and out of the edited regions undetectable. This isn't
guaranteed, and depends on the kind and degree of editing being
done. Choosing region boundaries at zero crossings is just one
of those "best practices" kind of things. It really makes my own
editing results quite a bit better than if I'd ignored the issue.
I hope that helps....
--
Kevin
6:50 p.m.
Hallo,
Kevin Cosgrove hat gesagt: // Kevin Cosgrove wrote:
Usually I attend to the very worst abnormalities
individually.
After that I apply a fast look ahead limiter to deal with the
remaining peaks, if needed. Following that I might compress the
track, if needed, or I might try to level the volume, if needed.
I use Audacity for all of this.
I use Ardour for it and when I was doing it for the first time, I
discovered the difference between "Slide edit" and "Splice edit". For
cleaning up interviews you generally want "Splice edit" mode, which
will move regions after the cut automatically to fit with the regions
before that. (Audacity doesn't know any other mode.)
If you don't want to do cuts, Ardour's level curves etc. are a big
help as well. Which to choose of course depends on the material.
Ciao
--
Frank Barknecht _ ______footils.org__
6199
days inactive
6199
days old
linux-audio-user@lists.linuxaudio.org
5 comments
5 participants
participants (5)
-
Florin Andrei -
Fons Adriaensen -
Frank Barknecht -
Kevin Cosgrove -
thomas fisher