Sometimes, a key that i am not even close to will randomly play and then hold itself down forever, and sometimes keys wont register and i have to hit it multiple times for it to do so. Then it will show up as being held down forever, even though i can still use the key and it makes no noise. I believe this is likely to be a cable issue, so ive tried three different new cords and it did not work. Could this be a problem with the piano itself? The sounds always play just fine, its just synthesia does not register them.
10.3.4096 windows 10
Keys not registering when pressed and other weird issues
When describing problems, always mention your OS and game version (shown at the bottom of the title screen).
If your keyboard has USB or MIDI ports, there is a tremendously high chance (>99%) it will work with Synthesia. See what you'll need on the keyboards page.
If your keyboard has USB or MIDI ports, there is a tremendously high chance (>99%) it will work with Synthesia. See what you'll need on the keyboards page.
Which brand/model keyboard are you using?Ghotty wrote:Could this be a problem with the piano itself?
Usually this is a MIDI adapter problem, but we've recently heard from another user with an M-Audio Keystation 88 (connected directly via USB) that described exactly the same problem as yours. Even after exchanging the keyboard (in case the first one was faulty), the problem persisted. He said it tended to happen more when lots of keys were being played simultaneously.
How interesting, especially that both reports came in so close to one another. I wonder if Microsoft changed something in Windows. (Mostly because Synthesia 10.3 has been out for more than a year and this is the first time this has come up.)
This might be worth a shot: Microsoft just recently added a replacement MIDI API to Windows 10. It's the first big change to Windows MIDI since, like, Windows 3.1 (seriously). And in the meantime, the older-style MIDI API has been having a rough time since Windows 10 was released. (At launch, Microsoft had left it completely broken!)
The latest beta version of Synthesia 10.4 adds support for the new stuff Microsoft just added. If you give that beta a try, do you still get stuck keys?
This might be worth a shot: Microsoft just recently added a replacement MIDI API to Windows 10. It's the first big change to Windows MIDI since, like, Windows 3.1 (seriously). And in the meantime, the older-style MIDI API has been having a rough time since Windows 10 was released. (At launch, Microsoft had left it completely broken!)
The latest beta version of Synthesia 10.4 adds support for the new stuff Microsoft just added. If you give that beta a try, do you still get stuck keys?
We heard back from the other user (after running out of ideas ourselves) to hear that he'd solved it himself. This sounds very strange, but... he had been using VirtualMIDISynth with Synthesia and after increasing the "additional buffer" setting in the synth, the problem went away.
That is a very strange solution. Normally an output device should have absolutely no effect whatsoever on an input device, but that is what worked for him.
(Now, if you're not using VirtualMIDISynth, I'm still at a loss about what might be going wrong. Maybe the buffer change was coincidental and it was something else like a Windows Update that fixed it?)
That is a very strange solution. Normally an output device should have absolutely no effect whatsoever on an input device, but that is what worked for him.
(Now, if you're not using VirtualMIDISynth, I'm still at a loss about what might be going wrong. Maybe the buffer change was coincidental and it was something else like a Windows Update that fixed it?)