Lifting the constraints of measures and time signatures
I'm probably in the minority here and I understand that perhaps I just have a backwards approach to transcribing music, but something that I find particularly cumbersome with Musescore is how strict it can be when filling out a measure.
I'm a long time user of Guitar Pro because, well, I'm a guitarist who used tabs for a really long time. I've been trying to get away from using it and I've been wanting to learn how to use "legitimate" notation software so I chose Musescore.
My general process when writing in guitar pro is to select a measure, type in all the notes for a musical phrase, then go left to right and change their lengths to fit the rhythm. Guitar Pro also lets you know in the bottom right corner how long the phrase is , so if the time signature was set as 4/4 but what I entered in was actually 7/8, it says "3.5/4" so now I know to alter the time signature. Also, the measure itself is highlighted red if the the content of the measure was either under or over capacity. When you play back the audio through guitar pro, it'll either linger on the measure to fill our the specified time signature or just jump to the next measure and ignore the extra beats. This alone seems like warning enough to the user that they need to fix their score without imposing constraints on how they enter it.
Now I could just be a complete noob to Musescore, but my understanding is that the measure must be at exact capacity at all times or else it's a no go. If I entered 4 quarter notes that I meant to make eighth notes and so I go back to change them, what Musescore does is add little rests between each note. If I then try to click on those rests and delete them because I want this pattern of notes to be together, Musescore doesn't allow you. It doesn't even prompt a message to let you know why you can't delete it. I ran a google search and found that I'm expected to either retype the phrase or cut and paste the notes around which is unnecessarily excessive in my opinion.
I find this odd because I've noticed that this idea behind coloring errors is actually in Musescore in a different way. When you enter a note that is technically impossible to play on the assigned instrument, Musescore doesn't restrict you from notating it but it highlights that note in red as a "Hey, just to let you know, this is impossible to play."
But yeah, I just find this to be really cumbersome and it interrupts my process for how I'm used to transcribing music. I just find it so much easier to type in all the notes, assign their values, and adjust the time signature based on what I entered. I mean hell, I tend to play odd-ball avant-garde progressive rock music or whatever you want to call it and my compositional process rarely includes me figuring out what time signatures I'm playing in, hell, sometimes I'm used to using Guitar Pro as a tool to assist me in making sense of my compositions. It would be really nice if this is a feature that can be included someday. Just some kind of checkbox the lifts the "forced" meter of a measure.
Comments
A normal Delete removes sound, as a rest is already silence, it will indeed not again be replaced with another rest. If you wish to remove that "time" from the measure, then select the rest and press Ctrl-Del; you will now also see a small '-' indicator above the measure indicating it has less beats than given by the time signature.
Also have a look at the "insert" note input mode.
But yes, MuseScore does not work well for inputting pitches first and then rhythms 2nd. The other way around is way easier, by using rhythm and repitch note input modes.
In reply to A normal Delete removes… by jeetee
How can i get the correct Beats per measure back in musescore 4?
are you aware of a scoring-software that is user-friendly in the "first pitches then rythm"-Approach?
There is a plugin for this https://musescore.org/en/project/duration-editor
But only for MU3
In reply to There is a plugin for this… by sammik
It is interesting to me that the OP was about wanting to learn "legitimate" notation. And then rejects what is needed to make that happen.
In reply to It is interesting to me that… by bobjp
They haven't rejected anything. Their (and my own) frustration lies with the lack of flexibility of the program.
OP doesn't want to have the finalised version of the measure to have an illegal number of beats in it, they just want the flexibility to see the error present rather than having the program fight you for putting it in. For example, if I realise that I need to increase from a semiquaver to a quaver, Musescore should highlight the error and tell you that it won't work instead of editing the note in front of it, because maybe I want to adjust a different note in that bar to make the time correct.
In reply to They haven't rejected… by blatchie460
See in the Announcements forum Our near-term plans for MuseScore Studio section 3. Refactoring the codebase:
https://musescore.org/en/45-and-beyond
In reply to See in the Announcements… by DanielR
https://musescore.org/en/4.5-and-beyond
In reply to See in the Announcements… by DanielR
Thank you for sending this through! Really appreciate the transparency with everything :)
Sorry if this is outside the scope of this post, but are the scores saved in nightly builds able to be used in stable ones?
In reply to Thank you for sending this… by blatchie460
No. Nightlies are already marked as 4.5, so 4.4 wouldnt open them.
(You can change 4.5 in header in mscx to 4.4, but it is potentially risky)
In reply to They haven't rejected… by blatchie460
@blatchie460
In the case of making a note longer, consider that MuseScore did exactly what you asked it to do. It made the note longer. It has no idea if you want to edit something later in the measure. In the OP case where they wanted to change a line quarter notes to eighths, again MuseScore did exactly what was asked of it. They probably selected the measure or the range of notes and hit the eighth note in the tool bar. So of course there are eighth rests in between. Because a note in a measure is defined by pitch, duration, and location in the measure.