Just a general tip for those starting to use the noise: At the beginning I wrote a sketch which repeatedly randomly manipulated x, y, scale (later z also) and showed the resulting noise for 10 seconds AND the actual parameters via serial monitor. If it looked cool, I wrote down the parameters. That helps a lot for a basic understanding/feeling what the noise is.
I mean, instead of compiling a sketch hundred times to see the same thing with slightly different parameters - let the machine do the job by itself and just observe what happens!
And please do not ask me for the skech, I wrote so much stuff in the last days that I completely lost the overview which sketch does what.
Well, at least I managed to take some videos (I showed you just a very few of them…) in order to have a chance later to reproduce what I did.
When I was fiddling with it, I had the zoom parameter hooked up to a pot, so I could adjust it in real-time.
When doing the fine tuning for parameters I used to use a “potentiometer bank”. But because the analog readings are not 100 percent stable it sucked sometimes. I already considered getting a midi controller for these jobs.
I’m thinking of making a fastLED synthesizer connected to several pots and throw some noise and sine waves at it. Would make for an awesome discovery station for kids.
That is an amazing idea. They will love it. I had proof of concepts like that on my table running and my experience is, the the most difficult part is, to filter the input in a way that avoids situations like blackout/whiteout/huge scale noise/ any kind of problem that can only be solved by turning one pot in the right direction. But maybe it is easier to handle if you long not for an extreme range at different effects at once as I did. 
What I used to do was using a universal processing sketch I’d made, to send variables from my computer to the processor via a serial connection. Worked like a charm! And you can send a lot of different variables, like FFT or just stream effects generated on the computer to you pixels. It also gives the opportunity of a nice remote.
I’ve planed to release mine, and a collection of effects, but it’s not finished (not at all) and I do not have much spare time… + the microprocessor I would like to use for my projects (SparkCore) is not supported yet 
The more I think about it the more I see the beauty of these basically simple and obvious idea! I never thought about it before.
It would improve developing effects so much to have some dozens (virtual) sliders and all I need for it I have already.
Thank you for the inspiration @Simon_Hermansen !
Exactly, it takes sooo long to upload sketches again and again just to play with a few variables, and its easy to bind FFT-values to different parameters. It’s all the sound-reactive stuff that are interesting me the most, and I haven’t played with my pixels for waaay to long, so most of the noise stuff have been going over my head. But I may say your experiments have made me pick my Arduino up again (I’m setting up the IDE right now…). Great work! I would just love to have it running on my SparkCore :I
My ultimate plan is to have that all working off a BTLE-connected iPhone app. Initial experiments aren’t looking good—RedBear give you either the low-level Nordic Semi libraries (which need to run some QT-based pile-o-poo on Windows to change the service and characteristic definitions) or their totally undocumented wrapper. Thus my gripe the other day. Holding out hope RFduino is more serviceable.
But when it is working, it’ll be awesome—the phone can hear, see, knows how fast it’s going and where it’s pointed, and has an infinite variation of controls.
Well, that was the reason I bougth the SparkCore in the first place. I got the LPD8806 library working with artnet and OSC from my computer and my android phone, but i would rather use FastLED! But I’m already running out of RAM even without the nice effects… Need more!!