Download EZ-Patch (read the instructions below first!) EZ-Patch.ny (2.17 KB)
I have an audio track with a bad glitch on the right channel (shown selected)
The glitch is too big and bad for the Repair tool.
It can be moderated using the “Pop Mute” effect, but that will not remove the damage, it’ll just make it a bit smaller.
The best way to repair would be to make a “patch” by copying and pasting a similar piece of audio and cross-fading rapidly from one to the other. The audio immediately after the glitch would be suitable for making the patch, but it’s quite a fiddly job to make a good job of patching.
Time for “EZ-Patch”.
Here’s I’ve selected the glitch and allowed a little room either side for a rapid cross-fade, then extended the selection to the right fare enough to create the patch.
Doing this manually would require multiple steps, but with EZ-Patch all that is needed is to select, then click OK.
It’s a percentage of the “patch” (see the second picture in the first post). In other words, a % of half of the selection.
If set to 50%, the crossfade at the beginning of the patch will meet the crossfade at the end of the patch.
Usually you would want the crossfade fairly short - it’s there so that the transitions into and out of the “patch” are smooth.
I read the code. What is bug 425? Does it involve incorrect trimming of right channel stereo results, sometimes? Because I tried my own work in progress on this example and that is what I saw, and when I imitated your workaround it went away.
My own efforts at automatic click removal seem not good enough to fix this example, though they are very promising with fixing the speech crackles which are actual but undesirable recorded sounds, not playback glitches from old media.
It doesn’t seem to quite match Leland’s explanation, but note that the comment in the plug-in was nearly 2 years before Leland offered that explanation. It matches the bug in as far as Audacity is not handling the returned stereo data correctly, and in the problem that I’m working around one channel (the left) is a reference to channel 0 of S.
If the problem that I worked around in EZ-Patch has the same cause as (vector (aref s 0)(aref s 0)) not returned correctly to track, then yes the evidence is there. When I wrote that comment I clearly thought that was a more likely possibility than that it was unrelated. What do you think? Do you think it is an unrelated bug?
I have been searching hi and low for the download link to EZ-Patch and have been going in circles on the Audacity site. I checked the Nyquist Plug-Ins, and New Plugins but cannot find it, yet there are posts regarding it here in the forum.
Can anyone tell me what the download link to the EZ-Patch plug-in is ?
Thanks Gale, the 1st link your provided allowed me to download EZ-Patch.
However, your second link takes me to the page I was previously looking at for EZ-Patch and where I clicked on the various links on that page.
Per your comments, the 1st link is supposed to be the download link for the plug-in: Unless I made a mistake, at the top of the page there are two links, neither of which do anything when I click on them, and the URL for each of them is not the same as the link you provided me for the download - so either I’m clicking on the wrong link(s) or the links on the page are not correctly formed.
I somewhat agree, especially given the first post is very long and detailed and the white attachment box for the download is not not that obvious. If you don’t know you are looking for an NY file, it is even harder.