MuseScore 4.0 RC1 Unable to use shortcut adding rests
MuseScore 4.0 RC1 Windows..
I am unable to get the keypad zero character "0" to insert a rest for a selected note duration. The digit "0" in the top row of my keyboard does work, but is inconvenient to use when manually adding notes from a printed score. I am ALSO unable to reset the feature in the 'Preferences' menu by trying to define it using the keypad.
Has this method of rest entry change for 4.0, or is it an omission? I wouldn't exactly call it a bug, but it would be great to match the 3.6 behavior in this case.
Comments
The keypad shortcuts issue is known
To be clear: the numpad is not recognized correctly on some (many? most? all?) systems. It's not specific to 0, just a general numpad issue.
Not sure what makes the regular 0 inconvenient on your keyboard, but you can redefine it to be whatever you like, other than a numpad key.
In reply to To be clear: the numpad is… by Marc Sabatella
Okay -
The keypad did and does work in MS3.6 . I transcribe old scores and the zero keypad key is within reach without letting go of the mouse, so the keypad is a big convenience. Otherwise, I am forced to lose my place in the transcribing source score to find the regular keyboard zero (I'll live).
I didn't expect this to be a serious issue to "fix". I am sure development has their hands full, so I wouldn't valuable time wasted on it.
In reply to Okay - The keypad did and… by Chris_Clawson
I'm still confused though. If you're using the mouse anyhow, why not use it to enter the rests? And if you're mostly using the keyboard, isn't the lack of the other numeric keys working an even bigger issue? And what about the idea of redefining the rest shortcut to be something else that is convenient? Understanding your unique workflow is important to us being able to offer you the best possible assistance while we all wait the for the issue to be resolved.
In reply to I'm still confused though. … by Marc Sabatella
(Sorry this is long) I am not a composer. I am a transcriber, historian and collector of vintage media and music. My phono record collection dates back into the 1890s. Today, I digitally conserve vintage media and produce local history video documentaries.
I began studying music and transcribing in the 1980 as PCs became practical enough to use for MIDI. My source material was antique music scores I found at flea markets. This is the core of my music background.
MIDI scoring and public domain music is perfect for a zero budget, amateur video producer. Music may be edited and timed to fit video scenes perfectly. The music is public domain and I am rendering my own versions, so there are no copyright issues. MuseScore has become a blessing and critical part of my production work flow.
I am now transcribing 130 year old scores I have owned for 30 years and didn't have the skill to read even a year ago. It is important to be both accurate and fast in transcribing. I am amazed with admiration how well suited and designed MuseScore is made for musicians and I am sure that many (if not most) of the designers also have music skills, themselves.
Sight reading musicians look only at their scores while performing. A Musescore transcriber is at a disadvantage, because their 'instrument' must also be looked at, in order to 'play'. I am forced to follow what is on screen as well as keep my place in a score I am transcribing. Of course, all of MuseScore's tools and shortcuts are critical, but usually require additional screen interaction.
My hands are mostly used in keeping a finger on my place in the score and operating the mouse for note entry. The 'up', 'down', 'left', 'right' and keypad Zero keys are also used constantly and the mouse hand can quickly get to them with the bend of a wrist and then back without ever looking. The keyboard zero is in the upper middle of the keyboard and requires me to break my place in the score and lift my arm to hit the keyboard zero. This may sound silly as a complaint, but it loses time, accuracy and gets tiresome when repeated 100s of times.
I have also begun using voice recognition to activate many keyboard shortcuts. This helps me keep place and allows rapid switching between note lengths and articulations. Voice recognition works well and I will be making better use of it later.
I hope these points and descriptions have been worth the time reading. I have the utmost respect and appreciation for the MuseScore project. I spend many hours a week using it. I am realizing old music never performed in this lifetime and am learning much more rapidly than I have ever expected.
I guess RC = "release candidate". Is this something that comes after 'beta'?
In reply to I guess RC = "release… by Are Jayem
Yes
In reply to I guess RC = "release… by Are Jayem
Yes. Beta = “we’ve implemented almost all functionality; still plenty of bugs but should be usable enough for people to install and help us test”. RC = “we have literally fixed everything we plan to fix, so unless new bugs are discovered than the ones we already decided not to fix, this RC will be what is actually released (usually very soon)”.