News:

Welcome to the AlpineSoft support forum.  To return to the main website, click here: www.alpinesoft.co.uk

Main Menu

Getting rid of a repeating 'crick' noise

Started by Steve Crook, June 27, 2019, 01:36:04 PM

Previous topic - Next topic

Steve Crook

The first track has this noise on one channel every revolution for about 5-8 minutes (so 150+ of them), each cricks section lasts around 0.25s. It's immune to automatic click removal at anything less than destructive levels, so I've been selecting the bit with the cricks and re-running click removal on the selection at Max, 6 or even turbo with little or no percussion protection.

It does a good job. But. It's tedious and slow, even using ) to go to the next revolution. Is there an alternative method or some way to automate it?

FWIW I've cleaned the LP *twice* on a Moth RCM, so, short of splashing out on an ultrasonic cleaner, whatever gunge is on the LP is there to stay.


Paul Sanders (AlpineSoft)

Hi,

It's probably some kind of scuff, and therefore immune to (physical) cleaning.

The best you can do is to use ')' and then repair the section manually, either as you are doing now or perhaps by using Patch.  Sorry I don't have better news for you.

Steve Crook

Here's how I dealt with this.

  • Work though the area affected using ')' to skip a rev at a time and marking the beginning and end of the crick sections so they're there for future reference
  • Pick a representative section, select it and scan. Start at level 6 with max percussion protection
  • Iterate through increasingly powerful click repairs until you've got the least aggressive settings that'll give you acceptable results
  • Then it's just a matter of selecting between the markers for each crick, repeating the click removal and checking everything is OK
  • Sit back, relieved it's all over
I tried manual click repair and patching, but found neither worked well for a noise that was made up of a bunch of relatively close but not very peaky transients.

Manual click repair would have worked, eventually, but because the individual crick components weren't close enough to be covered by a single repair I found I had to had to find and correct a dozen or more elements for each crick. Too tedious. Patching sometimes worked, and sometimes didn't, often, to get rid of a crick I'd have to use so much that it caused other equally intrusive artefacts to appear in place of the crick.

So it took a while, but I'm happy with the result.

About the only think I can think of that would have speeded it would be to be able to tell VS to apply the same correction between a selected set of marker pairs. But, honestly, just writing the sentence seems like a lot of work...

Paul Sanders (AlpineSoft)

> About the only think I can think of that would have speeded it would be to be able to tell VS to apply the same correction between a selected set of marker pairs

In the corrections list, click on the first marker and then shift-click on the second.  This will select all the audio between the markers and you can then do 'Scan Selection'.

HTH