rest marks will not delete in 3.6 version
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S3 - Major
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
In musescore 2 I could go back and delete the rest marks that the program left once I was finished writing a piece of music ( they must be used a placements by the program). In the latest version, the rest marks can not be cut out of the completed score which makes a huge mess of the notation that I had put into the score
Comments
(Voice 1) Rests could never get deleted in any version of MuseScore and why should they? Rests are silence, you replace them with notes, sound, deleting silence doesn't really make sense.
You can make rests invisible though (and in all versions of MuseScore), by pressing V
OTH in Musescore 3 you actually can delete rests (and notes( by pressing Ctrl+Del<
In reply to (Voice 1) Rests could never… by Jojo-Schmitz
I am not talking about rest marks that I put in for notation, the rest marks come up automatically to show placement of notes...however once the score is finished, I have always went back over the score and deleted those which were left behind, they are not added by me to the notation, and yes I have always been able to do this in Musescore 2...in Musescore 3.6, there is no way to delete them, if I choose to cut them out they stay in the score and when I print it off, it is a mess of rest marks in between notation....there is something really wrong with 3.6 and I have since gone back to my original version 2
Ok, score and better explantion needed.
I have circled the rests that will not remove in a score...or any score for that matter...they seem to be placements for the notation but once I have the score finished, they cannot be removed, making the final printed matter a jumbled mess
In reply to I have circled the rests… by Michael Saint
Please post the score - the MSCZ file, not a picture.
I wonder if you entered Voices 1 and 2 in the top stave and Voices 3 and 4 in the bottom; if so, this will have left rests in Voice 1 in the bottom stave and you should have used Voices 1 and 2..
This is another one that I had finished, and I could delete the rest marks after I finished the notation in Musescore 2....however Musescore 3.6 will not allow me to delete them...and they must be placements for notation....I have now deleted 3.6 and will use the 2 version, it has less headaches
Those rests are in voice 1. No version of MuseScore would allow those to be deleted. In this score, it seems you made the mistake of skipping cvoice 1 on the bottom staff, using voice 3 & 4 instead. That's never correct - always use voices 1 & 2 first for each staff.
To fix this score, select the contents of that staff, then use Tools / Voices to exchange 1 with 3, then 2 with 4, then you can delete the remaining rests (eg, right-click one, Select / All Similar Elements, then hit Delete).
In reply to Those rests are in voice 1… by Marc Sabatella
there is no need for me to do all of that extra work, my Musescore 2 will ALLOW me to delete all those rest marks therefore I have deleted the 3.6 and kept my version 2...problem solved!
No MuseScore version is diffent in that respect.
Staying with MuseScore 2 is absolutely possible if that's your preference nobody should contest that.
However, ability to delete rest hasn't changed one hair between MuseScore 2 and MuseScore 3 .
[ Well in a certain way it has changed as it is actually more (not less) possible in V3 than V2 by automatically reducing measure length.
I don't think it is that particular feature that you are looking after though. ]
So you may want (again your choice, just a proposal) reconsider your tests as deleting voice 1 rests is NOT possible in V2 & V3 and deleting voice 2/3/4 rests IS possible in V2 & V3. As your conclusion was that delete is possible in V2 and not in V3, there is a high probability that you were experimenting with voices 2/3/4 in V2 and voice 1 in V3.
Finally (up to you) it may be worth spending 5 minutes learning how MuseScore manages voices, you may well discover that finally not so many rests need to be deleted.
The most confusing point (but once you get that the rest ;-) is natural) is the fact that what MuseScore calls voices are in fact voices BY STAFF, not voices as in SATB.
MuseScore wants/needs/requires a COMPLETE voice 1 on each and every staff. This is the voice 1 relative to THAT staff, not relative to the score.
So:
SATB on 1 staff ==> use voices 1/2/3/4
SATB on 2 staves ==> use voices 1/2 on each staff
SATB on 4 staves ==> use voice 1 on each staff