Musescore 3 - Note entry with USB Keyboard is very slow, really unwieldly

• Feb 23, 2019 - 19:43

Hello everyone. I am using Windows 7, Musescore 3, and a M-Audio Keystation 49e USB keyboard. In Musescore 2 the data entry using this keyboard was quick and easy. After musescore 3 arrived it is now very slow and buggy, entering chords especially is a pain, the program keeps mis-interpreting my chords as being either single consecutive notes, or entering them on the wrong beat. It also occasionally throws out one note, and then ties said note to the rest of the chord occuring later on. No matter how many times I go back and re-enter the chord on the right beat, it seems to keep doing this, not sure why.

Note entry used to work. Now it doesn't. Am I the only one having this problem?


In fact, I'm going to add to my earlier complaint. The entire program is slower. Musescore 2 was much faster at everything, from starting up to moving the cursor note to note to saving files and exporting mp3s, etc, etc. Everything was faster.
I do very much hope that musescore 3 can be brought up to speed, it would be a great shame to simply allow it to become slow and burdensome.

In reply to by Milock

I think this is due to an unexplored bug. (hopes are still fresh :) )
v3.0 was really fast up to a certain stage during the development.
Perhaps a code has been modified and the runtime has slowed down (Of course, this was not expected and It's not even known what caused it).

P.S:Of course the "autoplace" feature will have a load on the system. But not as much as now.

In reply to by Milock

If you're able to uninstall and install previous MS3 releases to find where the slow down started, that would probably be a big boon to the devs since it would help them figure out what release the slowdown started. I might give that a try this evening. I haven't noticed a huge difference, but I only do step-insertion because I'm a really bad piano banger.

In reply to by Marc Sabatella

I just quickly tested a large symphonic score in both 2.3.2 and 3.0.3 and I'm very pleased with the initial results in 3.0.3. I will now start using version 3.0.3 to see if the results prove reliable. Since the release of 3.0 I have limited my use of 3.x to mostly testing and bug verification. I expect to have more of an opinion in a couple of days.

Do you still have an unanswered question? Please log in first to post your question.