For several years now I've been using MuseScore to notate and write music. See https://musescore.org/en
It is great for getting started, and a big plus is that it is free to download and to use. It can also handle large scores - it does have a lot going for it.
However, there are limitations, and I'm now seriously wondering whether to bite the bullets and switch to other systems such as Sibelius or Dorico.
There are planned improvements to MS - taking it to version 4, but I doubt whether some of the more significant failings will be fixed for some while - a time measured in years not weeks.
Things I find particularly painful in MS include:
1. No album feature. This was available in MS v2 - and it is possible to revert back to that if really "essential". Most people won't want to do that, though I can see that on occasion that might actually be the best option. An album feature allows one to create several pieces, and assemble them all into a group - for example a suite of pieces, or a set of variations.
There are kludge ways round this in MS v3 (and presumably v4) - such as concatenating XML files, but that's hardly a good way to go about things. Useful to know maybe, but hazardous for many who aren't technically very proficient with under the hood software systems.
2. No persistent history feature. There is a history feature which works within a session using MS, but navigation through that is haphazard, and it hasn't been developed to any really sophisticated extent. Unfortunately it is not persistent, and the history disappears when scores are saved. It is possible to have persistent history in software as some photo editing and designer packages have already shown.
3. Poor lock features. It is not possible to lock sections of a score to prevent accidental changes. At times it might be useful to make changes to a small part of a larger score, but be sure that nothing outside the selected range will be amended. Again this is similar to a select feature in a photo editing package.
4. There is no file include feature which works. It would be very useful to be able to insert other score files into a larger one. I know this may present problems, but it shouldn't be completely insuperable. This would allow a larger work to be built up from smaller parts. It could be as "simple" as Symphony = Movement 1 + Movement 2 + Movement 3 + Movement 4 [where those are either separated pieces of music, or continuously flowing] but could also be more detailed - such as Movement = Intro + Theme 1 + Contrasting Theme 2 + Development Theme 1 + Themes1+2 combined ...... + Coda. This would enable work on parts of a larger work to be carried out without spoiling the whole structure.
An alternative approach is sometimes suggested - simply work on the whole thing - and have multiple copies - but this raises the issues already mentioned in points 2 and 3.
It can be a recipe for disaster.
So - having pointed out some of the problems, what I now want to know is whether Sibelius, Dorico, or any other notation packages will reduce these issues to something manageable - even at a cost.
MS is really good for getting started and writing small pieces, and some of its features such as transposing and parts generation from master scores are really helpful, but I am unconvinced that it is currently good enough for anything really large - not without a lot of frustration anyway.
Comments from other users of notation sofware would be of great interest.
It is great for getting started, and a big plus is that it is free to download and to use. It can also handle large scores - it does have a lot going for it.
However, there are limitations, and I'm now seriously wondering whether to bite the bullets and switch to other systems such as Sibelius or Dorico.
There are planned improvements to MS - taking it to version 4, but I doubt whether some of the more significant failings will be fixed for some while - a time measured in years not weeks.
Things I find particularly painful in MS include:
1. No album feature. This was available in MS v2 - and it is possible to revert back to that if really "essential". Most people won't want to do that, though I can see that on occasion that might actually be the best option. An album feature allows one to create several pieces, and assemble them all into a group - for example a suite of pieces, or a set of variations.
There are kludge ways round this in MS v3 (and presumably v4) - such as concatenating XML files, but that's hardly a good way to go about things. Useful to know maybe, but hazardous for many who aren't technically very proficient with under the hood software systems.
2. No persistent history feature. There is a history feature which works within a session using MS, but navigation through that is haphazard, and it hasn't been developed to any really sophisticated extent. Unfortunately it is not persistent, and the history disappears when scores are saved. It is possible to have persistent history in software as some photo editing and designer packages have already shown.
3. Poor lock features. It is not possible to lock sections of a score to prevent accidental changes. At times it might be useful to make changes to a small part of a larger score, but be sure that nothing outside the selected range will be amended. Again this is similar to a select feature in a photo editing package.
4. There is no file include feature which works. It would be very useful to be able to insert other score files into a larger one. I know this may present problems, but it shouldn't be completely insuperable. This would allow a larger work to be built up from smaller parts. It could be as "simple" as Symphony = Movement 1 + Movement 2 + Movement 3 + Movement 4 [where those are either separated pieces of music, or continuously flowing] but could also be more detailed - such as Movement = Intro + Theme 1 + Contrasting Theme 2 + Development Theme 1 + Themes1+2 combined ...... + Coda. This would enable work on parts of a larger work to be carried out without spoiling the whole structure.
An alternative approach is sometimes suggested - simply work on the whole thing - and have multiple copies - but this raises the issues already mentioned in points 2 and 3.
It can be a recipe for disaster.
So - having pointed out some of the problems, what I now want to know is whether Sibelius, Dorico, or any other notation packages will reduce these issues to something manageable - even at a cost.
MS is really good for getting started and writing small pieces, and some of its features such as transposing and parts generation from master scores are really helpful, but I am unconvinced that it is currently good enough for anything really large - not without a lot of frustration anyway.
Comments from other users of notation sofware would be of great interest.
Comment