Page 1 of 1
Posted: 15 Dec 2009, 19:36
by grego mondo
Sub Patches makes things clearer and easly re-useable, but is it a good way (in terms of CPU and speed) to do lots of them ?
Posted: 15 Dec 2009, 20:00
by martignasse
Hi grego modo,
Agree, Subpatchs in one of the master keys for modularity.
The cost in term of CPU is justified (and generally negligible) as it let you organize and master a big workspace.
You even have a Browser->Interface Control->Patch active (turn on/off) module to put in your subpatchs, so you can save some CPU by turning off the subpatch when not used.
and what do you mean by 'lot of them' ?
Posted: 15 Dec 2009, 20:22
by grego mondo
not so many, just talking about may be ten, just to know if it's a good habits ("habitude") or not.
Thanks !!
Posted: 15 Dec 2009, 21:26
by martignasse
ho yes, it's a good 'practice'.
and 10 isn't a lot.
i have a workspace with maybe 100 of them (cant know exactly) and i cant imagine achieving the same result without.
GO GO with subpatch
Posted: 15 Dec 2009, 22:51
by senso
In future version (not the V5 but perhaps the 5.1) sub-patches will cost nothing more in CPU. I have an idea of an important optimization.
Actually it cost the copy of data's into wires.
Also, a data input module cost less than a fader input try to use them as much as possible.