I'm gonna write me a synth.
(well, tweak existing synth code for my own nefarious purposes)
I already have a midi sequencer app. (that edits notes and such)
And I'd like the synth to be a seperate .exe since it's a different sort of beast and would be nice to have runnin on another core, etc.
So now i gotta come up with the best way to send midi bytes
(and load c:\THISpiano.patch messages, etc, etc)
from the sequencer .exe to the synth .exe
I guess memory mapped files are the windows way, eh?
Sequencer app opens mem mapped file and writes to shared mem.
Synth app opens same mem mapped file and reads from shared mem.
Anybody got any other hi performance techniques for inter process talkin on windows - especially by a native c++ app?
thanks mucho!
...Steve
Actually, while I'm at it here, if I DO use mem mapped files,
is there a way for me to WAIT and not spin in a busy loop looking
constantly for any change in shared mem?
It'll be in a busy loop ANYway when there are ANY notes on.
But when things are silent (notes/voices are all off)
it could be nicer to the cpu.