zynaddsubfx

ZynAddSubFX open source synthesizer
Log | Files | Refs | Submodules | LICENSE

commit 59abef3bd13487a772bca9f2ebe51bb60126c2be
parent 420f5167ffdda7e1f5363bb5c2ed3dfe5587eea6
Author: Johannes Lorenz <johannes89@ist-einmalig.de>
Date:   Tue,  7 Nov 2017 18:55:25 +0100

Fix rtosc merge

Diffstat:
MTODO.txt | 2++
Mdoc/architecture.txt | 12++++++------
2 files changed, 8 insertions(+), 6 deletions(-)

diff --git a/TODO.txt b/TODO.txt @@ -1,6 +1,8 @@ TODOs for default values: * iterate correctly over arrays * use b (or #?) for bundles, not a +* code for random port ("init() to random") +* remove rDefaultMissing if possible move code: ports.cpp => default_values.cpp rtosc.cpp => ...cmp.cpp? diff --git a/doc/architecture.txt b/doc/architecture.txt @@ -76,7 +76,7 @@ Synthesis Objects:: Objects which initialize with parameter objects and generate output audio or control values for other synthesis objects Container Objects:: - Objects which are responsible for organizing a variety of synthesis and + Objects which are responsible for organizing a dvariety of synthesis and parameter objects and for routing the outputs of each child object to the right destination (e.g. 'Part' and 'Master') Hybrid Objects:: @@ -133,15 +133,15 @@ There simply isn't an effective means of capturing all parameters without taking a large amount of time. The master has two kinds of parameter objects: - - Realtime variables which are only ever mutable through the RT thread - - Non realtime variables which are only ever mutable through + - Realtime parameters which are only ever mutable through + * OSC dispatch within Master + - Non realtime parameters which are only ever mutable through * OSC dispatch within Master * MiddleWare (using struct NonRtObjStore) Now, in order to permit the serialization of parameter objects, the backend is -partially 'frozen'. 'Partially' means that only the non realtime variables are -ever being saved. Since the freezing message is the last one the MiddleWare +'frozen': Since the freezing message is the last one the MiddleWare sends, this essentially prevents the backend from processing further messages -from the user interface and when this occurs the parameters which are to be +from the user interface. When this occurs the parameters which are to be serialized can be guaranteed to be constant and thus safe to access across threads.