midi mergers/patch bays are passive…
Im not… and I suspect most tempo based sequencer works this way.
if you just passed the clock thru (when using midi out+thru/midi out)
then when the pyramid generated messages off its ‘grid’, these messages would be slightly off that clock.
instead, its syncronising its (internal) clock to the external one, and outputs this… so its grid is nicely aligned.
also this has the advantage, that the pyramid can smooth out the (inevitable) jitter that occurs with midi clock messages - so hopefully put out a slighly more stable clock. (*)
thats not to say, it couldn’t be made to work by passing thru the clock (and not output your internal clock), but I suspect it would just create a different set of problems…
(*) i think this is esp. the case, if your slaving to a DAW, where the OS introduces a certain amount of jitter if your using usb midi.
I agree, Ive always had a great response from them when Ive reached out- this is I why recommend users reach out via the contact form… Squarp can then contact you to really understand what it is you need, and also how they might be able to help… what is ‘feasible’ give the codebase and resources etc.