View Single Post
Old 02-06-2016, 03:11 PM   #2
Human being with feelings
Join Date: Feb 2016
Posts: 138
Default OSCII-bot timing insight

The thread ordering and sequence was gradually determined by using diagnostic debug printf() output to the OSCII-bot console log and by logging precise times using the time_precise() function call in the debug log.

The @midimsg and @oscmsg sections seem completely exclusive of one another and run on the same thread. Only one or the other runs at any one time making global variables thread safe within a script.

OSCII-bot coders relying on time and sequencing should note that in the standard console messages like this

TIME: 531.917 [OSC input] /fxparam/11/name [s] 1: Volume

that "TIME" here uses a less precise time stamp that does not always increment with wall clock time.
goldenarpharazon is offline   Reply With Quote