latency

[cuchufo]

Any idea of how to measure the delay samples or latency introduced by an schematic?

[trogluddite]

Disclaimer: I am really a SynthMaker user, but the underlying principles should be the same for FlowCode.

Unless your schematic uses explicit delay lines in its design, the schematic itself won't add any extra latency over and above the latency inherent in whatever hardware you are using - the entire schematic is processed once over for every sample period with no extra software buffering. This is a nice knock-on effect of FlowStone being derived from SynthMaker, which has to work that way for its VST exports to work properly.

If you search the SynthMaker forum, you can find several examples of modules that can be used to 'Ping' a delay line to confirm the delay time (depending how the code is written, an extra sample of delay can sometimes creep in). Those modules should function equally well if you load the .osm files into FlowStone.

There's a nice thread here at KVR with suggestions for measuring the real-world latency of your hardware - simple calculations from the driver buffer sizes etc. can often be misleading, as they take no account of the hardware latency of Analogue-to-Digital conversion, USB ports etc.