Feedback after a long score transcription

• Oct 21, 2024 - 16:22

Please note that I attach the content of this post as a Microsoft Word document.

Dear MuseScore developers and users,

After many other and simpler transcriptions, I took a great pleasure in the transcription, from its original score published in 1947, of Sergei Rachmaninoff’s second piano concerto, Op.18. This is not complex music (I mean, except for the pianist, who is really working hard!!!), in terms of harmony, but very efficient in terms of emotions.

MuseScore is becoming a fantastic tool, and let me first warmly congratulate the development team, who has made a tremendous work.

I would like to take this opportunity to give feedback based on my personal experience (this score, but also contemporary music, which I transcribe from living composer’s manuscripts). I work on a powerful computer (Intel i9, 32 Gbytes of RAM, 2 Tbytes of SSD as main storage, and NVIDIA GeForce RTX 4080). OS is Windows 11, French. As I don’t have – yet! – a MIDI keyboard, everything is made with mouse and keyboard (French).
I worked on this score with MuseScore 4.1 and up to 4.4 version.

Among positive points, let me highlight:
• Very good stability of the program; mainly manipulation of slurs pose problem, as you may already know (systematic crashes occur when you handle one, not by its handles, but its shape)
• Ergonomics:
o The program is very well organized (better to my point of view than Finale, which is now – surprisingly – abandoned by its creators)
o Tool palettes are very well thought
• Extraordinary richness and intuitive use of (numerous!) musical signs
• Versions 4.x and 4.4 have brought major improvements with:
o Coloured measure subdivisions to better position dynamics indication (hairpins or other)
o Possibility to differentiate sound levels according to voices (this is very useful for Rachmaninoff’s piano part, which has often several voices, even within one hand staff)
o Much easier manipulation of arpeggios among two staves, and in general rather easy change between staves for piano (CTRL + MAJ up and down arrows, only slurs are sometimes a bit difficult), etc.
• To my point of view, MuseScore sounds are of great quality, including articulations, even if the dynamics should be improved (for instance piano pianissimos sound like if you turn a volume knob rather than playing really pianissimo)
• Automatic horizontal alignment between hairpins and neighbouring velocity indications is also a great improvement
• Zooming in and out with the mouse wheel is very fast and reliable (never any crash)
• PDF export is very fast and of excellent quality
But of course, “The more you have, the more you want”… So let me now focus on points that require improvements, to my point of view, with a “Liste à la Prévert” as we say in French, hoping this will be useful for developers and users.
• Probably the most urgent is the copy/paste. For obvious reasons (complexity and length of this work), I worked with 3 different files, one for each movement. Merging those 3 scores into a unique one has been very painful. As you already know, MuseScore does not tackle appropriately time indications:
o Time signature changes are not considered (this is a long-lasting bug, which should be corrected urgently)
o Tempi indications are also not copied for most of them
o More surprisingly, “ral.” or “alarg.” are copied, but not “a tempo” or tempi indications, etc.
o Measure bar separations are also ignored (double bars for instance, inside a movement)
o Markers along the score (for instance numbers in squares at the top) are also ignored
• For practical reasons, I work in continuous horizontal layout. Consistency between this mode and the page mode should be improved: slurs, piano pedal signs are not positioned coherently
• I also noticed a significant difference of time for saving in page mode or continuous horizontal mode (particularly significant with large scores). Perhaps continuous horizontal mode could be further optimised.
• Piano pedal signs should be put systematically below the left-hand staff and horizontally aligned, even if for practical reasons, you chose the right hand as a reference for their duration (and you should avoid creating an artificial supplementary voice at the left hand to define them)
• Some space should be added below those pedal signs, to prevent clashes with the staff below (in my case first violins)
• “Una corda” and “Tre corde” should be added to the piano pedal palette
• Please enable much slower arpeggios: in slow movements you would like them to be slower, and the current max indication is “2”; increase this value
• Please enable manual breaks inside a measure: if you have a very long “ad lib.” phrase with grace notes, you would like to easily break the measure, without creating artificial and irregular measures (with painful cut-and-try) to feed in a page
• Trill playback should be improved (it would be interesting for instance to add a knob to tune their speed, including accelerando and rallentando), and grace notes after a long trill are generally ignored
• I also work for a living composer, who has very complex music, and one great improvement with trills would be to add, as a grace note between parentheses, the second note (which can be above or below the main one): interval indication (major or minor second, etc.) is often insufficient. I manually add those grace notes, but of course, their playback is incorrect, and it is tedious…
• As I said, sounds are excellent; please add spiccato for chords. Also in their articulation palette, “arco” would probably be more useful than “normal”
• The coloured subdivisions of measures are a major improvement; perhaps CTRL + mouse to stick to a subdivision would drastically ease the vertical positioning of hairpins, “cresc.”, etc.
• It would also be interesting to add a flag on parties to show or hide them at the very beginning of the score: in this work, there are only a few measures at the end of the first movement where cellos are split (first half being in arco, second half in pizz., so you cannot put them in the same staff); I had thus to create a second staff for cellos, which should not appear at the beginning, contrarily to other instruments, even if they appear later in the movement
• Another wish, in particular for people working for contemporary music, would be to consider horizontal direction as absolute time (in seconds), enabling you to superimpose vertically in the same amount of time different time signatures for various instruments. Another way would be to enable superposition of different time signatures for different instruments, with different speeds (so that, after some time, you recover a vertical alignment). I understand this is a rather specific topic, but as Finale is now more or less abandoned, I am afraid that MuseScore will become the reference tool for living composers (I never used Sibelius). I don’t know what the reaction of music editors will be, who were – at least in France – very often asking for Finale native files.

