XY Morph patch in Add-ons

[bsork]

Ok, I've uploaded a patch in the Add-ons that "morphs" between 4 different sets of 16 parameters using array modules and a script.

I first tried to use sub-patches instead of a script, but the CPU usage went up way too high as I added the subs for each parameter. In the script I've restricted the number of executions to save CPU, since the first version using a script was using around twice the amount of CPU as the already unacceptable sub-patch version.

I used array modules, since handling up to 16 parameters is quite easy and lowering that number just a question of changing a couple of constants. More than 16 parameters is a bit more work, but nothing hard or complicated. Check it out if you want.

[senso]

cool
I take a look.
thanks

[senso]

Less than 1.5% cpu on my old computer (5 years old 4 2.2 GHz)!!!

[bsork]

I also have an idea of using the preset manager to program the 4 parameter sets one at the time and then run a sort of update so that the arrays values don't have to read all the time.

[senso]

try it & let us know

[Vincent]

Hello Bj?rn!
I just feel twice (only) trepanned reading your posts. But I don't care, cause I'm learning!

I also have an idea of using the preset manager to program the 4 parameter sets one at the time and then run a sort of update so that the arrays values don't have to read all the time.

Hey, what do you mean by "the arrays values don't have to read all the time"? How do yo do that?
I am very interested, you know?

Cheers!

[bsork]

Hello Vincent, didn't know I was getting into skull surgery, so I guess I'm learning something entirely new by this...

There was a "be" missing, and I suppose this makes some more sense: "the arrays values don't have to be read all the time".

What I meant, was that I'm trying to create a patch where the 4 sets of values is saved using the preset manager in normal Usine fashion, and then an update routine reads these values into arrays within the script. I was working on this yesterday, but there are some issues - especially when getting the preset values - that have to be figured out. I'm not quite sure if my idea is even feasible given the behaviour of the preset manager, but I'm not sure. The presets might include a bit more than what I thought...

Anyway - don't forget that the morphing can be controlled by something else than an XY pad. What about an envelope follower for the X value, and a pitch tracker or a MIDI controller for the Y value?