It’s a rollercoaster of emotions.
The tension is killing me.
But now, it is actuall done.
It now works.
If you need to sequence something with Octatrack, but it starts droneing because the receiving synth does not understand that Midi Note On with Velo 0 means Note Off, you can buy a RK002 from Retrokits, and program it with this sketch:
#include <RK002.h>
RK002_DECLARE_INFO("SAMPLE CODE","duy@retrokits.com","1.0","7b47d3dd-991a-4197-ac02-d340cdabfb59")
boolean RK002_onNoteOff(byte chn, byte key, byte vel)
{
RK002_sendNoteOff(chn, key, vel);
return false;
}
void setup()
{
}
void loop()
{
}
Albert and Gerrit from Retrokits are awesome. They didn’t give up.
They are stronger than me.
Explanation:
*) RK002_onNoteOff() is correctly being called by the internal parser upon reception of noteOn/vel0 (because the MIDI standard dictates: noteOn/0 should be handled exactly the same as NoteOff (!))
*) normally the RK002 would literally pass-through the received bytes (so: noteOn/vel0 ----> {no handler} --> passed as NoteOn/vel0)
*) but because now the handler explicitly transforms it into a NoteOff message, the path will be: noteOn/vel0 —> {noteOff handler called} --> explicit NoteOff message sent
I guess you can’t imagine how happy an old man can be.
I can sequence now my loved Gen-R8 with the Octatrack.
I was on the way to throw the grey monster out of the window and call it done.