I want to implement a stand-alone variant of http://www.maxforlive.com/library/device.php?id=196
What I want to achieve: I want to select quantize grid, feed clock to the core and play live, but with getting quantised output.
Has something like this been done? What’s the best approach? I was thinking of using the NoteStack from MBSEQv4 and pushing/popping notes on the notestack
based on midi clock.
just a few thoughts… not a full programm or even right, anyway it has to morph to a running programm by doin it… i do not - so just a few ideas…
no not done… but i am in a bit in note processing… and have programmed my own note processing devices (with built in sequencer based on MIOS stuff)
so the note stream is getting delayed? to the next tic? maybe not, so to the next beat? but what is the next beat? the source material can be 3/4, 4/4, 5/4, 7/4, 9/4, 11/4 13/4,
so you have to set the counter in your device to the Beat-Structure, of course only when the currently played beat is finished, you could do that with programchange or controll change from your seqencer (ableton?) clips cc function… but that change will then only happen to the next beat (if it is above… for example a currently played 4/4 @ step 15 has to be finished before a 13/4 can be set…
i would run the seq.c and set the tact counter via control change, for ammount i would simply solder a pot to j5A, trippled mode = tact system 3/4
the sequencer tic output + the number generator/counter i would send to a function in main.c where the “buffer arrays = notestacks” are getting triggered.
the buffers itself i would fill in the midi-notify function.
and then your brain has to work…
if you delay a 32the length note-on-message to the next 4/4 beat, and 32th later you delay the note-off-message to the same next 4/4 beat, your probably hear nothing
so you have to counter the tics off the note-on-note-off time,
and then my brain stop getting a clue… you will need a “input buffer” and a “waiting buffer”…
so the easyest way is maybe to make a trigger-function that handles all 127 notes for a channel(hi priority) l, and have a second function that handles note off calculation (which is not hi priority) and dump out note offs - a frtos xtag which is called every ms for example,
the note on off tic time calculation i would do with a flag set in the midi notification function, the flag counter itself is in the trigger function which itself is drivcen from the seq.c? tic sending…
the calculated note off tic time then will be written into the note off buffer - or start the the second function which handles note off calculation (counter every millisecond…)
what should be the interface? programchange/cc + that controlls like on maxforlive? well the hardware will be the easy job…
michi
Audio Commander’s AC Sensorizer on the PIC18f quantizes incoming notes and note-timing based on the internal or external midi clock:
harmonizer with 20 scales (minor, major, blues, spanish…) ? harmonizes generated or received (by MIDI!) note-signals
syncronizer: master/slave mode (autodetect clock input switches to slave) and selectable BPM
quantized events: 1/2/3/4/6/8/12/16/24/32/48, selectable per sensor
http://www.midibox.org/dokuwiki/doku.php?id=acsensorizer_04
Although this was made primarily to read and interpret incoming analog voltage signals via an AIN module, it’s great for midi too.
If you’re interested, I have version 0.5 which isn’t listed on that page.
On 20-3-2018 at 8:48 AM, sneakthief said:
If you’re interested, I have version 0.5 which isn’t listed on that page.
Hi Sneakthief,
I’m interested in 0.5. I bought one here on the forum, and put a lot of effort in it to get it working with the latest release back then. But I loved it, great application, I have to dig it up, but this seems a good reason. What’s with 0.5?
Cheers, Roel
Hi Roel, check your PM’s from 5 years ago - we had this whole discussion and I helped you setup your compiling environment to get 0.5 up and running 
Right, now I know! that was the hassle, and I 've all in my archives. Thanx again!