From the original SynthMaker forum (2004–2014), with its members’ names and dates.
oddson ·
How about a component that delays a trigger and which can be inserted into a problematic green data path to make sure the trigger arrives after the data changes in a parallel data path so that we don't get tempted to use the problematic TThread component.
This is either a good idea... 😇 ...or just an excuse to push Unkargherth out of the top ten posters list... 😈
Tom7777 ·
I may be wrong but i thought you can already do this using the timer module and use a feedback from the output to the stop input of the module. 🙂
stefan ·
or a loop that is ridicously short, or whatever 🙂 a component would ofcourse be fancier....
Tom7777 ·
a component would of course be fancier....
Well yeah i agree but i just thought i would say about the workaround so people can use it until a new module is added to the toolbox.
doug4350 ·
I picked up on something from Malc the other day regarding link order. I vaguely remember it being discussed in my early days, and gave it a passively mental arrogant *duh* response 🙂 and moved on. I may have misunderstood Malc, but can't you keep the datapath in front of the trigger by linking the datapath first, then linking the trigger??? Thinking like a programmer, this would keep the datapath before the trigger in an array, linked list, stack or however they're piling up those things. So, when the engine code loops through all that, the datapath gets de-ref'ed, popped or whatever, before the trigger to keep things in the desired order.
In the case where the datapath goes through a bazillion other "places", I suppose you could buffer the trigger (via a bool component or something) at the point of re-insertion where it's needed.
I hope that makes sense, something tells me otherwise...
Still, I suppose a component for that could be useful, but in the mean time...
Aloha, Doug
infuzion ·
True Doug, sometimes the link order does make a difference.
oddson ·
infuzion wrote: ...sometimes the link order does make a difference.
...and sometimes not!
Tom7777 wrote: you can already do this using the timer module and use a feedback from the output to the stop input of the module.
Thanks, I don't use the timer 'cause I've been lead to believe it has bugs. But it does seem to work in this capacity.
stefan wrote: ...or a loop that is ridicously short
also seems to work.
For both of the above suggestions I tested against the example in the bug in string equals module. But you could fiddle with the timer delay or loop number until you get the result you need.
So, for my suggestion, nevermind! 😇
Wrote something here? To have a post removed or your name hidden, write to [email protected].
SynthMaker