Et un raton laveur ! (for non-French speakers, please refer to Jacques Prévert’s “Inventaire” poem!).

So, in conclusion of this long post, “Long and successful life to MuseScore!!!”.

Thank you very much for your enthusiasm and quality!

Pascal Garin


Comments

User here.
My understanding is that Finale will no longer be developed. Does that mean that your version will no longer work? Or just not be updated any more.
I can't get slurs to crash no matter how I manipulate them.
Arco and pizz are in the Text palette. I prefer them to the Staff Text option.
There is a setting to hide staves that don't have notation. They will show when there is notation.
C+P is indeed a problem. I suppose if you prepare the paste area first, that might help.

I have an older copy of Sibelius. Play back is better in MuseScore in some respects, but not in others. Sibelius UI does much, much more than MuseScore.
One good thing and bad thing with MuseScore is that there are so many updates that are not backwards compatible.

In reply to by bobjp

Dear anonym user,

Thank you very much for your rapid feedback.

I agree with most of them. Since the creation of the staff text palette, I use it, but you are right: pizz. and arco are in the text palette.

With respect to slurs, I have systematic crashes when I have one over two piano staves, and I must untick the self-placement option to position it appropriately (phrase passing from left to right hand). Their handles work well but moving the whole slur does not work.

I also agree with hiding instruments, but I think you cannot select the ones you want to show at the beginning from the other ones you don't want to see (perhaps am I wrong).

Unfortunately, preparing the staves before copying another score is not really efficient (although boring). In any case, this long-lasting bug must be corrected: it is too important.

Thanks again for your time,
Pascal Garin

In reply to by Pascal Garin

"With respect to slurs, I have systematic crashes when I have one over two piano staves, and I must untick the self-placement option to position it appropriately (phrase passing from left to right hand). Their handles work well but moving the whole slur does not work."

I find the best way to handle those cases is to write the whole phrase on one stave, add the slur and use cross staff notation to move part of the phrase to where it really belongs, on the "other stave". The slur goes with it and the shape can even be adjusted to be S shaped if you wish.

S-Slur.jpg

In reply to by SteveBlower

Dear Steve,

Thank you very much for your answer. I also did that but have nevertheless some crashes (perhaps due to the length of this score). Attached is an example.

I also understand from frank Rose, who also kindly answered to my long post, that this issue has been solved in the coming 4.4.3 version: let us cross the fingers!

But for my point of view, the main concern remains the copy/paste bugs.

Kind regards,
Pascal Garin

Attachment Size
Slurs.png 309.1 KB

In reply to by dj frank rose

Dear Frank,

Thank you for your comments (I will wait the official release of MuseScore 4.4.3). With respect to zooming, you just press CTRL key while rotating your mouse wheel: it is immediate and, as I said, particularly reliable. To navigate in a long score is thus much easier.

Hope this helps.

Regards,
Pascal Garin

"I had thus to create a second staff for cellos, which should not appear at the beginning, contrarily to other instruments, even if they appear later in the movement"

It is possible to define this "Do not appear at the start of the score" as a property of a Cutaway stave.
Right-click in the stave to get the popup Stave/Part Properties dialogue, and enable these properties for your Cutaway stave (cello divisi line):
Hide when empty = Always
Cutaway checkbox = enable

In addition, these are the general score options which you need to set:
Format > Style... > Score > Hide empty staves within systems = enable
Format > Style... > Score > Don't hide empty staves in first system = enable
Cutaway_example.png

Cutaway staves are explained in some detail in the Handbook section Showing staves only where needed
https://musescore.org/en/handbook/4/showing-staves-only-where-needed

Attachment Size
Cutaway_stave_example.mscz 42.85 KB

“Una corda” and “Tre corde” should be added to the piano pedal palette

I also can't find them in the master palette. I'm gonna open an issue, this is a huge lack.

Do you still have an unanswered question? Please log in first to post your question.