Hi Nycholas,
I haven't personally experiemented with this type of configuration, but the UDP-based approach is applicable in theory. The low-level building blocks needed are dsp.UDPSender and dsp.UDPReceiver, and the example that you linked should indeed put you on the right track.
From a practical standpoint though, your specific design idea may have other challenges. You will have to pay attention to things like:
- Sending UDP messages needs knowledge of a given receiving port, or otherwise needs working in broadcasting mode
- You may need plugins with different roles to use different local ports
- You may find it hard for a plugin to discover other running instances of the same type or to configure themselves for a given master/slave role automatically
In summary, my suggestion would be to start small (e.g. create two separate plugins with different pre-configured roles) and to try to grow the complexity incrementally only once you understand all relevant implications.
One important piece to remember - when you generate the VST plugin from MATLAB, any UDP communication will depend on a shared library under matlabroot\bin (see for example the documentation page How To Run a Generated Executable Outside Matlab ). Υou should ensure that folder is on the path before firing up your DAW.
For example, I use the following .bat file to open REAPER in Windows:
set PATH=C:\MATLAB\R2018a\bin\win64;%PATH%
"C:\Program Files\REAPER (x64)\reaper"
Good luck,
Gabriele.
