yes, MIDIPLAY mode was modified in v2.10
v2.10 wrote:MIDIPLAY mode now uses the "midi-note-tracker" code to track up to 8 simultaneously held notes. Now one n0nx0x2 can drive another one with the MIDI notes. It's also possible to play the x0x via a MIDI keyboard in legato style.
now let me explain, it's a bit long but i've been asked a bunch of times about this issue already
i don't know who was the first guy to implement MIDI input (with sequencer bypass) on a 303, or 303 clone, but whoever it was - he has decided to use Velocity for the Accent.
this is convenient, and somewhat logical, but
TB-303 patterns do not
translate properly, specifically the accent.
a few examples:
1) a non-accented note with a slide, followed by the same note with accent
2) an accented note with a slide, followed by the same note without accent
the good news is that at least overlapping notes (playing legato) translates to slide properly.
now, for a proper translation, something else should be used for the accent.
i would think a MIDI CC perhaps
it only needs to be used as a boolean value, just "on" or "off"
however, since whoever decided to use Velocity for the accent - every MIDI implementation on a 303 (or clone, or emulation) does it the same way (i can't blame them)
the x0xb0x firmware does it that way too, same goes for n0nx0x up to v2.09
now, using MIDI CC for the accent might be complicated and inconvenient (from the user point of view)
so in n0nx0x v2.10 i decided to try and make a compromise
what i've done:
i use Velocity for the accent, but the code sepparates notes based on Velocity, in order to distinguish accented from non-accented, so that the same note (with different accent value) can be overlapped
this is a dirty compromise
it means that if you play a C-3 note with velo=100 - it's interpreted as a non-accented C-3 note
now you can also play a C-3 note with velo=127 (which will be accented), however, the device which is generating the midi notes must end both notes <- this is the weird/dirty part
and, i admit this is an ugly compromise
for example, my MIDI keyboard (CME UF60classic) has different velocity on the NoteON and NoteOFF, depending on how hard you press/release the keys
that means that playing legato on the keyboard results in stuck (technically slid) notes in n0nx0x v2.10 whenever the noteON accent value doesn't match that of the noteOFF
n0nx0x2 itself generates MIDI notes according to this, so if you play patterns on one n0nx0x2 machine and send the MIDI to another one, in MIDIPLAY mode - the patterns will perfectly translate
so, in your case, your DAW probably generates MIDI notes with NoteOFF velocity different than their NoteON velocity (which is perfectly normal)
and, i will have to remove this dirty solution, in the next version
the question is: what to do about it:
1) bring it back to the same implementation which everybody uses, where the accent doesn't translate well, but it's perfectly playable via a MIDI keyboard
2) implement the accent with MIDI CC or something equivalent, so that the accent translates well