@samaaron I am so sorry!!
My computer is old, - and my sonic pi code became too complex for it. This is 90% of the problem right there, on my (pc hardware) side. Imagine a non-professional, cheap midi setup ontop of that. The issue was getting it in sync with hardware sequencer. This issue did not feel like a sonic pi problem - more like a hardware/software/interface-problem in general with lag and so on… sonic Pi is awesome! But old pc with code too complex and jitter = not the masterclock I wanted it to be.
I tried a simple setup / experiment before I kinda gave up on that idea (because I needed another more stable solution):
Korg Monologue got a built-in 16 step sequencer. In theory - When a note hits - the sequencer starts to step thru the 16-step sequence / or restart/transpose it, when it’s already running. So, I wanted Sonic Pi to send a random note at step 1. to just hit on step 1. I was not able to to this in sync with sonic pi serving the clock. reliably. without adjusting delays and so on… The flashy step sequencer on the monologue would show jerky motion and/or overstep a lot. Got similar experiences with other hardware, especially chea midiinterfaces (?) and volcas. but will test that for sure again - with other midi interfaces, just to get an update on that issue for myself - and so I dont spread mis-information about sonic Pi!
It kinda worked. But was not ‘reliable’ as the clock. And thats more of a general PC-problem, than a specific sonic pi problem. I would expect every other midi program / daw to give similar experiences on similar hardware.
SonicPi is like a swiss knife: It reads and does everything i want, when want it. Its like the hidden dagger to stab somone with. But I needed a rock to lean on. And my PC was not able to deliver.