tago

Hi @Hawkeye thanks for your fast response. I'm using Windows 10. I've done it successfully before on Win 10. The only thing that works now is starting all over and uploading the bootloader via ST-Link again and then a precompiled NG app via MIOS Studio. (i haven't tried the bootloader hold trick yet) Greetings

This is the NG app compilation output: make rm -f project.hex ------------------------------------------------------------------------------- Application successfully built for: Processor: STM32F407VG Family: STM32F4xx Board: MBHP_CORE_STM32F4 LCD: universal ------------------------------------------------------------------------------- arm-none-eabi-size project_build/project.elf text data bss dec hex filename 294048 224 173520 467792 72350 project_build/project.elf 20000000 D __ram_start 2002a6b0 B __ram_end

Hi, i compiled an unaltered NG app and uploaded it to the core ( STM32F4). MIOS Studio told me it was uploaded successfully. During upload i could see 'bootloader mode' on the display. But now the core is unresponsive and MIOS Studio doesn't find it anymore. One red led is blinking the other is permanently on. A green led near the micro USB port is on as well. The Display which is connected to the core shows nothing. How can i check what's wrong? Thank you

Hi, is MIDI 2.0 support planned or already being worked on? Best regards

Me too. Really strange behavior. Let's see if Thorsten can enlighten us.

Great, that seems to work. Thank you so much @FantomXR!

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.

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?

Unfortunately the problem is still there. I had to change the USB port again, after getting inverted on/off events. I've no idea what is causing this. What could be the culprit?

Radioactive Man ;)

Yeah its kind of solved. I mean the inverted On/Off behaviour is really strange.

Thanks for your assistance @Antichambre

I changed it back to the original USB port and now it works there too. Maybe the cable was not correctly inserted? But that doesn't explain why MIDI-OX showed the correct MIDI data all the time. Very strange.

I think i found the culprit. I've changed the USB port and now it works. Regardless i'd like to know what the underlying problem is. I've never encountered such a problem in conjunction with a MIDI keyboard before.

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.

Disabling MIDI thru in Cubase preferences results in no MIDI input at all. My controller has no regular MIDI ports to test with, USB only.

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?

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

Thanks for your help @Antichambre Yes, i tested it carefully. It can also be heard when playing a VSTi. Frist i thought there were hanging notes. But now it looks like Note On and Off events are simply inverted, which results in a similiar scenario.

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

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.

new thread:

...

...

Thanks Thorsten!