Why FlowStone can't hard-sync with DAW?

[Nowhk]

I don't really know how to sync my DAW to FlowStone! In any way! Also using primitive modules that are made for that purpose. Here for example:

Lazy on Init.png (25.02 KiB) Viewed 10860 times

It's easy: when I start DAW, it should init the controller to 0, from whatever the value of my plug is, at t=0. Instead, it takes times to accomplish that (of course. digital introduce latendy, but where is buffering?).

If I record the automation (knob last value 1 before playing) I can clearly see the delay (communication between DAW and FS is slow):

Lazy on Init_2.png (6.58 KiB) Viewed 10860 times

This makes incongruity every time I play, because first part of processing have the value of the last played one (which can be different every time).

Why FS can't sync Host with itself? For every environment I'm working on there is always that "famous" inherit/init buffer that help to sync between host and plugin (a necessity for DSP).

Am I missing somethings or just FlowStone it is not a robust road for audio?

Lazy on Init.fsm

(335 Bytes) Downloaded 798 times

[Nubeat7]

you can use the "afterload" prim for initialising after starting the DAW, or the "init" methode in ruby..

the "is playing" primitive has nothing to do with wht happens when the DAW is loaded, it just reacts when play is set to on or off (stop)...

btw. i would recommend to dive a bit deeper into all the mechanisms of FS, FS is a complex programming language and you need to learn how to use it, not everything is readymade for your purposes...

and how things were already mentioned in other topics about your FL controller automations, the controller automation is send in "green" so it will never be sampleaccurate, these are very basic informations about FS and you really should understand these basic mechanisms of FS before walking a blind end road...

FS can be synced with the Host but this is done with stream ("blue" or "white" audiothread) which always have priority to the green GUIthread, these are common ways to handle GUI based Audioapplications..

[Nowhk]

you can use the "afterload" prim for initialising after starting the DAW, or the "init" methode in ruby..

But my problem is not to "init" data, but sync it with DAW during playing (which is different).

and how things were already mentioned in other threads about your FL controller automations, the controller automation is send in "green" so it will never be sampleaccurate

That's I know. But I don't need (here) to be sampleaccurate (its just a sort of boolean mechanism that need to react at a fixed time with DAW).

Of course it is not "readymade", and would be nice make my own schema to accomplish the task. But for what I see, if also the primitive for basic operations can't deal with DAW, I don't see how I could use for my purpose And that's sad, because I love it...

[Nubeat7]

But my problem is not to "init" data, but sync it with DAW during playing (which is different).

....But for what I see, if also the primitive for basic operations can't deal with DAW, I don't see how I could use for my purpose And that's sad, because I love it...

its always the same answer, as long as it is in green there will be no accurate changing of values also when its just a boolean... you nned to stay in blue or white or ruby (midi)..

[Nowhk]

you nned to stay in blue or white or ruby (midi)..

I just... can't FL Studio doesn't deal with MIDI for internal controller. That's why there's Controller prim. Since it's green, I guess I'll always suffer of these asynch problems than...