8 step sequence to leds via midi clock

[ssp]

Im making a arturia mini filter replica controller and it has an 8 step sequencer that steps through 8 leds. this is switched by an 8 way rotary switch (STEPS) that has a value defined map.

The rotary switch defines the steps as the plugin does so if switched to 3 then only 3 steps are active and only the first 3 leds step 1-3.

If i were to use midi clock for this is it possible?,  so the midi clock is forwarded to drive the 8 leds but they are defined by the rotary switch 1 through to 8 leds in use for the steps

 

so in effect the midi clock is always sent to the leds but the ones lit up at any time are set by the steps rotary switch.

I have everything else working, Maps, Range values and radio buttons, the steps knob works fine using my 8 position single pole rotary switch, and i am reading up on midi clock code at the moment.

 

thanks

 

 

 

[ssp]

With some advice from antichambre I have taken a look at the github: https://github.com/midibox/mios32/blob/feature/usb_hid/modules/sequencer/seq_bpm.h

i noticed that it has the ability to accept bpm clock and be "clocked"

However this is not an .ngc file and I suck big time at C' in any form.

I have got the handle on most of the .ngc format now and would like to somehow make this work in there.

i understand that there are 24 pulse per quater note so anything slaved knows a quater has passed after 24ppqn. sending 0xF8  24 times.

So if each led has a sysex recieve of 0xF8 x 24 then the 25th steps to the next led etc would that work?

This is a whole new thing to learn but I am game to try it out.

[ssp]

looking here as well

MIOS32 Tutorial #017: A simple Sequencer

Sequencer --------- The BPM generator can be used in MIDI Clock Master and Slave mode with a definable resolution, which can optionally be (much) higher than the common MIDI clock resolution. It it configured for Auto mode, which means, that it will generate an internal clock by default (Master), and synchronize to an extern clock once the appr. MIDI clock events are received (Slave). In slave mode, the incoming clock is multiplied depending on the defined PPQN (pulses per quarter note). The MIDI event scheduler queues MIDI events which should be played at a given MIDI clock tick. The approach has the big advantage, that events can be pre-generated, eg. to bridge the time while loading new pattern(s) from a SD Card, or to generate effects like MIDI Echo (very simple, just put the note multiple times into the queue with different bpm_tick values). The advantage of using the MIDI clock as time base instead of an absolute time is, that the sequencer is even in synch if the tempo is changed while unplayed events are in the queue.   This here "The MIDI event scheduler queues MIDI events which should be played at a given MIDI clock tick" makes me think that this is the way to go. So now i gotta start learning C'???... lol

 

 

And i am also looking at the arpeggiator tutorials, this is all way over my head but i am reading through things, if anyone has anything else i should think of looking at let me know.

 

Edited February 10, 2020 by ssp