Hey! Remember me? I’m still enjoying the JUCE, though on Linux now a days. (Transitioning development to Linux turns out to be a piece of cake, much thanks to JUCE. GCC error messages could be less cryptic though)
I’m writing an app that will render audio in real time, much like a modest virtual studio.
So I have a gui component tree in the regular Juce style, and I’m thinking I should put the audio rendering in a thread of it’s own and up it’s priority a little. So far so good, but how do I best send data back and forth between the threads?
My current thought is to make a singleton data manager that collects the stuff from the gui and have the audio thread lock it once per buffer cycle or so, and copy the data into local vars for use in the DSP processes.
But I’ve never done anything like this before so I’d like to hear what others make of this before I start banging out the code.