Did MOTU address note on/off issue in version 10?

[bayswater]

Modartt was testing DP 10, and did get back with the final word:

There are no rounding errors. DP is not ordering the note-on and note-off as it should. Here is a list of events received when scrubbing a quantized MIDI sequence:

t=38285 : new MIDI event: note ON chan 0 note 45 vel 62 delta_frame=0
t=38331 : new MIDI event: note OFF chan 0 note 45 vel 64 delta_frame=0
t=39678 : new MIDI event: note ON chan 0 note 41 vel 62 delta_frame=0
t=39678 : new MIDI event: note OFF chan 0 note 45 vel 115 delta_frame=0
t=41024 : new MIDI event: note ON chan 0 note 42 vel 62 delta_frame=0
t=41025 : new MIDI event: note OFF chan 0 note 41 vel 115 delta_frame=0
t=41628 : new MIDI event: note ON chan 0 note 41 vel 62 delta_frame=0
t=41628 : new MIDI event: note OFF chan 0 note 42 vel 115 delta_frame=0
t=42371 : new MIDI event: note ON chan 0 note 41 vel 62 delta_frame=0
t=42371 : new MIDI event: note OFF chan 0 note 41 vel 115 delta_frame=0
t=42975 : new MIDI event: note ON chan 0 note 41 vel 62 delta_frame=0
t=42975 : new MIDI event: note OFF chan 0 note 41 vel 115 delta_frame=0
t=43532 : new MIDI event: note OFF chan 0 note 41 vel 64 delta_frame=0

At t=42371 a new note-on is received for note 41, immediately followed by a note-off for that same note.

I assume you'll ship that off to a MOTU tech link. But doesn't it contradict the same test done using MIDIMonitor to check the ordering of MIDI events?

[stubbsonic]

I assume you'll ship that off to a MOTU tech link. But doesn't it contradict the same test done using MIDIMonitor to check the ordering of MIDI events?

You're right. I certainly can't explain the different result. Modartt seemed quite emphatic that it was the order the events were received.

[stubbsonic]

Just a short follow up:

Support has acknowledged this as a "known issue", so that may be a sign of progress.

We'll just have to keep an eye on upcoming release notes to see if it is ever added to the list of squashed bugs.

[bayswater]

Just a short follow up:

Support has acknowledged this as a "known issue", so that may be a sign of progress.

We'll just have to keep an eye on upcoming release notes to see if it is ever added to the list of squashed bugs.

Good news. I guess they must have dug a bit deeper. Only a couple of weeks ago they told me they couldn't repeat the problem.

[stubbsonic]

Well, the response was actually less "confident" than that.

"I''ll need to double-check this, but I believe this is a currently known issue, something that has already been logged as a bug. My goal is to reproduce the behavior on my end, check out bug log for this issue, and if it is not present, log this with our engineers for fixing."

I did detail the steps to reproduce and reported that "another user" (i.e., you), and the Modartt developer were able to reproduce it.