I’m building a standalone which simply routes packetized midi from localhost UDP to midi ports.
The data traffic is handled in Threads which I assume I can set a higher priority (though performance seems good without changing the default).
Now I want to add indicators and visualizers of the traffic data without impacting on the timing of the midi events or unduly adding CPU load affecting the concurrent DAW app.
I suppose that sending data coming out of the “data traffic” Thread to a queue which is read by components in the main window for display would achieve this. How would I ensure that the graphic and GUI parts of the app have minimal impact on time critical CPU resources of the PC?