![]() Nearly every element in MS can be styled and customised. GP has a fixed automatic element placement algorithm MS has an AI based algorithm that the user can override. MS gives you a huge set of text styles which can be customised at the global level or per instance - and you can use colour - and you can define your own styles. For me, GP excels in ease of input, (little things like automatic rests do make a difference), and quality of sound output, (the range and quality of the soundfonts is impressive, especially guitars), whilst MS excels in control of layout for printing.įor example, GP gives you stave text, lyrics text, chord text and finger text which you can style with any font, size, style - all in black and defined globally only. GP is obviously somewhat guitar focused but by no means "current musics" and, unless you're on a tight budget then it's fairly low priced for what it offers. IMO it works well in other apps like Guitar Pro 7, just saying. You see how that "no-autocorrect" option would temporarily break the bar rhythmic integrity but streamline the workflow. It would be way quicker to just select the first note and shorten it into 16th's, select the second note and lengthen it into 8th's, done. ![]() Sort of same story happens if you decide to shorten the first note into 8th: a rest is created, you have to "move ahead" the other note then lengthen it into 8th. That's annoying, you have to go back and edit. That's intuitive, but in MuseScore if you select the second note and make it from 16th's into 8th's then MuseScore "eats" the next 16th note to keep the bar correct. Handwriting on a sheet of paper you would just fix the 16th note beaming, done. Then for whatever reason you decide to swap the duration of the first two notes of that fragment, without altering the pitch. Say you just composed/arranged/transcribed a melody where a fragment has one 8th note followed by two 16th notes. This is why such option would be a convenient feature, actually saving time. In short: it does not seem to be possible at the moment. Cut and paste it to the rest just before it. Hit the right arrow twice, landing you on the sixteenth. Of course musescore will now show a normal eight + sixteenth rest + old sixteenth note. On each dotted eight, use the '.'-key to remove the dot. In your specific case, the rewrite is quite doable without having an impact. You might just as well have decided to use entirely different pitches, including uncommon tuplets etc… No psychic on the planet can guess that, let alone a computer. You know you want to go from dotted eight + sixteenth to two eights with the same pitch as before. As far as anyone or anything except your own mind knows, this melody could be completely different. You problem seems to be that you've written a melody and then decide to change the melody that is written by a new one. It notates the remainder of the measure in a correct manner at all times. ![]() This is even more true if my co-composer continues where I left off. ![]() Its actually keeping the measure correct so that at whatever moment in time I stop/restart writing the score I never have to keep track of all the measures I would've made incomplete. I've never found keeping the count of a measure as it is (always have 4 beats in 4/4) 'entirely screwed up'. ![]()
0 Comments
Leave a Reply. |