Ok, seeing this thread pop up I’m gunna jump in as I have a related issue I’ve been trying to work through for a bit.
I’m running sc alongside Bitwig Studio. BWS currently set at 512 sample buffer. When both are idle running concurrently I get regular peaks in my cpu usage causing dropouts (see upload). BW on it’s own is fine (although my set is quite heavy). SC on its own doesn’t use much CPU or ran, and this happens just with the server running.
I’m pretty ignorant of what’s going on at a low level, but my thinking there’s a CPU allocation issue where supercollider and bitwig are competing for the same chunk of cpu time which isn’t enough.
To fix this, I have set s.options.hardwareBufferSize = 2048;
With this setting the peaks are still there but lower and I can perform without dropouts. Am I doing something destructive to the signal in by having hardware buffers that don’t match, or am I just adding latency to supercollider?
Checking my parse => the setting refers to sc buffers for the hardware, not my mac’s buffer for the hardware…
This really isn’t ideal, but seems just about manageable for now (I’m processing audio for control not fx).
Is there something I’ve missed or any other config that might be able to ease my issue?