A4 sending false note off messages?

Elektron Gear Analog Keys/Four
#1

Hi!

I noticed my A4 (mk1, 1.50A) sending seemingly random note off messages.

For example:

  • Create a 1 page pattern, tempo 30
  • 0xxx0xxx0xxx0xxx
  • Set MIDI output on a channel for the track (in my case, it’s the FX track), it is reproducible with both usb and din midi
  • Watch MIDI with software, e.g. MIDI monitor

On the 16th note, I consistently get a note off. message, silencing the note right away, and it’s messing with my workflow.
With longer patterns, it seems to be more erratic. With very short page (4/16), there is no problem at all.

I am planning to report the issue, but it would be nice to understand it more first. Or maybe it’s an error on my part.
Did someone else notice anything similar? Any workarounds?

#2

Firstly - the bug discussion thread might be best for things like this

Secondly - you’re not providing enough info to replicate

The Midi out should create a note off (almost) immediately after every note on (dependent on track Note Len or plock - default 1/16), when starting from a new project, this does what you’d expect - so it’s hard to say what’s wrong for you as it works normally here

#3

Bug discussion <- you might be right, sorry about that.

Midi Note len is 1/2 on all of the mentioned trigs. Plus, this note off is happening exactly on the 16th note.

For example, if I try to micro-time this last note +1/384 as a workaround, the note off happens first then the (delayed) note on, and it sounds ok.

#4

I don’t see this - you need to document all steps from a new project if you want somebody to reproduce

you have a step every 4 1/16ths i.e. every 1/4bar
the note length is 8 1/16ths i.e. 1/2 bar - so every note should be getting a note (cut)off immediately prior to the next Note on, this is what I get all the way past 16 notes, like clockwork - note on followed by note off 2sec later w new note on immediately ad infinitum

no note offs are happening here within 2sec

if you can reproduce from a new project then share that step by step workflow for consideration

#5

Interestingly, I managed to workaround it by setting bigger note length (way bigger than 16.0). I still think this is a bug, although I was not able to clearly reproduce in a fresh project so it’s a bit mysterious.

Thanks for being helpful!