Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verify Fork event order #4

Open
wvengen opened this issue Jun 27, 2021 · 0 comments
Open

Verify Fork event order #4

wvengen opened this issue Jun 27, 2021 · 0 comments

Comments

@wvengen
Copy link
Owner

wvengen commented Jun 27, 2021

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant