I like that the “skirts” of the active segment can be tuned so not only the plosive blast goes away, but the slight click before and after as well. That example is far from what I can do with more effort. You can still hear I didn’t get the delays quite right.
Given that there is no valuable work at all during the pop, gracefully suppressing them without damaging anything else is a good thing – and I didn’t drill them down to nothing, either. They’re just a lot lower than they were and probably a handful of dB down from the overall show volume. They sound like the performer is too close to the microphone, but the pops don’t shatter glass any more.
I’ll play with it a bit and let you know how I get on. I’ve a very badly damaged copy of Neil Young’s “Harvest” (damaged before I got it, I hasten to add) which should make a good test bed.
However, one problem I can see with a record as badly damaged as this, is that there are places where I’m left with gaps where the pops used to be, which is nearly as bad. What about looking at the audio level for, say, 10ms either side of the pop, and setting the attenuation to that level?
If the effect is being used on one pop at a time, that relatively easy to do.
If you mean that you want to be able to process multiple pops with a dynamically changing mute level that follows the dynamics of the music, that is quite a bit harder, and I expect that it would also require the threshold level to also change dynamically.
This is not a “clever” effect, it just blindly attenuates sounds that are above the threshold down to a “floor” level. I’ll have a look to see if I can make it a bit more intelligent without it becoming horrendously complex.
Pop Mute is a real time saver. I record church services for CD and podcast, and we have a couple of people who can’t remember not to clap in front of a mic. I fade out the mic, but not before I’ve got a string of spikes in the recording. With this tool I can squash the whole string in one operation instead of manually fiddling with each one. It even works on coughs. Just one simple improvement to suggest: Separate settings for attack and decay. I use a ceiling mic to pick up individuals in the congregation speaking without a mic. Sometimes a cough reverberates, so it has a sharp attack and a slow decay. The separate controls would let me approximate the event envelope.
There’s always a balance to be drawn with this type of plug-in between flexibility and simplicity. As the complexity of the interface goes up, the usability goes down (especially for casual or novice users). My aim was to make this plug-in as simple as possible to use.
That’s a persuasive argument for adding one more slider.
There’s been no comments regarding the “Linked Stereo” mode, so I’m guessing that it’s not really useful.
I’ve removed the “Linked Stereo” option in this version, though it can easily be re-enabled (open popmute.ny in a text editor and read the comment text near the top of the file). popmute.ny (1.84 KB)
Only built-in effects can be used in the 1.3 batch mode at File > Edit Chains.
You could import all the files, Select All then run the effect and come back later to do Export Multiple (this assumes there is no valid reason not to using this effect). However it would add silence at the end of tracks so as to make all the tracks as long as the longest one, so that’s a good reason not to run Nyquist effects on more than one track at a time at the moment.
That track does not lend itself to using pop-mute to remove the bass drum: on that track the bass drum does not produce peaks above the rest of the track, which is what the pop-mute technique I suggested relies upon.
You could just cut the bass from it using equalization to reduce the bass, a before-after example and equalization curve are attached.
What was the benefit of linked stereo? If the pop was only in one channel it would seem to artifact the other channel to no purpose.
I attached a wav file with an artificial spike of 10 ms (EDIT this meant 10 samples, see post below) generated white noise. Strangely Click Removal seems to remove it with less artifacts than PopMute (I tried less attack though it did not help much, and I appreciate setting the mute level is critical). Perhaps like Paraic, I think it might be good if the effect could be more clever and have an “auto” setting that tries to figure an appropriate residual level. Even when I matched the mute level exactly I still sensed more of a “whoosh” in the area than Click Removal produced. Perhaps unlike Click Removal, the recommendation for PopMute should be to use it on as small a region as possible?
Clearly though there are many cases where PopMute works and Click Removal has little or no effect.
I added links (not attachments) to the front page post:
The “benefit” is:
If the effect is applied to audio with a long burst of noise on one channel, using a slow attack/release, independent channel processing will cause the stereo image to swing violently across to the side without the noise (not much fun if you’re wearing headphones and riding a bicycle at the time).
In practice I found that linking the channels is very rarely useful, and in my opinion not worth the additional control.
You mean 10 samples of white noise?
Yes, for very short clicks the Click Removal effect is much better, but with clicks of 10 milliseconds or more, Click Removal will hardly touch them, and that’s where “Pop Mute” can come in useful. Pop Mute not a subtle effect, it just bashes spikes with a big hammer, but it can make loud pops (and even hand claps, drum beats and small explosions) less obtrusive.
Sorry, I did of course mean 10 samples! And Click Removal also seems fairly ineffective on even narrow spikes if they are not very much louder than their surroundings.
What do you think is the best route to getting a single click/pop removal effect that removes a wider range of disturbances? Can Click Removal ever be improved? Is the better route to make Repair work on much longer selections? The two proof-of-concept attempts at doing this a while ago were apparently fairly successful.
Meantime should PopMute be “starred” as a Wiki candidate (even if you eventually try to make it more intelligent)? I guess it only needs a single page of “help”?
This could be classified as a bug report with a workaround found. I don’t know whether the issue is in Audacity itself or in the effect I was using. I use this effect often and have never seen this happen before. I’m using Windows XP, SP3.
I had 162 ms selected about 30 minutes into a long track (project has two tracks but the other track is vacant (no clip) in this area). I tried to use Pop Mute (tried both versions) and consistently got an error box:There is not enough room to paste the selection. After the operation, the selected part had been deleted . I undid the operation and tried setting the threshold so Pop Mute would do nothing. Same result. I undid it again. I tried setting the Attack/Decay parameters very short. Same result. Undo. Changing the length of the selection made no difference either. Then I tried duplicating the selection and operating on the copy with my original parameters set. Success !
My curiosity now stoked, I tried another experiment: I split the original track (selection was now a clip within the track). Pop Mute worked on the clip just as it had on the copy.
One more experiment: I undid the effect and duplicated the clip. Length of the new track was 7176 samples. I applied Pop Mute to the copy, then clicked on the track panel to make sure I had it all selected. Length was still 7176 samples.
PopMute is a third-party plug-in and not directly a part of Audacity, so it’s best to post feedback/bug reports directly to the third party rather than in a general Audacity part of the forum. In this case, I’m the third party and this is currently the “home page” for this effect (I presume that you downloaded the PopMute plug-in from this topic).
I’ve moved your post here so that it is together with other discussion for this plug-in.
When testing plug-ins (and software in general), use the most current version, which in this case is version 0.2 (experimental).
That’s curious, because that error message is not generated by the plug-in.
I’ve not been able to reproduce the problem.
Did the problem occur only with that one audio track, or are you able to reproduce the problem with other audio tracks?
Which exact version of Audacity are you using (Look in Audacity “Help menu > About Audacity”)