DSP Robotics Support

Ok so i have this problem:

- i made a an modulation system that it works using a ruby clocked timer... that basicly converts linear array data
into values at precise measures, meaning that i can modulate any parameter of knobs using this way...

it worked fine and i am very happy with it... but when experimenting this on actual DAW i have this anoying problem:

- when the interface of the plugin is open, it work perfectly... everything comes fine.
- when the inteface of the plugin is minimized or closed, the modulation doesnt work, everything else sounds fit
but the modulation doesnt work...

and i wonder if this isnt caused because ruby is suposed to be a "bitmap" coded tool mostly...

So i am wondering if in order to save resources the flowstone doesnt automaticly dissable ruby while the plugin is minimized or not showing in the display

and because of this, my system doesnt work like i wanted...

it works fine when the plugin is opened, its perfect, it doesnt fail the ticks... the calculations work...

Ruby simply seems to stop while the plugin is minimized, meaning the clock stops, meaning the calculations stop and the modulation doesnt happen...

i tryed the otherway around... going from stream to greendata, but i dont like it... and i cant do the things i want that way, streaming modulation is too limited, and i cant control the time, so i have to do all the timing in green data, and modulate the knobs from green data to green data... but ruby must work all the time, i cnat have ruby dissabled while the plugin is minimized otherwise it doesnt make sense...

if there is any type of way of making ruby working all the time even when the plugin is minimized i would apreciate information

Thank you.



[in order to make people try and understand what i am doing, i made an example of how it works...
if you export the vst version and try to use it on a DAW you will notice, that the modulation only works when the plugin window is opened, when its minimized or closed, the calculations or the ruby code, stops...]

OK I fixed this...

instead of using the Ruby tick counter... i made a timer using 100 ticks per second primitive...

i had to multiply the 100 tps primitive for x1.5686 because it was losing time against the ruby ticker...

the ruby ticker is acurate and faster

so i did a testing multiplying numbers till they match, and now they match... there may be a gap in 1000 ticks of
-1 or +1, but its fairly acurrate for what its meant

because basicly, this numbers will index the array of values that will modulate the knob parameters
this was the way i found to modelate stuff without streaming... i created an array from a linear shape form
and then used the timer to index the samples per rate... meaning for each bar there is a certain amount of samples

so.... this is a system where it loops while your playing the keyboard.. the modelation design in the graphical modulator... and then it index the data in the sample array, resulting in this type of modulation

Hola Ricciardo,
but why you not generate the clock in blue and then read the array data with a Float Array to Poly primitive?

Tronic wrote:Hola Ricciardo,
but why you not generate the clock in blue and then read the array data with a Float Array to Poly primitive?

i dont know how to do it... if you think that way is better and if you can adapt it to modulate knobs
using green data in the end, than ill be pleased to seen an example...

Ok, after to think i while, i tryed the other way, using the stream mono to float to trigger the time...
i find it more stable than using midi to trigger, besides, by triggering it by stream, its better because its possible
to use the release and decay times attached to the modulation timer...

so i think this is a step forward