thx.. i was just about to ask why Live is reporting 16 sample latency and Bitwig is reporting 0 for Hive. so turned it off for LiveUrs wrote:Here's what base Latency is about:
"If your host automatically sets the buffer size to a multiple of 16 samples, you can safely disable Hive’s own base latency setting here. If in doubt, leave at ‘16 samples’."
If you turn "use fixed buffer size" off in FL, there's going to be irregular buffer sizes such as 1 or 37. Those are not a multiple of 16, and thus you shouldn't switch Base Latency off. If you do you'll get crackles and distortion. I guess we should add that info to the user guide
I'd always recommend to keep a fixed buffer size for our stuff, but it still depends on the host if that fixed buffer size is a multiple of 16. Ableton Live for instance gives us an irregular buffer on a loop end no matter what, thus the option shoudln't be used in Live. It's a pity. Other hosts such as Logic keep going normally on a loop, there's no issue at all.
The sound differences are related to very fast modulations e.g. through the modmatrix. The update rate of the modmatrix depends on the overall size of the buffer as well, at least to some degree. A series of very short buffers will lead to a slightly higher resolution in modulations, which makes an audible difference on modulations that are nearly audio rate. It however also means more CPU. As a reference, we developed ACE and Bazille specifically to tackle audio rate modulation. Hive is flexible enough to get into that territory, but for it's CPU usage one shouldn't expect the same results as with ACE or Bazille.
but how do you tell if the host automatically sets buffer size to multiple of 16?