Although that's not the intended use of the click removal effect, I bet you
are right: in some cases, a very, very brief (milliseconds) instance of
clipping might be moderated by applying this effect. But keep in mind that
your suggestion addresses clipping once it has irreversibly occurred; I was
focusing on preventing it in the first place, which I feel is by far the
preferable strategy.
Rich
----- Original Message -----
From: "Billy Geiger" <scalemodeler@...>
To: "Discussion list for Audacity users"
<audacity-users@...>
Sent: Monday, September 25, 2006 1:16 PM
Subject: Re: [Audacity-users] clipping prevention automation
| EFFECT > CLICK REMOVAL?
|
| BG:) (JIF)
|
|
|
| ----- Original Message -----
| From: "David R. Sky" <davidsky@...>
| To: "Discussion list for Audacity users"
<audacity-users@...>
| Sent: Monday, September 25, 2006 3:22 PM
| Subject: Re: [Audacity-users] clipping prevention automation
|
|
| |I agree Rich - I'd rather not need to do tsecond and third and more
steps.
| | Being blind, it's impossible to see when/where a clip specifically
occurs.
| | Although I can think of a Nyquist way to tell me which peak values are
| | where (plus or minus 1.0), I cannot think of a "sound" way to "soften"
| | those clips.
| |
| | David
| |
| |
| |
| | On Mon, 25 Sep 2006, Rich wrote:
| |
| | > I'm not following how your point has anything remotely to do with
mine. Everything you pointed out is 100% true, yet is equally unrelated to
the topic. It's as if one of us wasn't even discussing the same subject.
Anyway, I'm too tired to argue - somebody else wanna jump in on this one and
either excoriate me or exonerate me?
| | >
| | > Rich
| | >
| | > ----- Original Message -----
| | > From: Jimi Photon
| | > To: audacity-users@...
| | > Sent: Monday, September 25, 2006 5:24 AM
| | > Subject: Re: [Audacity-users] clipping prevention automation
| | >
| | >
| | >
| | >
| | > Subject: Re: [Audacity-users] crossfades
| | > To: "Discussion list for Audacity users"
| | > <audacity-users@...>
| | > Message-ID: < 001701c6e04b$e1724810$6701a8c0@...>
| | > Content-Type: text/plain; charset="iso-8859-1"
| | >
| | > Yah, I agree - the final mix to WAV isn't clearly documented, and you
can't
| | > really tell what is going on. As best as I can tell, Audacity
| | > mathematically sums the corresponding individual samples from each
track
| | > every 44,100/th of a second when using a sampling frequency of
44.1KHz (or 1
| | > divided by the sampling frequency for other sample rates), and
outputs those
| | > summed samples during playback and during export. The problem is
that
| | > Audacity seems to PERMIT clipping at this point, i.e., if the samples
sum to
| | > a value greater than 2**n (where n is the number of bits per sample,
usually
| | > 16 for CD quality sound, or around 64,000), it's no problem - BUT IT
NEEDS
| | > TO BE.
| | >
| | >
| | > p>No, rich, it doesn't...here's why...if you do as you suggest, you
will clip the waveform. what you see are harmonics...they re-inforce each
other slightly, which accounts for the spikes.
| | > fixing it is as simple as going to edit, undo, then lower each track
slightly.
| | > THEN do a "quickmix"...you can always reamplify the resulting wav if
need be.
| | > this is also a good use for compression!
| | > try the kjaerhaus classic compressor, try the default setting, but
put the first slider at 420 the last to 227 or so... seems to be a
reasonably universal setting there.
| | >
| | >
| | >
| | > I know this is the wrong forum for suggesting product enhancements,
but to
| | > me, odomirok1's comments perfectly highlight an issue that's
extremely
| | > irritating yet so fundamental to Audacity's design that I'd bet few
people
| | > are even aware of it. Simply stated, Audacity willingly and silently
lets
| | > you create a clipped final mix without knowing it.
| | >
| | >
| | > p>dude, that is operator error, not audacity error!!
| | > turn the mixed tracks down lower, then amplify after you mix!
| | > if it's CLIPPING, that's cuz the stuff you're mixing is TOO LOUD , or
has too great a dynamic range!
| | >
| | >
| | >
| | > I'd like to suggest that Audacity be enhanced to optionally display a
| | > dynamically SUMMED WAVEFORM that visually represents all tracks mixed
| | > together. That would make clipping easy to spot, giving us with an
| | > opportunity to reduce the levels of the appropriate track(s).
Admittedly,
| | > that would be of little benefit to our visually impaired users, so
I'd also
| | > like to suggest a project-level option simply called "Prevent
clipping",
| | > that defaults to the "on" state. When set, this option would
restrict us
| | > from setting the gain on any track to a level where clipping would
occur in
| | > the mix.
| | >
| | >
| | > p>not cool either, sometimes ya WANT clipping!!!! just use the
amplify tool, make sure prevent clipping is checked if you really need
something like that...it's easy bro.
| | >
| | > So, for example, to bring up the level of one track, we'd be
| | > forced to first reduce the level of some or all of the other tracks.
The
| | > "Amplify" effect already has a simliar feature built in, so I know
this is
| | > possible.
| | >
| | >
| | > p>then why do what you suggest? sometimes, it's better to just use
the envelope tool to control the dynamics, far more useful than turning the
whole track down in the invremments that are default! it's easy....find the
spot that clips, and simply use the envelope tool to re-draw the volume
envelope..once ya try it once or twice, it gets pretty intuitive.
| | >
| | >
| | >
| | > I really like this solution - it seems like it would kick Audacity to
| | > another level of professionalism, by revealing a critical aspect of
the
| | > final mix that is currently obscured.
| | >
| | > Thoughts?
| | >
| | > Rich
yah, dude, no disrespect meant!!!
peace,
jimi
| | >
| | >
| | >
| |
> --------------------------------------------------------------------------
----
| | >
| | >
| |
-------------------------------------------------------------------------
| | > Take Surveys. Earn Cash. Influence the Future of IT
| | > Join SourceForge.net's Techsay panel and you'll get the chance to
share your
| | > opinions on IT & business topics through brief surveys -- and earn
cash
| | >
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
| | >
| | >
| |
> --------------------------------------------------------------------------
----
| | >
| | >
| | > --
| | > Mailing list: Audacity-users@...
| | > To UNSUBSCRIBE, use the form at the bottom of this web page:
| | > https://lists.sourceforge.net/lists/listinfo/audacity-users
| |
|
| -------------------------------------------------------------------------
| | Take Surveys. Earn Cash. Influence the Future of IT
| | Join SourceForge.net's Techsay panel and you'll get the chance to share
your
| | opinions on IT & business topics through brief surveys -- and earn cash
| |
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
| | --
| | Mailing list: Audacity-users@...
| | To UNSUBSCRIBE, use the form at the bottom of this web page:
| | https://lists.sourceforge.net/lists/listinfo/audacity-users
| |
| |
| | --
| | No virus found in this incoming message.
| | Checked by AVG Free Edition.
| | Version: 7.1.394 / Virus Database: 268.12.9/456 - Release Date:
9/25/2006
| |
|
| -------------------------------------------------------------------------
| Take Surveys. Earn Cash. Influence the Future of IT
| Join SourceForge.net's Techsay panel and you'll get the chance to share
your
| opinions on IT & business topics through brief surveys -- and earn cash
| http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
| --
| Mailing list: Audacity-users@...
| To UNSUBSCRIBE, use the form at the bottom of this web page:
| https://lists.sourceforge.net/lists/listinfo/audacity-users
|
