Welcome to %s forums

BrainModular Users Forum

Login Register

quicklink behavior

I need help on a Patch
XpiR
Member
Posts: 113
Location: Marseille (F)
Contact:

quicklink behavior

Unread post by XpiR » 06 Feb 2026, 11:33

Hello

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)
You do not have the required permissions to view the files attached to this post.

User avatar
oli_lab
Member
Posts: 1286
Location: Brittany, France
Contact:

Unread post by oli_lab » 10 Feb 2026, 15:17

Hi !
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
You do not have the required permissions to view the files attached to this post.
http://oli-lab.org

Win11 Ryzen9/32GB RAM - RME MADIFACE - SSL alpha link 4-16 - OSC capable interfaces

follow OLI_LAB adventures on Mastodon
@olivar_premier@mastodon.social

XpiR
Member
Posts: 113
Location: Marseille (F)
Contact:

Unread post by XpiR » 14 Feb 2026, 20:52

Thanks Oli for your explaination.
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.

Post Reply