3 Nov
2011
3 Nov
'11
2:39 p.m.
On Thu, Nov 3, 2011 at 9:22 AM, Harry van Haaren <harryhaaren(a)gmail.com> wrote:
On Wed, Nov 2, 2011 at 5:09 PM, Iain Duncan
<iainduncanlists(a)gmail.com>
wrote:
no, using a protocol like OSC doesn't solve the basic problem: making
changes to data structures used by the RT code when those changes
can't be done with RT constraints (e.g. memory allocation). you still
need some code that runs outside RT constraints to modify the data
before giving the new version to the RT code to use.
--p
I'm hoping to arrive at some sort of design that ultimately lets the
engine act as an audio server with multiple user interface clients, possibly
not even on the same machines
Did you concider using OSC as an "abstraction layer" between your GUI &
Engine? Spares quite a lot of nasty shared-mem tricks, and RCU, well.. is
suppose you could have the editing commands sent to engine, or else run the
algo on the GUI side, and update the sequence in the engine.