Afternoon, I managed to get the clicks out of my audio with the DeClicker tool. if anyone would like my settings, they might vary but are here
The only problem is I have to manually find any bad audio and select 10 second intervals for the DeClicker because of how much RAM it uses if I try to DeClick the entire project. 2 quick questions:
Is there a Nyquist script for being able to run it for 10 seconds every 10 seconds until the end of the project? As in Declick for 10 seconds…stop…Declick another 10 seconds, repeat until finished
Would it be extremely memory-intensive if this script is run?
I apologize, my hands are so messed up that I can’t try to fiddle around with a script myself. Actually this post was mostly dictated (this was brought over from Reddit). Thank you for any guidance. I’m using 2.4.2
Do you know where the clicks are coming from? My test voice submission failed because of lip and tongue “click” noises.
run it for 10 seconds every 10 seconds
I can think of one programming reason not to do that. When you do the job manually, you know where the clicks are and so you can place the declicker optimally. If you get software to do it, you could have clicks at the boundaries of the correction and just change the noise into something else. We note that errors like this can tell when you’re working on an important show.
Would it be extremely memory-intensive if this script is run?
It wouldn’t make any difference because you can change the aperture (correction time) and just wait it out.
And speaking of memory. There’s things you can do to help there. There is a “Clean Shutdown” (Shift+Shutdown) in Windows which doesn’t try to “help you” by remembering running software and settings. It shuts everything down. If it asks you if you want to open up existing software after the shutdown, say no.
Now run Audacity and the aperture may be longer. It may just go from ten minutes, to fifteen or twenty, but still.
You might hate to hear this, but in my nearly five-hour video, I had to run through the entire thing and highlights however many seconds to run the plug-in on the entire time. It took about two weeks. That’s part of why I’m making this…the other is for my arthritis
I can think of one programming reason not to do that. When you do the job manually, you know where the clicks are and so you can place the declicker optimally. If you get software to do it, you could have clicks at the boundaries of the correction and just change the noise into something else. We note that errors like this can tell when you’re working on an important show.
From what I remember, that’s actually true. Sometimes the Declicker would miss certain clicks or create minor ones. The latter often done when running multiple passes. 90% of the time personally, these issues didn’t come up for me, but I also wouldn’t mind keeping two copies of the audio to undo the 10 so mistakes the program would make every 5 hours. It’d still save my hands so much
It wouldn’t make any difference because you can change the aperture (correction time) and just wait it out.
Thank you, that’s exactly what I’m hoping. I could literally just go to sleep on it if that’s the case and wouldn’t mind either way. I’ll give that clean shutdown a try from now on. Never heard of it before, but what you’re saying would save me a lot of trips to the task manager. Thanks a lot
I am sure Steve or someone will spot the flaws in my reasoning, but I am thinking that a Nyquist routine couldn’t do this as you would have to pass all of the audio up front, and a macro couldn’t do this because it can’t loop.
Now I imagine the audio could be split into a large number of small files by creating Regular Interval Labels, then doing Export Multiple. A macro could could process and export each of those files, which could then be imported and re-connected via Align Tracks End-to-End and a Mix and Render.
You’re right, but there’s more to “why” you’re right.
I assume that the “DeClicker” tool being discussed is the Nyquist Plug-in from this forum. A Nyquist plug-in cannot launch another Nyquist plug-in. I expect that it would be “possible” to write a de-clicker plug-in in Nyquist that could handle long selections, but it would be a big job, and the original author of the DeClicker plug-in has moved on to other things.
Well, that’s disappointing but good to know still so I don’t rack my brain anymore on trying to learn this programming for the plugin. Thank you all for saving me time.
