Who would have thought!
All kidding aside, I've made a patch that can tell which chord is most likely to come up, to be used in my jam-machine.
It looks at incoming notes and tries to recognize a repeating pattern in it.
When it does, it outputs the chord that was next in the last repetition.
It's functioning, but causes dropouts, even though the CPU-usage is below 2%.
The part that is at fault is a nested until loop.
I thought that 'until' spits out the next bang as soon as the "depth first" branch is completed, but no sooner.
Is this true?
If so, a until (even a nested one) couldn't cause a dropout as long as it doesn't tax the CPU too much, right?
I'm at a loss here. If someone could please have a look, the troublesome part is in MIDIchordImpro.pd->ChordProgresionChecker->Compare
Thank a lot!!!
PS: the patch is in alpha state, so don't expect too much of it. Also, some sub-patches are messy, though I've cleaned up the one that is giving me grief.