Yep, just tested in a FL20 demo and had ~6ms delay using Edison to record On Play.

Looks like they might have fixed it

@BWSounds Yeah I thought it would be a thing that primarily affects bouncing. I'm not sure if there's really anything to be done, you could try talking to @Christoph-Hart but I'm pretty sure the issue is with FL, not HISE, and he only introduced that latency as some sort of safeguard.

How bad is the issue exactly? Are the plugins completely unusable in FL? Or is it managable / only affecting a small part of the workflow?

@Christoph-Hart Watching git like a hawk

@Natan Could you try this again? Or did this not work out?

@Natan What kind of node setup are you using? I brought mine down by a significant amount by adding a button that disables oversampling nodes.

For simple stuff like compression/filters/dry-wet chains and saturation, you should be able to bring the CPU usage down to reasonable and competitive amounts, not sure about more modulation-based stuff though.

@Natan I haven't done it, I exported them to meta nodes, which don't affect CPU and are also being deprecated.

@Tania-Ghosh Thanks for giving it a spin

@BWSounds Thanks for letting me know! I'll have to add some sort of warning to the store page... I like FL but it definitely has its issues.

I'm stupid, I didn't expect the oversampling nodes to have that much impact, I'll have to lower them to 4x...

I wonder what the ideal middle-ground is for anti-aliasing and performance. I assume 16x will have diminishing returns for aliased frequencies.

@Natan Exporting nodes to CPP is currently not working, but Christoph is working on it as part of a whole giant HISE 3.0