I get this all the time. It's a real problem, because in a longer score it usually means the first half of the score has had all its notes changed to a new reference pitch and the second half hasn't, and there's no way back from that but to reload the piece.
I have a "JInext" abstraction I made, which takes a bang or a next message, and finds the next $1 scalar in pd-score. Because I have a vertical line on each beat, and octave marking lines, and tempo markers, plus notes, it has to skip past a lot of other templates. I put an internal delay in it, so that every 10 times it goes, it waits 10 ms. I've adjusted this to be slower and slower as I've written longer scores, but I still get stack overflow from the "next" message that retriggers it.
Can anyone explain more about what exactly "stack overflow" is? Might it help if I just put a 1 ms delay for each scalar?
Thanks. -Chuckk
-- "It is not when truth is dirty, but when it is shallow, that the lover of knowledge is reluctant to step into its waters." -Friedrich Nietzsche, "Thus Spoke Zarathustra"