Why do the parameters for the sequencer have to be
*process* variables?�� Why can't they be instance
variables of an object?

SequenceControl (mutex v1 v2 ...)
�� initialize
������ mutex := Mutex new.
������ v1 := default for v1.
������ v2 := default for v2.
������ ...
�� v1
������ ^v1
�� v1: x
���� validate x all by itself
���� mutex critical: [
�������� validate x in context of other variables
�������� v1 := x].

This takes care of all the memory fiddling necessary.
Once again, the existence of this object would be a shared
secret between the process and the creating process.


On Wed, 3 Mar 2021 at 00:48, <mspgate@gmail.com> wrote:

thanks Sven and thanks Richard.

I already thought it was not a good idea to change a variable inside the process as for OOP principles.

but I dint find any solution to do what I want to do, that is a tool for live coding in which the process variables are values for a sequencer sendin OSC messages to another application. I need the process for the timing.

what I had in mind came from the fact that in c++ frameworks to build audio application you can modify variable values inside a thread.

after your answers I think I will have to look for another approach.