I have some issues with the midi of my Octatrak mk2 (V1.40A),When i make parameters locks on notes on a few trig sometimes it seems that certain steps are mute, it doesn’t send any midi data (i’m not seeing the blink on the screen) For exemple, on a 16/16 pattern, all trig are active (red), i make parameters locks (notes) while listening to it and suddently a trig or several trigs are skip (not midi send). The only thing i find to “reactivate” this trigs are trig+yes for preview, or change the midi channel, or restart the octatrack. It does the same thing sometimes when i change the root note for transpose the sequence.
Anyone had this issue before ? Is it a bug or i did something wrong ?
Welcome!
I never encountered that. Same behavior with a fresh project ?
I guess you don’t use trig conditions…
Do you plock notes only? No lfos?
A note with VEL(ocity) with value 0 is not sent. Plocks of lfos on VEL can mute notes. (Lfo on VEL was a trick to mimic trig conditions before their implementation).
Thanks for the answer !
I tried too with a new project , no trig conditions indeed, no lfo either only notes are parameters locks.
I think this issue comes from the trig preview (trig+yes) i did it when listenning (trig+yes until i find a note i like) and there the trig doesn’t work (seems midi off on that trig)
It’s weird, maybe a bug ?
What is going on with this, has there been any solution in 4 years? I have the same problem with the OTmk2 MIDI sequencing a moog Sirin, i can easily reproduce a state where certain notes in the scale are not sent. I will make a video.
I also have a Sirin being sequenced with an Octatrack MKII. I have not run into this issue yet, but I’ve only had the OT for a couple months. Curious to learn more about this issue in case it comes up down the road.
No, not for the notes that are apparently missing. The videos in my new post show that.
No, unfortunately I don’t have one.
Here’s my new post with videos. TL;DR previewing MIDI trigs with TRIG+YES while p-locking different notes to that trig breaks the sequencer. Another post said this confuses the sequencer and that STOP STOP will fix it but for me it does not.