ArrayArrayArray BrainModular BrainModular Users Forum 2026-02-14T21:52:14+02:00 https://brainmodular.com/forums/app.php/feed/topic/7429 2026-02-14T21:52:14+02:00 2026-02-14T21:52:14+02:00 https://brainmodular.com/forums/viewtopic.php?t=7429&p=46227#p46227 <![CDATA[Re: quicklink behavior]]> Having a wire solution slower than a wireless one is a kind of counterintuitive!

And I'll keep this practice in mind, using a wait in any case.

Statistics: Posted by XpiR — 14 Feb 2026, 20:52

]]> 2026-02-10T16:17:01+02:00 2026-02-10T16:17:01+02:00 https://brainmodular.com/forums/viewtopic.php?t=7429&p=46225#p46225 <![CDATA[Re: quicklink behavior]]> that is because quicklinks are faster and be computed on the same cycle vs wires may take a bit more time.
the ms counter is sending a trig at the end of duration, and once this is done it waits for a trig on the start input, that can only be done on next cycle
best practice is to use a wait, even with wires.

anyway, you could achieve the same sampler behaviour with putting the sampler in loop mode.
I recommend also that you explore what can be done with the "restarting" output
sampler behaviour.wkp

Statistics: Posted by oli_lab — 10 Feb 2026, 15:17

]]> 2026-02-06T12:33:34+02:00 2026-02-06T12:33:34+02:00 https://brainmodular.com/forums/viewtopic.php?t=7429&p=46223#p46223 <![CDATA[quicklink behavior]]>
There is something I can't explain. If you check those 2 super basic racks :
Rack 1, the counter has a quicklink "finished trigger" that restarts the count. It only works with a wait module (no wait = no restart counter)
Rack 2 is the same patch without quicklink, directly wired : there is no wait module needed.

Can you tell me why ?
(I'm of course not discussing what is doing this basic patch, it's just a behavior example)
Wait_behavior.wkp

Statistics: Posted by XpiR — 06 Feb 2026, 11:33

]]> BrainModular BrainModular Users Forum 2026-02-14T21:52:14+02:00 https://brainmodular.com/forums/app.php/feed/topic/7429 2026-02-14T21:52:14+02:00 2026-02-14T21:52:14+02:00 https://brainmodular.com/forums/viewtopic.php?t=7429&p=46227#p46227 <![CDATA[Re: quicklink behavior]]> Having a wire solution slower than a wireless one is a kind of counterintuitive!

And I'll keep this practice in mind, using a wait in any case.

Statistics: Posted by XpiR — 14 Feb 2026, 20:52

]]> 2026-02-10T16:17:01+02:00 2026-02-10T16:17:01+02:00 https://brainmodular.com/forums/viewtopic.php?t=7429&p=46225#p46225 <![CDATA[Re: quicklink behavior]]> that is because quicklinks are faster and be computed on the same cycle vs wires may take a bit more time.
the ms counter is sending a trig at the end of duration, and once this is done it waits for a trig on the start input, that can only be done on next cycle
best practice is to use a wait, even with wires.

anyway, you could achieve the same sampler behaviour with putting the sampler in loop mode.
I recommend also that you explore what can be done with the "restarting" output
sampler behaviour.wkp

Statistics: Posted by oli_lab — 10 Feb 2026, 15:17

]]> 2026-02-06T12:33:34+02:00 2026-02-06T12:33:34+02:00 https://brainmodular.com/forums/viewtopic.php?t=7429&p=46223#p46223 <![CDATA[quicklink behavior]]>
There is something I can't explain. If you check those 2 super basic racks :
Rack 1, the counter has a quicklink "finished trigger" that restarts the count. It only works with a wait module (no wait = no restart counter)
Rack 2 is the same patch without quicklink, directly wired : there is no wait module needed.

Can you tell me why ?
(I'm of course not discussing what is doing this basic patch, it's just a behavior example)
Wait_behavior.wkp

Statistics: Posted by XpiR — 06 Feb 2026, 11:33

]]>