ha, yes i see the ambiguity in the question, apologies. my main interest, which was answered, was about the threshold of failure.
we're dealing with what should be considered a pretty small processor (66mhz). it's difficult to define the boundaries given the various ways you could possibly overrun the system. i've already made a sort of definition by not allowing the metro clock to go below 10ms. but there are certainly ways to bog the system. there are ways to bog any digital processing system. but unfortunately this takes time to learn-- ie, super long loops, fast metro, all 8 inputs firing scripts with extreme speed, script recursion. it's much different than the common understanding of "too many plugins in my daw" but i think you're correct-- we should put together some suggestions for ways to bog your TT (and hence, avoid them)
that said, the issue reported is not related to processing power, luckily. it seems like an interrupt priority issue.
@sam @bpcmusic @scanner_darkly
what do you think about scripts getting executed within the event loop? so metro and trigger inputs would simply queue a script event? it would quantize script execution to a 1ms clock (which i don't see as a problem), but would certainly prevent any collisions (ie, a trigger firing a script while a metro script is mid-execution, which i think might be possible at this point-- not having looked at the code).