Hi and welcome!
First, let me fix my mistake. The latest update to the Stacker pattern – this time with all the controls working, instead of being inadvertently left commented out – is up in the library now. If you’ve already downloaded the old one (with no working UI sliders), I highly recommend replacing it with the new one.
If I were going to add sound reactivity to Stacker (or almost anything else), here’s how I’d go about it:
First, I’d grab the beat detection code from @jeff’s Music Sequencer pattern (also in the library, discussed in this thread.) You could actually take as much or as little of the rest of his music analysis code as you like.
I’d plug it into Stacker, and let the beat drive the movement speed. Since Stacker’s speed is timer controlled in milliseconds per move, it’d be easy to convert from beats per minute by just dividing the bpm until you think it looks good.
You could also use the Music Sequencer’s phrase and measure detection system to, say, change the number of segments and/or color every few bars. Once you’ve got the music analysis code in, you can use it to change pretty much any of Stacker’s settings.
If you’re not used to coding for Pixelblaze, this may be a little challenging, but we can help if you get stuck. And I’m also curious about how it might look – if I can get a little free time this weekend, I’ll knock together a sound reactive version and see what happens.