We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I just noticed that you schedule MIDI messages on the tempo clock:
TidalVST/TidalVST.scd
Lines 91 to 97 in a625ad6
For accurate timing, the MIDI messages should be scheduled as OSC bundles instead. For example:
~dirt.server.makeBundle(latency, { instruments[vstName].midi.noteOn(0, note, velocity); }); ~dirt.server.makeBundle(sustain + latency, { instruments[vstName].midi.noteOff(0, note, velocity); });
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I just noticed that you schedule MIDI messages on the tempo clock:
TidalVST/TidalVST.scd
Lines 91 to 97 in a625ad6
For accurate timing, the MIDI messages should be scheduled as OSC bundles instead. For example:
The text was updated successfully, but these errors were encountered: