BrainModular

Gurulogic spoted someting i hadn't noticed previously, as i was using a very fast refresh rate as default.

It *looks* likes preset chunk datas are sent to user modules as if quantized on the set global graphic refresh rate speed , but not for 'normal' modules if im not wrong that are near instantaneous.

when i try on an empty otherwise scope but just trace a char 'ok' on the onSetChunk, the ok is displayed delayed, delay depending on the resfresh speed.

could it be set to react faster, independantly of resfresh rate? think it can create problems on recall if there are latencies on some modules and not on some others.

or maybe there is an issue somewhere else in my code causing this, let me now in case if thats not the current internal behaviour

Yes, you're right the chunk load is done in a background task with low priority.
this ensure that, when you load a big VST it has a lower impact on the audio process (avoid glitches).
moreover, some VST can open dialog windows which can totally block the messages queue.
the main drawback is that it is slower.

but unfortunately I'll not change it, the consequences could be dramatic.

yes totally make sense no problem .