From the original SynthMaker forum (2004–2014), with its members’ names and dates.
Dave B ·
Are the green processing paths smart enough to only recalculate the path if something changes?
Also, are there green path optimizations when data supplied are all constants?
On a related note do knobs only consume CPU resources when actually being changed or do their values get recomputed constantly?
rl ·
- AFAIK yes, that's what they are made for. In my understanding the green wires transport values AND triggers (when values change)
- e.g. a float that doesn't change his value causes no trigger
- no extra CPU. Only when redraw is triggered.
Dave B ·
Makes sense, but things don't always work as you think they might! 😇
Tom7777 ·
but things don't always work as you think they might!
Definately true, i find working with modular apps trial and error methods are the best way to work and having found quite a few bugs now which have stopped me from working for a while things don't always go right too when working with modulars 🙂 But again i must say this program has some great devs and if i ever find im going to have to wait for something i know that wait wont be long as they are great at fixing bugs 😀
infuzion ·
rl wrote: - e.g. a float that doesn't change his value causes no trigger
Not true; often a green connected to something will send a trigger (& resend the value) when it is activated. Eg, when a GUI with a DragXY will "bump" the float. To get around this, you need my Sample & Hold on Change
Dave B ·
infuzion wrote: rl wrote: - e.g. a float that doesn't change his value causes no trigger
Not true; often a green connected to something will send a trigger (& resend the value) when it is activated. Eg, when a GUI with a DragXY will "bump" the float. To get around this, you need my Sample & Hold on Change
Yeah, I saw your sample & hold post and wondered about that if the green paths are "smart". Do you have other examples of what causes triggers in green paths with no associated data change? I would not expect most typical GUI usage to impact the audio performance significantly if properly implemented.
infuzion ·
Sure Dave, * Everytime you change a Selector or Multiplexer, you'll bump the value, even if the actual value doesn't change. Workaround
* When you bump the conditional for a comparison, you'll bump the output, even if the test result stays True/False.
Trigger Filter suggestion
sambean ·
Round float to integer: These can cause trigger paths with no change in value too..
eg 1.1->1 + trigger, 1.2->1 + trigger...
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker