Out-of-Phase click

[Ctrl+N]

Sometimes clicks are out of phase and sometimes they are not.



How do I include an image?

OK, so that's how as an attachment. So what's the img tag for?

[Ctrl+N]

I want this observation to be below the image. So I am having trouble with posting images still.

If you repaired the highlighted portions, the click would go away. Or it would be smoothed out, depending on how you look at it.

[kozikowski]

If we're transferring a phonograph record, that can be two different errors. A cat hair can move the stylus straight up and down and give you one error and groove damage can move the stylus straight sideways and give you the other one. Stereo music is diagonal in the groove. Up-right to lower-left for one channel and up-left to lower-right for the other.

No matter what I do, I can't find the Wikipedia picture of that.

Koz

[steve]

OK, so that's how as an attachment. So what's the img tag for?

The img tag is for entering a link to an image that is already on the internet. For example the Audacity logo at the top of this page is at;

Code: Select all

http://audacityteam.org/forum/styles/prosilver/imageset/Audacity-logo-r_190x75_trans_forum.png

The image can be embedded in a post like this;

Code: Select all

[img]http://audacityteam.org/forum/styles/prosilver/imageset/Audacity-logo-r_190x75_trans_forum.png[/img]

and it will look like this;


When you upload an image, there is a button (after the image has been uploaded) called "place inline". When you click that button it will insert code at the current cursor position that looks something like this;

Code: Select all

[attachment=0]clicks.jpg[/attachment]

The image will then appear on the line where that code is.

[waxcylinder]

If you repaired the highlighted portions, the click would go away. Or it would be smoothed out, depending on how you look at it.

Interpolated, rather than smoothed - that is what the repair function is for. You can select up to 128 samples and then apply the Repair effect to that selection. Repair will interpolate a waveform based on the neighbouring waveforms. You will have the same number of sample points as before, nothing will be cut out.

Alternatively, if you;re feeling bold and have a lot of patience, you can use the draw tool to repair the damaged waveform by hand.

The most important part of the process, either way, is the auditory review you make of the repair afterwards to make sure it sounds ok to you.

WC

[Ctrl+N]

Repair will interpolate a waveform based on the neighbouring waveforms

Yes, if there is damage in the middle of a long note, it will create a waveform of the same pitch. It is impossible to tell the note was interrupted.

[waxcylinder]

Yup, that's what's intended - but the auditory review that you do to ensure that it's worked ok is important.

Personally I prefer to use Brain Davies' excellent ClickRepair software for click & pop removal - it costs a little, but is only a little short of being magic. See this sticky thread: http://forum.audacityteam.org/viewtopic.php?f=28&t=1994 you do get a 21-day free trial so you can see if it works for you before you commit to the purchase.

WC

[Ctrl+N]

I don't agree that an auditory review is absolutely necessary. Sometimes there are just too many clicks to review individually. More significantly, if there is no way to tell the clicks from waveshape alone, then how does click detection work within software?

[steve]

You don't necessarily have to listen to each and every click that you have repaired on a one-by one basis. If you run a click repair tool over a lot of clicks you can just play a representative sample. I think the point that waxcylinder is making is that it does not really matter that much what the waveform "looks" like - once you're playing it on your CD player you are not "looking" at the waveform, you will be listening to the music. If it sounds good, it is good. If it sounds bad, it is bad.

[Ctrl+N]

The ear gets fatigued much sooner than the eye. You can't trust it.

But in the back of my mind I am thinking about the repair.cpp:

Code: Select all

This was formerly the PopClickRemoval effect, but it was
renamed and focused on the smaller subproblem of repairing
the audio, rather than actually finding the clicks.

So as I use repair, I am thinking the whole time: mmm, I wonder if I could use what I am learning about what a click looks like to write the code to find them automatically?