Controle Rate in A Signal Rate System
Hi,
I'm working on a architecture between control-rate logic (Markov / prob) and signal-rate timing (phasor~).
My goal is:
A continuous masterphasor acts as the only time source.
I want to divide this phase into N segments (e.g. 4 ).
A Markov /
probsystem (control rate) outputs discrete states (e.g. 1–4).Depending on the current state, exactly one segment of the phase should be active (e.g. as a gate or trigger source).
Crucially: all timing should remain sample-accurate in the signal domain (no event-based timing).
My current approach was:
Using
subdiv~and taking the index from its right outletComparing that index with the
proboutput using==~
However, the right outlet of subdiv~ is control-rate, which effectively means I'm doing:
signal → control → back to signal, which i red in the forum many times seems not a good idea right?
This feels conceptually wrong, since it reintroduces scheduler timing into what should be a purely signal-driven system.
So my questions is:
How can I derive discrete segment indices (e.g. 0–3) directly from a phasor~, entirely in the signal domain whilst using weighted propability transitions generated in the controle rate domain (prob) ?
Thx!!!
Example patch:

here keeping signal to what
sick! got it! thx! just out of interest - would there be a scenario where the controlerate index of subdiv will miss the gate that round produces for it (bigger patch, lots of ui, controlerate jitter e.g.)? or is this nothing to worry about?
there are a lot of theoretical "issues" with switching domains, but if you do it and something works like it should, a higher overall processor load should not change anything about that. everything in the signal domain and everything in the scheduler domain always follows the same "ruleset" - until you run out of processor cycles.
hi roman makes sense - i got a non theoretical issue now ^^ i want to achieve some master phasor based accents and it works just perfect when working in signal domain, but the controle rate translation (signal mult to velocity) causes that my midi triggers are missing the accentuated hits.
now the weird thing is, when i have the pattern 1 0 0 0 in subdiv, the thing works perfectly with my midi translation. it is only when i have patterns like 1 1 0 0 where it starts to glitch out.
like i mentioned, everything works completly fine with signals though.
