late errors - any idea why?

[fuzzySi]

Hi Sam
Getting lots of 'LATE' errors all of a sudden. linux on an old laptop but performance is only 5-8%
Any ideas how to sort this?
Thanks, Si

[23:47:46.984.486] LATE: 8.7ms (count=318)
[23:47:49.822.834] LATE: 13.5ms (count=322)
[23:48:07.822.318] LATE: 17.6ms (count=325)
[23:48:10.853.740] LATE: 4.0ms (count=326)
[23:48:14.594.019] LATE: 8.4ms (count=327)
[23:48:15.771.781] LATE: 17.0ms (count=331)
[23:48:18.773.590] LATE: 3.5ms (count=334)

here's the start code

gui.log

[23:31:56.086] [supersonic] state: stopped -> booting (init)
[23:31:56.108] [piano] wavetable loaded: 586349 samples
[23:31:56.634] Available drivers: [ALSA] [JACK] [PipeWire]
[23:31:56.775] [device-setup] boot driver: 'PipeWire'
[23:31:57.799] -H 'Patchbay (16 ch)' -> PipeWire : Patchbay (16 ch)
[23:31:58.014] [supersonic] scsynth block size = 128 samples
[23:31:58.025] [supersonic] attaching audio callback to device 'Patchbay (16 ch)'
[23:31:58.025] [juce] resizing input accum: 4096 -> 18432 floats (perChanCap=1152 chans=16 hwBuf=1024 activeIn=16 mNumIn=16)
[23:31:58.025] [juce] output channels (16 total):
[23:31:58.025] [juce] [0] out_1 (active)
[23:31:58.025] [juce] [1] out_2 (active)
[23:31:58.025] [juce] [2] out_3 (active)
[23:31:58.025] [juce] [3] out_4 (active)
[23:31:58.025] [juce] [4] out_5 (active)
[23:31:58.025] [juce] [5] out_6 (active)
[23:31:58.025] [juce] [6] out_7 (active)
[23:31:58.025] [juce] [7] out_8 (active)
[23:31:58.025] [juce] [8] out_9 (active)
[23:31:58.025] [juce] [9] out_10 (active)
[23:31:58.025] [juce] [10] out_11 (active)
[23:31:58.025] [juce] [11] out_12 (active)
[23:31:58.025] [juce] [12] out_13 (active)
[23:31:58.025] [juce] [13] out_14 (active)
[23:31:58.025] [juce] [14] out_15 (active)
[23:31:58.025] [juce] [15] out_16 (active)
[23:31:58.025] [juce] aboutToStart: device='Patchbay (16 ch)' type='PipeWire' sr=48000 bs=1024 activeOut=16 activeIn=16 outLat=1024 inLat=1024
[23:31:58.025] [supersonic] audio callback attached — waiting for first tick
[23:31:58.042] [juce] first audio callback: numSamples=1024 out=16 in=16
[23:31:58.043] [synth] [juce] audio thread realtime: status=1 policy=1073741825 prio=83 err=1
[23:31:58.044] [supersonic] audio callbacks started (19 ms)
[23:31:58.044] [supersonic] state: booting -> running (boot)
[23:31:58.044]
[23:31:58.044] ░█▀▀░█░█░█▀█░█▀▀░█▀▄░█▀▀░█▀█░█▀█░▀█▀░█▀▀
[23:31:58.044] ░▀▀█░█░█░█▀▀░█▀▀░█▀▄░▀▀█░█░█░█░█░░█░░█░░
[23:31:58.044] ░▀▀▀░▀▀▀░▀░░░▀▀▀░▀░▀░▀▀▀░▀▀▀░▀░▀░▀▀▀░▀▀▀
[23:31:58.044]
[23:31:58.044] SuperSonic v0.71.0 (SuperCollider scsynth-compatible 3.14.1)
[23:31:58.044]
[23:31:58.044] Compiled: synth Link Link-Audio MIDI Gamepad
[23:31:58.044] Patchbay (16 ch) (PipeWire)
[23:31:58.044] 48000 Hz | block 128 | buffer 1024 | out 16 | in 16
[23:31:58.044] TCP port 29197 (max 16 connections)
[23:31:58.044]
[23:31:58.129] [synth] DRIFT: wall clock +102.8ms from audio timebase, re-converging (peak 102.8ms, 1 hits since last report, 1 total)

[fuzzySi]

putting with_fx loops outside live_loops has helped, didn't know that was a thing
I've also changed CPU to performance not powersaving
better now, still occasional lates but far fewer

[01:24:07.068.432] LATE: 12.1ms (count=1)
[01:24:44.571.138] LATE: 13.5ms (count=2)
[01:25:52.071.121] LATE: 7.4ms (count=3)
[01:25:59.569.624] LATE: 16.3ms (count=4)