Developing MuseScore 3.0: Make it better
I like some new features in MuseScore 2 version however I have to stick with the older version because in the second version the words stick to each other too often. I really hope this issue will be fixed in the 3rd version.
I'm looking forward for a new version hoping it would work much better although I'm already happy with this absolutely affordable and mostly easy in use note writing software and a lot of tutorials here on your website!
There are also a few features I'd like to see available (unless I'm wrong if I couldn't find them in older versions):
- To be able to select a specific lyrics row (not clicking on each word/syllable holding ctrl key all the time), to be able to delete all at once, if necessary
- copy and paste music notes without attached lyrics
ALSO:
- to make files compatible to older and newer versions (as of now, I cannot open in MuseScore(1) the file created in MuseScore 2. With this issue, when someone shares with me a newer version file I must work only in newer MuseScore 2 with words/syllables stuck to each other.
Comments
- you can lasso-select a whole row, or use right-click/Select/more.../same verse and then delete all at once.
- using the selection filter you can copy notes without the lyrics
- older version won't be able to open files created in newer version, due to new features and the changes in file format that went along with that. You should be able to export as MusicXML in the higher Version and open/import that in the lower version
In reply to - you can lasso-select a by Jojo-Schmitz
Thanks!!
I'm working on a new song right now and one glitch happened in the old version of MuseScore: while changing key signature to F#, it started automatically add ♮ to each note (so frustrating).
So I switched to version 2 which does not make this problem and that is good.
However, I can't use one feature that was available in old version:
I can't select a single pause and right-click to set invisible.
I hope this feature (right-click and select "set invisible/set visible") will be available again in a newer 3rd version.
In reply to Thanks!! I'm working on a new by ovitruk
It probably wont.
You can however toggle the visibility of any element using the corresponding checkbox in the Inspector (F8) or simply by pressing the shortcut keyV.
In reply to It probably wont. You can by jeetee
OK, thanks for letting me know how to use this feature, I really appreciate this.
In reply to Thanks!! I'm working on a new by ovitruk
FWIW, it wasn't a "glitch" in 1.3 that typing F would enter an F natural regardless of key - it was how it designed to work. Typing F always entered an F, so the behavior was consistent; if you wanted an F#, you had to hit the up arrow afterwards. But indeed, most people found this unnecessry extra work, so it - along with thousands of other things - were improved in 2.0.
Can you explain exactly what you mean by "the words stick to each other too often", maybe with an example? That shouldn't happen and there should be really no good reason to use MuseScore 1.3.
In reply to Can you explain exactly what by [DELETED] 5
I assume he is referring to the fact that by default, tightly spaced hyphenated lyrics will appear without a hyphen, in accordance with how some editors like to present music:
This is considered correct in some circles, but some people do still prefer to see the hyphens. If you prefer to see them, it's easy enough to force the hyphens to appear - just increase the note spacing, which is what 1.3 forced upon you anyhow. You can either increase stretch for just the measures with the too-tight spacing, or go to Style / General / Measure and increase the global spacing value or the minimum note distance to mimic the 1.3 behavior. Here, for example, I increase the minimum note distance to 0.5sp:
3.0 will provide even more options to control this behavior.
So, there should be no reason to keep using 1.3. If that doesn't solve your problem, please start a new thread, attach the score you are having trouble with, and explain the problem in more detail. Probably it is something as simple as this.