There is no other host on the market which submits random(?) blocksizes to the plugins for rendering. It results in CPU spikes which cause crackles. There are also many plugins which make problems wothout this setting.
Why isn't 'use fixes size buffers' enabled by default?
Why does FL not behave like other hosts?
Why do my support requests get ignored?
Will you ever fix 'use fixed size buffers'?
-
- KVRist
- 259 posts since 16 Jun, 2015
Variable sized buffers are part of the VST standard and most plugins don't have a problem with that -- only certain plugins which fail to correctly implement the VST spec are affected, and that's why FL offers the workaround. The fact that FL uses variable sized buffers is part of why it has the tightest timing of any DAW on the market. So switching the entire DAW to work with fixed sized buffers to accommodate bugged plugins is, at the very least, a bit unreasonable.
Makin' Music Great Again 
-
- KVRist
- Topic Starter
- 179 posts since 29 Nov, 2012 from My home is my castle
It is bad practise. All other hosts work in a different way. The fastest possible timing is defined by the soundcard's blocksize. Usually this is a multiple of 2. Common sizese are 128, 256, 512 or 1024 samples.
FL studio requests weird sizese like 31, 738, 1, 63.
This does not work well with the CPU cache. On very small sizes like 1 there is a lot of overhead for the context switch.
The behaviour of FL Studio is bad Software design
FL studio requests weird sizese like 31, 738, 1, 63.
This does not work well with the CPU cache. On very small sizes like 1 there is a lot of overhead for the context switch.
The behaviour of FL Studio is bad Software design
