Posted
Kind of excited by this so I thought I'd share.
I've used the juce framework to build a tag based VST3 OSC server which uses tags to direct which VSTs and channel combinations should play the sounds.
Sounds are sent from Synfire via the OSC client, thereby bypassing midi. The midi data (notes and controllers) are sent in an OSC message to the OSC server together with the tags which tell the server which VST3i's should play the notes.
Works well with Synfire.
So., 27.10.2024 - 10:26 Permalink
External hardware processes incoming MIDI immediately. A plug-in or host can't. MIDI data is processed along with audio in blocks. For messages sent in real-time there is a noticeable delay depending on the block size. A host or plug-in can add a message only to the next block (the current one has already departed).
That's why Synfire sends time-stamped data ahead of time.
If you keep the Juce host's block size small, the delay will not matter much. You will still notice it with drums and percussive instruments though.
So., 27.10.2024 - 13:54 Permalink
The latency will be there but the same as if I was playing in using a USB midi controller. For super tight timing, I would be taking the midi export into Presonus Studio and recording offline. However, for prototyping/previewing I’m thinking this set up could work ok?