tulamide wrote:Do yourselves a favour and don't fool around with program threads, especially when the tool provided is in R&D, and you don't know about the topic behind the tool.
Threads
Can't contribute to the topic of actual "threads" but I have some newbie contemplations about timers...
It's enough frustrating to work with just regular delayed triggers using timers (within what I guess could be said to be the "main green thread"
)
Not having any control of underlying code... and creating actual new threads, and any asynchronous behaviour that follows feels like an awesome way to crash FS
Threads would seem to make more sense when not using somewhat of a "blackbox" environment like FS is?
I still don't understand if Ruby runs in same thread as green (by FS itself, that is).
I'm working very little with FS4... so I don't know If there is any way to accomplish it... but I do "sort of" miss a listener system in FS3.08... like a system with some predetermined flags that FS can raise when finished with updating poly or other hardcoded things, that then can be used to create consecutive triggers in green.
In general... regarding regular timers... The more timers I have the more issues I get in my synth
so I'm always trying to get rid of any. But I do have some left.
Mostly for two purposes...
To make sure an inital trigger propagates throughout the schematic and force FS to do that update.
And... also for creating what in the analog world would be the "knob" equivalent of a "button bounce protection" (I don't know the english translation) to reduce update frequency. For example when a condition is only met intermittently and any update only should occur when condition is met within a given timeframe.
I'm dealing with well over 600 poly selectors, probably much much more... switching on preset changes and when resetting these in my synth. The amount of green selectors/multiplexer and other spaghetti I've lost track of completely
Btw Tulamide...
Indirectly related to triggers. I'm in the progress of moving to using string presets parameters in my synth
and getting my switching/resetting system to work was a nightmare
I almost threw my laptop out the window several times.
The trick became to retain values correctly. Simple S&H prim logic alone didn't do the job. But I think I got it to work now, using unnecessarily elaborate trigger switch logic LOL
Unfortunately changing presets takes even longer than before string presets. But that's fine...