Note input
MuseScore version (32-bit): 3.0.0., 3543170
If with Virtual Piano Keyboard (they tell me that the same thing happens with the MIDI keyboard) I enter the same notes (C, C, C) the previous one is replaced by a rest. Is there a trick?
Do you still have an unanswered question? Please log in first to post your question.
Comments
Thanks for informing me about this. I can verify happens for both my midi keyboard and MuseScore's virtual keyboard. I'm on OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.0., revision: 3543170
In reply to Thanks for informing me… by ericfontainejazz
That commit is 5 years old, so got to be wrong, whoever built it probably forgot the "make revision". Not sure how this can happen on a Windows build...
I'm also noticing another problem...if I try to play a chord on piano while in step-time (default) note input mode, the cursor won't advance, so my inputted chord simply replaces the last inputted chord (without advanced further as it should).
Does anyone else know when this problem arose?
Exactly, that's what happens. Also in the case of repeated chords, even if it is another chord but contains 2 notes in common.
Also reported here: https://musescore.org/en/3.0
Maybe the same issue: https://musescore.org/en/node/280654?
I don't find an issue tracker entry, maybe should added there.
In reply to Also reported here: https:/… by kuwitt
See #280715: Identical subsequent notes disappear on MIDI input
Same issue here, but I'm using version 3.0.0.20137 Revision c1a5e4c, on Mac OSX Mojave 10.14.1
The program is saying it's up-to-date - no updates available, but the OP is running version 3.0.0.3543170 - is that a Windows-specific version and that's why it has a higher version number than the latest for Mac (.20137)? Or is there a different newer revision available online that can be downloaded manually? (Sorry for the ignorance about how the version numbering system works.)
In reply to Same issue here, but I'm… by edwardjc
OP is running a version on Linux that is reporting the wrong number.
In reply to Same issue here, but I'm… by edwardjc
c1a5e4c is the final 3.0 release from christmas eve, so indeed the latest and greatest.
There are a couple newer development builds, but a) thisese are just that, development builds and b) don't yet fix this particular problem.
I did make a PR: https://github.com/musescore/MuseScore/pull/4514
If someone on windows wants to test that: https://ci.appveyor.com/api/buildjobs/km8l85wrq3wmwgb2/artifacts/MuseSc…