CPU usage

[Vincent]

Hi all.

Well, it's not exactly a patching question... but...

There we were talking about velocity changes (ratios). Of course, the first thing I did was to make a simple sub-patch. I'm used to that, I did a lot of things in Reaktor. But when I saw the CPU% in the top-left corner, I had nightmares.
I really have no mean to check the difference with equivalent plug-ins, but the tests give points to plug-ins for many patches (not talking about audio, just data and Midi data). And I can bypass them when not used, not patches.
I've also tried to build something to remap midi notes (there is nothing similar in MFX on the Web). It's a crazy stuff. more than 12% CPU (Pentium IV 3 MHz, dual core soon, be patient, boy). As I have 3 keyboards, I have to use that patch 3 times, that makes almost 40% CPU only for that gadget!
I'll now try it with array modules, maybe shall I be able to remap any of the 127 Midi notes... But with how much CPU?
Then, if it's again too greedy, I'll make my midi thru Reaktor in plug-in with my old patches. As I also need it as synth, why not?...
Then, shall I have new ideas?!

In fact, I'm wondering if Usine is not a little bit too greedy for certain things ? (if I had a bug report, it would be that!) Or am I doing wrong wiring, using the same "routines" as I used in Reaktor?

I know it's just my problem, I should find solutions by myself and I would like to. But since I don't know Usine as well as some of you do, sorry, I need help. I need to understand. Because the stuff I'm building is big and it's the main tool of my duet.

Thanks guys for your answers, I really really appreciate, you must know it (in fact, I don't need Usine Pro but I'll get it soon, be patient boy! just to say how i appreciate). And one day I hope, I'll be able to help beginners like me.

Cheers.

[senso]

hello,
As you noticed, the scripting language is not really CPU friend...
But the Note 'transposition and velocity compressor/expander' script is very light, and shouldn't take more than 0.5% of CPU.

You allways have to find the best solution for all your problem:
Vst?, Script?, Modules? which preference?

My personnal rules (preference order):

For audio: 1:vst, 2:Modules , (no script)
For Midi: 1:Modules, 2:Script, 3:Vst
For Data/array: 1:Modules, 2:Script

The tempo detector (add-on) is a good example of this rule application. (less than 3% on my system)

Usine has nothing to compare with Reaktor. A Reaktor patch is allways made of many (thousand ?) "small" modules.
In Usine, 50 modules in a patch is huge, because modules are bigger.

Also, as you probably noticed, in Usine it's very easy to build a patch:
- flow conversion is made automatically (connect and play),
- you can mix flow together,
...
Everything has a cost...

Usine is not designed to replace Reaktor but to play with!
I use it a lot.
Feel free to mix Usine, Reaktor, vst's in the same patch.

[bsork]

Vincent, take a look at the Mapper Values module. It lets you map any value to any other value, the drawback(?) being that the values are "static" and must be entered manually. Also remember that you should be able to use parts of the various midi messages - eg the note number - to access the array elements, both in the array modules and in your scripts.

[bsork]

Ooops - just checked the Mapper Value module and it has only 16 values, so it's not a good candidate for holding remapping of for instance all note numbers to some other value.

You can however do almost the same thing in the array editor; you don't have access to the "from" value, but as you can use info from the message you're mapping to get to the right element of the array, that shouldn't do much. You'll maybe have to add or subtract 1 when doing things like these, but that's fairly common when programming anything in my experience....

[Vincent]

Yo!

Olivier: Thanks for your recipes. That's exactly what I needed.
It's true that Usine is more flexible than Reaktor (in wiring, sorry to compare!). It's true also that I must avoid to build patches with hundreds of modules like in Reaktor and find more efficient solutions. As you said, 50 modules in a patch, that's huge.
I have to be clever!

Bj?rn : Well, if you're interested, i'll put on line tonight my last version of the Note Manager (filters a range- THEN -remap notes- OR -transpose- AND/OR -change velocities with a ratio). I think I finally got the solution: array editor AND script. I hope.
It seems to me that you're very well minded for scripting, very logical. You really help me with your comments. BTW, MIDI Transform module does not exactly what I want, it's another purpose. I think I'll use it to make a module that plays synth pads (or harmonic groove) while I'm playing bass or something like that... But not now. First build my instrument, then experiment stupid features!

Thanks to you guys, you're quick and clear. I appreciate.