when I am in a proxyspace environment at times supercollider becomes unstable with Pbind, displaying the Post window message late 0.031814147.
My machine is a Mac Sonoma 14.2.1, my Focusrite Scarlett 2I2 audio interface, and Sc v 3.13.0. Can anyone explain the reason for the problem and if there is anything that can be done to stop it happening as infrequently as possible? I’m going to do a Live Coding next month and I’m worried about it. Of course CPU usage doesn’t seem to be the problem since it happens with 30% usage.about it. Of course the CPU usage doesn’t seem to be the problem since it happens with 30% of the time.
What is your s.latency setting? It should be, oh, 2 or 3 times larger at minimum than hardware driver latency. Not sure if Mac reports this at server boot (Linux does).
If s.latency is too small, then “late” warnings will happen more often.
if the latency of my daw with a scarlet focusrite 2i2 is 6.0 ms output, and the one of supercollider is 0.2 (s.latency), how much latency should Sc have to work properly? it seems that they do not work with the same units.
On my setup (OSX 13) I can’t go lower than about 0.030 (30 ms) for the latency parameter without getting late messages and other weird stuff. I often choose to set s.latency = nil, which does introduce some jitter, but is it not that bad…or maybe I just like the ‘humanzied’ grid, e.g. the small differences in delta time as a result of the jitter.