The circuit in post #19 is what I meant. This link gives the formula to calculate the fc of your second order low pass filter in post #20.
Les.
Les.

That sounds like a lot of circuit to design, ak.......The basic functions for an audio trigger go like this:
Mic amplifier
Lowpass filter
Envelope detector (Half- or full-wave rectifier, plus filter)
Comparator with adjustable threshold (and adjustable hysteresis?)
The envelope detector is key. Even with things rolled off at 120 Hz, you don't want the individual cycles of a bass guitar note showing up at the uC as a burst of 30 trigger signals in 1/2 second. The rectifier circuit can be more or less complex. Least is what you already have, with the lack of a negative power supply turning the mic preamp into a faux-rectifier. Not a terrible idea, but not the best performance. What is an outstanding feature of the 358 in many applications - that the input stage common mode range extends *below* its negative power pin - works against you in terms of how "precise" the rectification is.
There are many ways to do each of the stages, but my first thought is that it will take a 2nd LM358.
ak
And that is what I think is wrong with the existing circuit, a burst of noise causes extremely rapid bursts of the chases on the light controller, too fast to actually "see" the effect. I suspect the trigger input pin is assigned to an interrupt that steps the chases on, and there's no "delay" built-in to stop it being triggered rapidly. If I had written the code I would have found a way to suspend further interrupts for a time period, I'd probably make it about half a second, so that rapid step changes can't occur. But there's no way I can get at the code for this mcu, not without spending way too much money and time. So any repeat triggering delay must be put into the design, which I could likely do with an Arduino Nano or the like - sort of like a "pre-processor"Even with things rolled off at 120 Hz, you don't want the individual cycles of a bass guitar note showing up at the uC as a burst of 30 trigger signals in 1/2 second.
Yeah, I though the list might spark a concern. But breaking things down to their fundamental steps is the only way to make sure you've got everything covered. Plus, its not really as bad as it looks; some functions can be combined into one stage.That sounds like a lot of circuit to design, ak.......
The code probably is doing some form of peak detection or averaging, what would be dome with a diode and a capacitor. Lowpass filtering is difficult to do in software, but you might be able to get away with a single-pole filter after the preamp.EDIT : I've just found a code sample for the Arduino which detects the beat from music !! Probably won't need all those functions, just a variable gain mic pre-amp ....
Noted. Although to be fair, I'm not after fidelity, and if the MIC module has to have a higher gain to compensate I don't think I'm really bothered, providing the filtering algorithm in the software works well.Note the rather poor low frequency response of the mic module. Other than that, sounds like a good plan.
The MIC amp module I am using is this one, not the one I posted earlier...A 1 nF cap from between C1 and R4 to GND should squelch it, if that is what is happening.

Well I have breadboarded the Arduino beat detection circuit, and I have to say it works infinitely better than I had expected. So much so that I'm going to roll with it and build it into my DMX lighting controller.I will be having a go with this today, see if I can get beat detection working.
One of the great beauties working with Arduino's and the like is the ability to infinitely "tweak" the software to get it working as you want it, and I'll be using a wifi module and RemoteXY on my iPhone or iPad so that I can change program variables "on-the-fly". This will be a great bonus for live performances ....