AdmiralCrunch
Well-known member
Hi,
so now the point has come at which I have to deal with coding a sequencer for my project.
this has nothing to do with the thread-question but as I want the sequencer to be very feature rich, I ask myself if it will not be too much for the teensy.
I mean I use a T_3.6. but beside a ton of digital/analog-readings, the teensy needs to send the state permanenty to the Raspi (which acts as a display).
When I now add a sequencer for 16 tracks, each track with extensive functions, also this updates needs to be send to the Raspi.
Can one T_3.6. handle that all, or should I suggest to split it? .. maybe another teensy just for the sequencer?
so first things first, I thought I start with the midi-clock.
I searched and tried around, but I can't figure out how the midi-clock is working on teensy. Is there a good explanation, maybe with a working example out there?
I need to have:
- midi-clock-generator so my sequencer can run at some BPM-rate
- send the midiClock through MIDI-OUT, so other hardware or DAWs can sync
- teensy recieving midi-clock through MIDI-IN (teensy as clock-slave) and move through the pattern on each tick
so now the point has come at which I have to deal with coding a sequencer for my project.
this has nothing to do with the thread-question but as I want the sequencer to be very feature rich, I ask myself if it will not be too much for the teensy.
I mean I use a T_3.6. but beside a ton of digital/analog-readings, the teensy needs to send the state permanenty to the Raspi (which acts as a display).
When I now add a sequencer for 16 tracks, each track with extensive functions, also this updates needs to be send to the Raspi.
Can one T_3.6. handle that all, or should I suggest to split it? .. maybe another teensy just for the sequencer?
so first things first, I thought I start with the midi-clock.
I searched and tried around, but I can't figure out how the midi-clock is working on teensy. Is there a good explanation, maybe with a working example out there?
I need to have:
- midi-clock-generator so my sequencer can run at some BPM-rate
- send the midiClock through MIDI-OUT, so other hardware or DAWs can sync
- teensy recieving midi-clock through MIDI-IN (teensy as clock-slave) and move through the pattern on each tick