Audacity Forum

Just like Normalize, Click Removal could be automatically run (optionally - with a preference setting) on import. It's only a few lines of code and I have been using it now for a while quite happily.

Click Removal is not always a go-to-completion tool. If you mess it up, you could be called on to transfer the record again. Far better to do it in post where you only have to transfer the record once, IMHO.

Koz

If Click Removal is run automatically, can it be "Undone" (Ctrl+Z) to revert to the unprocessed import?

steve wrote:If Click Removal is run automatically, can it be "Undone" (Ctrl+Z) to revert to the unprocessed import?

Of course, just like with Normalize. My typical workforce is: go out and get a lot of old vinyl from the swap meet; digitize each as raw recording direct to CD (one track includes both sides); pile up these raw recording CDs until I have a couple hundred pending. In the meantime I'm doing studio work making demo CDs for bands etc. (no Click Removal wanted). When I get a long window of spare time I grab the CD pile and start processing them with Audacity - often do 20 or 30+ a day. That's when I turn on CR on import; I know I'm going to be cleaning them all and it just saves a step.

I'm asking because I don't use these features so I don't fully appreciate how they benefit work-flows.
How is this better than using Click Removal in a Chain?

steve wrote:How is this better than using Click Removal in a Chain?

Better - no, just different workflow.

With chains the user selects a bunch of files, starts the chain process then goes off for a cup of [insert favorite beverage here]; later she opens the "Cleaned" folder and must again import each file to do any individual processing.

I am not sure if the new ability for Chains to select multiple audio files from different folders has been committed, if not this means that all the files one wishes to process must be in a single folder. My typical folder structure looks vaguely like: Using a preference item to apply a (usually built-in) effect means that the file needs to be imported only once and (for me at least) it is easy to work within a fairly typical folder structure.

My issue with this is that you are overlooking the fact that Audacity Click Removal is not best-in-class - and would benefit from improvement/re-write.

See this section in the Wiki: http://wiki.audacityteam.org/wiki/Other ... estoration

Peter

I like the idea of streamlining the work-flow and automating repetitive tasks, but I'm wondering where this is going and whether "Just like Normalize" is the best approach.

I can see the case for adding a Preference for Click Removal on Import, just as I see the case for Normalize on import. Although I'm unlikely to use these features myself, I also see the case for adding a Preference for DC offset removal on Import, and for a Preference for "Rumble Filter" on Import, and for "Hiss Removal on Import" ...

Would it perhaps be better to be able to select an "Import Chain"?
The user creates a Chain of commands that they wish to use on import, which can contain Normalize / Click Removal / any other effect that they wish to apply prior to importing, and then some way to enable/disable that chain for all subsequent imports? In other words, I'm supporting the proposed "feature" but questioning how / where to achieve it - perhaps an individual "Preference setting" is not the best place.

Do we want to transfer this FR to the Wiki??

Peter

I'm not keen on automatically processing files on import. It could easily become a nightmare for support ("Why is the audio bad when I play things in Audacity?").
If we have this at all I think that it has to be off by default.

Rather than multiple options for processing audio on import, I'd much prefer one option to apply a user defined chain on import (off by default).