

Do this by inverting the original, and mix (1:1) with the Clickrepaired file. I find a good way to be sure you are not affecting the music much is to use a music editor (I use Goldwave, but it should be the same with any editor) to subtract the original file from the Clickrepaired file. I find I can quickly step through the album, rejecting any proposed fixes that are at the beginning of a music transient, and accepting the rest. Listening to the area as jfall suggests is a good idea. Of course these are just general guidelines. In the second set of pictures, I would guess that this is a true click, since it does not seem to correlate with a music transient. Even if it was a click that happen right at the start of the transient by pure luck, I doubt you would hear it. In my experience, this is almost always a false detect as opposed to a true click. The proposed fix happens right at the start of a "burst" of music. You can see this in the top trace where he has circled the proposed fix. In the first set of captures that jfall posted above, I would reject that repair because it occurs exactly at the start of a music transient. The trick is to find settings that maximizes the automatic finding and fixing of true clicks, while minimizing false positives.
#CLICKREPAIR ERFAHRUNGEN SOFTWARE#
When using ClickRepair, I run with the settings shown in the left image, listening to the output to identify missed clicks (and going back to manually repair them if I feel it's worth the time), while viewing the trace on top to identify false positives (transients that the software identifies as clicks, and going back to undo those). In the right image that has had the changes applied, the transient is now colored red, signifying that a change has been made (transient wiped out). In the upper right of each picture I have circled the area of the audio file that is zoomed in, creating the larger trace in the center. If I had chosen 'Resume' instead of 'Accept' the software would have moved on without affecting the audio. If I accept the change, the result is as shown in the picture on the right, the transient has been wiped out. The red trace within the circle in the center has been identified as a click. In the image on the left, the software has chosen a transient and paused for my input. I'll try to give an example of the loss of a transient. Your question is very general and tough to answer you should read the manual. I use ClickRepair in semi-automatic mode all the time. I find I can often clean up an album perfectly with this approach, although I still always play it through in real time on my editing program (Goldwave) and listen for any clicks that I missed. I can set it to aggressively remove the clicks in the quiet passages where they are more noticeable, and then back off so I don't affect the music transients when things get busy. During very loud, ‘raucous’ passages, I set it very low.ĭoing it this way, I can clean up an entire album in about 15 minutes or so. I usually end up sliding it higher to clean all the clicks during the quiet lead in to a song, then reduce it as the music starts building in intensity. If you decide it is stopping too often on false detects of music transients, then you can slowly raise the "Declick" setting until it quits getting false detects, or at least gets a reasonable number of them. This will cause the program to stop very often to highlight a suggested repair. The nice thing about this method is that you can set the "Declick" setting on the fly. If you decide it is not a real click, then select "Resume", which will start processing again without applying the repair. It will then apply the repair and start processing again until the next time it identifies a repair that exceeds the "Automatic to" setting. If you decide it is a click, then click "Accept". False triggering on the rapid rise of a music transient seems to be the most common place for Clickrepair to show a false repair. If it is in a more constant passage, then it is a click. If the suggested repair is at the beginning of a music transient, then it is not a real click. A key clue is to look at the top display. After some practice, it is easy to tell by looking if the repair is a real click or if it is due to a music transient that should not be repaired. But for larger repairs (more than 10 consecutive samples), it will stop with the suggested repair highlighted. This means it will automatically fix anything that involves less than 11 consecutive samples to repair. I use less than 10 with a 24/96k recording. It's been a while since I've done one, so I may not have all the terminology correct, but basically you set the "Automatic to.

I have also done an entire album by editing purely manually with an editor (Goldwave), but now I have settled on using the "semi-automatic" mode with Clickrepair. I started trying to find automatic settings that worked for an entire album, then just for an entire song, but I gave up even on that.
