You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mididings mentions the following about event order with a Fork connection:
Units are always called in the order they appear in a patch, using a “breadth-first” approach. For example, given the patch Fork([ Port('foo'), Port('bar') ]) >> Fork([ Channel(1), Channel(2) ])
Port('foo') will be called before Port('bar'), and the two events produced by the first Fork() are then passed on to the second Fork() individually. The four events resulting from this patch are thus emitted in the order ‘foo 1’, ‘foo 2’, ‘bar 1’, ‘bar 2’.
It would be good if RMididings has the same behaviour.
The text was updated successfully, but these errors were encountered:
Mididings mentions the following about event order with a
Fork
connection:It would be good if RMididings has the same behaviour.
The text was updated successfully, but these errors were encountered: