so, after watching this issue for a while now, i’m coming to the conclusion that it’s really not about beta versus non-beta plugins. (although there is great variability in the xrun behaviour of various beta plugins – choose wisely because some are fine and some are not – lots of testing of any particular pedalboard before it sees the stage or studio is key!)
i’m now pretty convinced that the only way i can entirely avoid this problem is to keep the pedalboard load under 75% at 128 frames only. it seems that if a pedalboard is complex enough that i have to drop to 256 frames in order to keep the load under 75%, there will inevitably be some xruns if i just wait long enough.
unfortunately, it’s a difficult problem to test rigorously, with various combinations of plugins. a lot of what i’ve been building up 'til now has required 256 frames, so i’m going to be examining whether it will work for me to simplify things, and make more use of pedalboard banks to switch setups during a performance.
given the processing power that’s been demonstrated on the Duo X, i’ll also be eagerly watching for any news of CPU upgrade options for the Duo!