I think there is a time-out or a RAM-overflow. If you see that pedalboard and if you compare how long it takes to render a sinpler one, I guess this one takes too much ressources.
It was working last week with a bit heavier setup, and it is the same result if I give some room to the CPU by setting the buffer to 256… it is something else no ?
Hard to say but I’d guess that it runs a virtual browser and loads the pedalboard in order to capture screenshots. Some combination of maxing out CPU / RAM is likely happening with the additional load. Can you get the load down by disabling a bunch of stuff and then Save?
Alternatively, if you’re comfortable with using command line tools you can make your own screenshot and add it to the pedalboard data: Pedalboard file layout
sorry i don’t have any brilliant solution… just confirming that i got your pedalboard loaded, and the share utility is behaving exactly the same way for me as well.
i’ve had boards with similar complexity, which have taken a very long time to generate the screenshot, but have succeeded in the end. in those cases, i never saw the Generating for screenshot… (final attempt) message.
