It was not all the time but more than other people for sure, electrostatic thing maybe, we never knew.
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?
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?
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 has an idea.
Did you try to set fastboot on in the bootloader? I think that was my workaround…
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 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.
I mean the bootloader of the midibox and not the computer.
Great, that seems to work. Thank you so much !
But anyway I’m highly interested what causes this issue… Something seems to disturb the STM when booting… I have no idea.
Me too. Really strange behavior.
Let’s see if Thorsten can enlighten us.