pascalargon

Been really scratching the old noggin on this one and would appreciate some puzzlemasters to chime in.

I have a [counter] logging the number of notes being played in an incoming midi file. I need this number in the [counter] to reset every 7, then every 4, then every 8 notes played.

I made an additional midi file that only plays every 7th (...4th ... 8th) note and used that to reset it, but somehow there's latency that I can't fix with [delay]; the first counter sometimes over-counts, sometimes under-counts, even though the two files are perfectly synced.

What I'm looking for ideally is a way to write in an algorithm of some kind to get the [counter] to behave under certain conditions without using any other external midi signals. In a perfect world, these conditions would extend past the three numbers to any arbitrary sequence of numbers programmed in (reset at 7, 4, 8, then 5, 2, 6 ....)

Hi all,
Been really scratching the old noggin on this one and would appreciate some puzzlemasters to chime in.
I have a [counter] logging the number of notes being played in an incoming midi file. I need this number in the [counter] to reset every 7, then every 4, then every 8 notes played.
I made an additional midi file that only plays every 7th (...4th ... 8th) note and used that to reset it, but somehow there's latency that I can't fix with [delay]; the first counter sometimes over-counts, sometimes under-counts, even though the two files are perfectly synced.
What I'm looking for ideally is a way to write in an algorithm of some kind to get the [counter] to behave under certain conditions without using any other external midi signals. In a perfect world, these conditions would extend past the three numbers to any arbitrary sequence of numbers programmed in (reset at 7, 4, 8, then 5, 2, 6 ....)

counter-reset-algorithm

What you're looking for is a form of "metasequencing", in that you want to change the state following a sequence (7,4,8,5,2,6 etc), and you want to step through this sequence every time your other sequence reaches that point. So sequencing with a sequencer.

Simplest method is for sequencing is [counter], of course, but you've been attempting to get a single counter to behave in a way that requires two counters, which I don't think is possible.

Here is a method that does a county-bit, in the manner that I think you're describing.

The [metro] represents your midinotes coming in, and the count can be changed by changing the [zl lookup] array.

What you're looking for is a form of "metasequencing", in that you want to change the state following a sequence (7,4,8,5,2,6 etc), and you want to step through this sequence every time your other sequence reaches that point. So sequencing with a sequencer. 

Here is a method that does a county-bit, in the manner that I think you're describing.
The [metro] represents your midinotes coming in, and the count can be changed by changing the [zl lookup] array.


Oh my god, this is perfect. Thanks so much, wow !!!!

just stumbling into this thread to say thank you for this concept.

[counter] reset algorithm (?)