Magic Music Visuals

There is so much potential in the Iterator that I thought it worthy of its own thread. Please post your exported experiments or ideas here. To start things off, here's one of my experiments...



Side note: The latest version of Resolume now includes the radial and linear cloner from Hive8 (which is great) but it doesn't compete with the Iterator.

Here's my video contribution. It's not really an experiment because the scene is included with the application (in the MIDIPiano.magic sample project), but since I created it, I get to post it here .

this is really an incredible software.

All done with one text module and one iterator and a few transforms.

Really nice stuff there Sadler.

Here we have two iterators, one driving the coloured grid with iterator frequency and the other driving randomised digits from a text file. Each iterator has 16*9=144 iterations. I just put the digits and panels together for demo purposes but 288 iterations runs at 60fps.

Thank you for this new tool !
Now making midi visuals is more simple for me

2 iterators here (one is derived from the piano demo, for the color )

I expected this would make your midi creations much easier - perhaps Eric thought of you when adding the midi connection? I imagine there is still quite a bit of fine-tuned maths getting the instrument arranged so elegantly. Your swirly sphere is also great.

I just discovered yesterday that a beat was available with the brand new iterators. And I saw the thread were you started the idea, and was thinking "wow, Eric did it!" so many thanks to both of you , Sadler and Eric! This is the perfect tool for midi/audio visual instruments. The implementation is brilliant and easy to understand. I'm not using a lot of math and expressions, but be sure I will pop up here if i have an idea that I can't compute myself

Because of my simple 3D models, my little creations are a bit old-school , I don't care in the end, this will become "vintage" with the passing years

short demo with the same music and 2 new instruments

Still experimenting with this new toy. One thing I noticed: the offset setting , depending on the tranform/scale/rotate modules you use before, can sometimes be touchy to use. Maybe a setting in the module allowing to choose wich midi note to start with (0-127) could be another way.

Basically it's set up so that the first Iteration # will be the Offset value. So if the Offset is 10, the first Iteration # will be 10. Does that help?

I noticed that. The thing is that it can change drastically your graphics when starting to use a greater iteration number as starting point for calculations.
In addition to offset, a midi note number starting point could be used when you want to change octaves without making changes to other previous modules in order to maintain your graphics behavior.

Well, yes, the reason it changes the graphics is because of the math. But it's easy to deal with. For example, in an Expression, you can do [x-10] if the Offset is 10, and then the first Iteration # will be 0 again.

Thanks for the tip! I'll use it, because I have 4 keyboards (25k, 37k, 49k and 61k), and not only theydon't have a similar middle C note, but some are used for lower or upper octaves.

Sorry, I've tried, but I don't get it to work. Could you please give a simple example?

Nevermind: I found it. I was trying to apply it to midi source/iterator# notes . Instead, I've put it in the modules parameters that used internal/iteration# as source.

Yes exactly. Just to show an example in case anyone else has the same question:
If the Offset parameter in the Iterator module is 3, then you can do an Offset modifier of -3 in your other modules to bring things back to starting at 0.

A question for Sadler: how did you do the wavey effect in your text example, please?

I found a way to make a waving effect, but using a global and expression. I was able to use it with text splitted in lines and lines set to iteration#.

You got it!