You could but is it worth the effort when you can get Brians Davies' ClickRepair for $40?Ctrl+N wrote: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?
IIRC SteveTF had a bash at a click clean-up plug-in a while back - maybe he will let you have a copy of his code as a start point for you ...
But yes, a good way to learn audio programming - if you get really good the Audacity developer team would welcome you as a recruit.
============================================
With regard to review - my advice there was somewhat aimed at the new user of repair tools (like the Original Poster of this thread). But personally, these days I have my copy of ClickRepair tuned with defaults that suit me and I just run it as a background task without monitoring. But one of ClickRepair's great strengths is its monitoring capability.
You can set it to nil auditory output (gives the fastest processing time) - but you still get a visual diplay showing what it is doing.
Or you can choose from thefollowing outputs while it is processing:
1) Noise only: this is the part of the signal that the s/w is removing - very useful as it enables you to listen to how much, if any, of the music is being removed (helpful in setting the pramater level for click removal),
2) Output signal: the cleaned, click-removed, signal,
3) Input signal: the raw input.
You can select from these via a set of radio buttons - and you can switch between modes while ClickRepair is working on your audio.
WC