How to delete measures in Musescore 3.
I DON'T THINK YOU KNOW HOW FRIGGING MAD I AM TO NOT BE ABLE TO FRIGGING DELETE THE FRIGGING MEASURE FROM THE FRIGGING SCORE! FRIGGING EVERYONE KEPPS FRIGGING SAYING THAT THERE'S A FRIGGING "Timewise Delete" IN THIS FRIGGING SOFTWARE, BUT THERE FRIGGING ISN'T!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! gasps I think I need to lay down..... But seriously if you could help that'd be great.
Comments
"Timewise delete" was the name of the command in an earlier version, but it's currently called "Remove selected range". Still in the Tools menu, and also, the shortcut Ctrl+Delete has always worked through all
versions of MuseScore.
In reply to "Timewise delete" was the… by Marc Sabatella
Yeah sorry about that. Just about as soon as I posted the thing, I figured out how to delete the measures, and now I can't take the post down. Sorry.
In reply to Yeah sorry about that. Just… by SmokySardonyx
LOL
In reply to Yeah sorry about that. Just… by SmokySardonyx
perfect
In reply to "Timewise delete" was the… by Marc Sabatella
It wont work for me
In reply to It wont work for me by babyg0a7
Score needed.
In reply to "Timewise delete" was the… by Marc Sabatella
Sometimes, Musescore 3 gets into a state where the Remove Selected Range function doesn't do anything. Not really sure why. Whether using Ctrl+Del or selecting from the Tools menu, nothing happens. If I close and re-open Musescore it fixes the issue and it starts working again. Strange.
I'd also like to say that I think the Tools menu is kind of a strange place for this function. I consider this to be a type of deleting, and thus I think it makes a lot more sense to have this in the Edit menu. After all, you are editing the score.
Below is my version info:
OS: Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.6.0.487915773, revision: 1977cb3
In reply to Sometimes, Musescore 3 gets… by Sam Chaney1
Exact same thing happened to me; I was really confused at first when I couldn't delete any measures. Restarting also worked for me though; thanks for the tip
In reply to Exact same thing happened to… by kiprobin1
Same here.
In reply to Sometimes, Musescore 3 gets… by Sam Chaney1
I think that Tantacrul is working on making the UI more user friendly. I cannot wait till MS4 with a whole lot of promised enhancements and VST interface. I hope that it also one day becomes a reasonably savvy DAW
Check it out:
https://musescore.org/en/handbook/3/measure-operations#delete
Hlp I need to delete this post I figured out how to delete measures but can't figure out how to delete the post. Pls help.
In reply to Hlp I need to delete this… by SmokySardonyx
Don't worry.
Your post may still be helpful to others who...
1. wish to delete measure(s)
and/or...
2. are not aware of the name change from "Timewise Delete".
In reply to Don't worry. Your post may… by Jm6stringer
I laughed out loud at this post! It lets me know that I am not the only one to have such a frustrating experience! Thanks for the smiles!
In reply to I laughed out loud at this… by ross.parrent@g…
This is one of the best sites for user support (and empathy).
![Muse_smile30.png]( "Muse_smile30.png")
Also, to diminish your frustration with MuseScore and augment your smiles, compare to this method of music notation:
http://lilypond.org/text-input.html
Regards.
In reply to Hlp I need to delete this… by SmokySardonyx
Don’t worry it’s all good! This post also helped me with the same problem lol
I agree it's annoying!!
you have to select the measures you want to delete
then TOOLS
then REMOVE SELECTED RANGE
but it should be called DELETE instead of REMOVE.
In reply to I agree it's annoying!! you… by Lafitte Music Center
Select measure or range and press Ctrl+Del.
We made it a conscious decision to have different terms for delete and remove, delete element/measure/range for deleting the content, remove measure/range to get rid of it entirely
welp well its now called remove empty trailing measures
In reply to welp well its now called… by olivialiu940
Well, no. That is an additional option / tool
In reply to welp well its now called… by olivialiu940
Indeed, "Remove selected range" remains the usual way to delete any selected measures. The "Remove empty trailing measures" is a new command meant only for that very specific case - removing empty measures at the end of a score, regardless of what is or is not selected.
I've tried 'remove selected drange' and cmd-del (mac) to try to remove bars 33-34 in this score, but it's not happening. Any advice?
In reply to I've tried 'remove selected… by jh_yd
That score is corrupt, so anything can happen with it:
Measure 6, staff 1 incomplete. Expected: 4/4; Found: 42/24
Measure 7, staff 1 incomplete. Expected: 4/4; Found: 20/16
Measure 8, staff 1 incomplete. Expected: 4/4; Found: 12/8
Measure 10, staff 1 incomplete. Expected: 4/4; Found: 28/16
Measure 11, staff 1 incomplete. Expected: 4/4; Found: 26/16
Measure 22, staff 1 incomplete. Expected: 4/4; Found: 34/16
Measure 23, staff 1 incomplete. Expected: 4/4; Found: 72/48
Measure 40, staff 1 incomplete. Expected: 4/4; Found: 28/16
Measure 272, staff 2 incomplete. Expected: 2/4; Found: 5/8
Measure 272, staff 5 incomplete. Expected: 2/4; Found: 5/8
Measure 272, staff 8 incomplete. Expected: 2/4; Found: 5/8
Measure 272, staff 9 incomplete. Expected: 2/4; Found: 5/8
Than again deleting those 2 measures just works, is disabling multimeasure rests first
In reply to That score is corrupt, so… by Jojo-Schmitz
Many thanks - I corrected these corruptions and now it worked just fine!
In reply to I've tried 'remove selected… by jh_yd
Seems to work just fine over here. Do note though that there were some corruptions listed when opening that score, which means that there's a good chance edits will respond in unexpected ways.
m33 and 34 are shown as a single multimeasure rest for me, so the question I have for you now is: How are you selecting those measures?
Do you see the blue rectangle around the MMrest before attempting the delete range command? If not, then you've not selected a "range".
In reply to Seems to work just fine over… by jeetee
Many thanks - I corrected the corruptions and now it worked just fine!
Maybe this is a Big Sur thing, but I cannot delete an empty measure. No combinations of keys or selection "Delete Selected Range" from the menu works. I really want to support MuseScore and I believe in open source, but I don't have time to waste on simple things like this, every time MS updates. I appreciate the hard work but I don't see how anyone could rely on this software. After 5 years of fighting on and off, I give up.
In reply to Maybe this is a Big Sur… by bwanicur
If you look at the delete selected range in the menu, to the right will be the shortcut. If there is nothing to the right of it then there is no shortcut defined. Open Edit->Preferences (it might be MuseScore->Preferences on Mac) then in the shortcut tab find Remove Selected Range and define a shortcut.
In reply to Maybe this is a Big Sur… by bwanicur
I'd stop wasting time on MacOS then as well.. Every big update they make they break compatibility with a lot of applications (including MuseScore or drivers).
It's not that I don't appreciate their hard work, it's just stupid to have to waste time on such things..
In reply to I'd stop wasting time on… by jeetee
Exactly my line of thought here ;-)
In reply to I'd stop wasting time on… by jeetee
I can't argue with your complaints about Mac OS. I can remember a time when people were buying macs because they supported audio software better. However, other notation programs manage (somewhat) to navigate the upgrade minefield. I'd rather support Musescore, but it seems to become unusable often.
In reply to Maybe this is a Big Sur… by bwanicur
A very few Mac users have reported a rare problem where somehow this command disables itself until you close and restart MuseScore. As far as I know no one has managed to reproduce it, but it happens just often enough, and only to Mac users, that I have don't doubt there is a bug in there somewhere. But it's a rare problem, with a simple workaround, no need to give up on the software!
Woh! Have some Brandy.
Haha! I feel your frustration working with this immaculately unintuitive software!
In reply to Haha! I feel your… by Gliese667Cc
Intuition is overrated when regarded as an equally allotted human trait.
Because it relates to knowledge and experience, it differs among individuals. What's 'intuitive' to one person may not be to the next.
Frustration, on the other hand, is more universal... ;-)
Consider this scenario:
Task a banjo player with playing a simple major scale... but
hand him a saxophone and you will observe more frustration than intuition.
hand him a mandolin and you will observe more intuition than frustration.
OK... so now:
Task a musician to notate a simple major scale...
hand him a sheet of blank staff paper - no problem.
hand him a laptop with MuseScore installed -- yikes!... different issues may arise depending on his level of computer experience, potential knowledge of, and therefore confusion with, other notation apps' methodology, reluctance to read the MuseScore manual, etc. These are all generalizations, hypotheticals.
So...
That's why the 'Support and bug reports' forum exists -- to address specific issues. Please respond there with any actual problems you encounter.
Forum volunteers will be glad to help.