Jump to content

Note Off events missing (inverted Note On/Off events)


tago
 Share

Recommended Posts

Hi,

i've encountered an issue while testing my keyboard controller.

The output in MIOS Studio shows correct note on/off (key pressed down = on, key released = off) events, but when i'm testing on a separate music computer running Cubase those events seem inverted (on -> off and off -> on)

Cubase MIDI monitor shows something like this on a single C3 press:

Note On   C3   0
Note On   C3   127

It looks like Note Off events are missing and strange 0 events are triggered before Note On.

I've no idea what is causing that.

 

Edit: The solution was to change the USB port or reinsert the USB cable.

Edit 2: The problem is unfortunately still there.

Edited by tago
Link to comment
Share on other sites

Here is my config. Jumper J6 on DIO_MATRIX module is set to the left position (inverted diodes).

KEYBOARD n=1   rows=8  dout_sr1=1  dout_sr2=2  din_sr1=1  din_sr2=2  din_inverted=1  break_inverted=0  din_key_offset=32 \
               scan_velocity=1  scan_optimized=0  note_offset=36 \
               delay_fastest=5  delay_fastest_black_keys=0  delay_slowest=100

 

Link to comment
Share on other sites

I noted another strange thing.

When i press C3 for the first time after opening Cubase i see multiple Note On 0 events with different note values fired. There is no C3 0 event, only the last C3 127 event.

Note On   E1   0
Note On   F1   0
Note On   F#1  0
Note On   G1   0
Note On   G#3  0
Note On   A2   0
Note On   A#3  0
Note On   B3   0
Note On   C3   127

After the first C3 press, there are only two events fired per key press as described in the opening post.

Edit: this happens only sometimes

Edited by tago
Link to comment
Share on other sites

I've swapped the MIDIBox controller with another MIDI keyboard and everthing looks fine in Cubase MIDI monitor. It sends Note On and Note Off events as expected.

Besides MIDI-OX outputs everything as expected for both of my controllers. MIDI-OX output looks exactly like MIOS studio output.

So there is something wrong when using the MIDIBox controller with Cubase. But what the hell is it?

Link to comment
Share on other sites

Try also to desactive MIDI THRU in cubase midi settings...

And if your midibox has regular MIDI and you own a midi interface try with it instead of USB directly.

Note: if your're connected with usb there's no running status then Note Off must be received.
Running status is only for regular midi connection(DIN) and MIOS studio marks the Note Off as "optimized" when it's the case.
 

Edited by Antichambre
Link to comment
Share on other sites

It seems is not an exclusive Cubase problem since NI Absynth in standalone does exactly the same thing (Note On/Off inverted).

Edit:

I've tested it on another computer, which also runs Windows 10, using SAVIHost running Synth1 with no issues.

Edited by tago
Link to comment
Share on other sites

  • 4 weeks later...

I could locate the problem to a point after some further testing.

It has nothing to do with changing the USB port. Simply removing and plugging the cable into the same USB port again solves it when the computer is already running.

The problem occurs after every system boot when the pc was disconnected from the mains before. But what can possibly go wrong in that scenario? I never encountered such a problem with any USB device before.

Has anyone an idea what to check or why it happens? Maybe it somehow power related?

 

Link to comment
Share on other sites

I remember that I encountered that a few times too already. All digital signals where inverted after system boot. So also buttons that were connected to the midibox didn't sent 127 when pressed but 0 and the keyboard did the same. 

I never solved this. Maybe @TK. has an idea. 

Did you try to set fastboot on in the bootloader? I think that was my workaround...

Link to comment
Share on other sites

38 minutes ago, FantomXR said:

I remember that I encountered that a few times too already. All digital signals where inverted after system boot. So also buttons that were connected to the midibox didn't sent 127 when pressed but 0 and the keyboard did the same. 

I never solved this. Maybe @TK. has an idea. 

Did you try to set fastboot on in the bootloader? I think that was my workaround...

The motherboard doesn't have an option for fastboot. It's an older Asus P8Z68-V Pro. I've changed some USB settings, but no luck with that.

I tried this: https://help.uaudio.com/hc/en-us/articles/213195423-How-To-Disable-Fast-Startup-in-Windows-10

But this didn't do the trick either.

Really strange. I don't know what else i could try.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...