If you increase the number of passes, this will allow you to catch clicks that were too near to another click to be detected the first time.

The De-Clicker enforces a minimum amount of time between clicks. Other parameters (grouped by topic, but no particular order) Eight (2^ 3) is three octaves, 16 (aka 2^ 4) is four octaves, etc. If it’s four times (2^2), that’s two octaves. To calculate how many octaves your frequency range covers, if the high value of your frequency range is twice the low value, that’s one octave. My current settings actually use 8 bands (4/octave) though, for increased sensitivity. This is 2 octaves (5,000 * 2^2 = 20,000), so to have the same number of bands/octave as the default I would only need 4 bands. For example, I mostly notice clicks that are higher pitched, so I set the range as 5,000 to 20,000 Hz. Low frequencies are more computationally expensive ( see forum post), so if you don’t usually have clicks down that far, you can omit those frequencies from testing. This is one band per half-octave (150 * 2^6 = 9600, so 6 octaves). Under the default settings, the de-clicker processes 12 bands, from 150 Hz to 9600 Hz. So, picking good values comes down to balancing those two factors. More bands = better click detection, but also more bands = slower. The main thing controlling both sensitivity and computation power needed is the number of bands. Frequency range and number of bands (default: 12 bands over 150 - 9600 Hz (2 bands per octave)).Most important parameters for sensitivity and computation ( source) I’ve attached my own declicker settings for reference at the end, in case that’s useful to anyone. After reading through this entire thread over the past couple days, I decided to compile some experimentation guidance and explanation of the different parameters as I understand them.

Audacity declicker download