Feedback after a complex orchestra score transcription

• Jun 13, 2025 - 16:02

To the kind attention of MuseScore Studio developers.

I have been using MuseScore Studio intensively for about 2 years now, and I realize how impressive has been the progress of this tool.

Now with version 4.5.2, I have just finished the transcription, from a scanned handwritten manuscript, of a very complex contemporary full orchestra score. To give a flavour, I attach two pages (I can’t show more for confidentiality reasons) of the result with some tricky ideas (among many others, not attached here!):
• Desynchronized instruments for a few measures (main orchestra with quarter note at 84, first violin and first cello at 112), see measures 47 and following on page 3
• Tuplets across measures, see page 13 string parts

My first comment is that, despite the difficulty of such a work, MuseScore Studio is incredibly powerful, stable (I have a very powerful computer, and I did not have one single crash), versatile and rich. So, my first and main thought is to warmly congratulate and thank the development team who is making a fantastic job!

But…

I try to hierarchize my comments and proposals according to their importance (of course, this is a personal point of view).

Copy/Paste. This is obviously a weak point of MuseScore Studio:
• Impossible to paste music containing different time signatures
• Instrument changes are also not pasted, obliging you to carefully check all of them
• Notes inside tuplets are also difficult to copy/paste

Multistave chords
• Please enable multistave chords (without having to cheat on stems) with, for instance, the same keyboard shortcut as for single notes shift between staves: selection of the notes inside the chord and CTRL + SHIFT up or down arrow to change the notes staff

Ergonomics
• The ergonomics of MuseScore Studio is rather good
• Perhaps a better use of the mouse right click (for instance for formatting) would be useful (such as CTRL + right click, or something like that)
• I also wonder if the tessitura of an instrument should not be better attached to the instruments panel, rather than its staff (but I understand that, for multi-instruments staff this is more logic)
• The Appearance panel would better display the reset circular arrow, rather than the 3 dots (for instance for dynamics formatting)

Dynamics
• Please enable the addition of any dynamics to the corresponding palette (for instance fpp is currently lacking)

Tuplets across measures, tuplets in general
• I could see on the forum that this is a long-lasting request: please consider its implementation in a next version
• When a tuplet is split between two staves, please improve the tuplet indication positioning
• Please also enable tuplets such as 4:5 (I think that today, it is impossible)
• Please enable the horizontal positioning of tuplets lines and brackets (very useful for instance for multistave tuplets)
• Tuplets fractions should be treated as the dynamics signs (as they are now displayed in 4.5.2 version), with a white background: when they are above a line or a measure barline, the latter should be hidden behind

Time signatures
• Time signature at the top of a score is the natural way to display them when they are frequently changed. In such a case, it is unfortunately impossible to display local time signatures. Please enable it
• Surprisingly, it is not possible to select all time signatures at the same time in order, for instance, to properly realign them (in particular when they are displayed at the top), contrarily to most other items: please correct this lack

Individual parts
• This would be obviously a major update: to export, at native MuseScore Studio format, instrument parts with (cherry on the cake as we say in French), bidirectional interaction between individual parts and orchestra full score.
• But the possibility to export instrument parts and work on their individual formatting would be already a significant first step (if I am correct, today you can only export PDF, at A4 format, no other page size)

Playback
• When you listen at the music, please disable the computer sleep mode, to continue reading the score without interruption
• MuseScore sounds are excellent (and sometimes better than costly external sound fonts!). Please improve the dynamics playback, to make them more realistic (pianissimi for instance sound artificial and exaggerated: they sound as if you turn a knob, rather than playing softer)

Correction of bugs
• When you use a line with (opening and/or closing) brackets from the line palette, close the file and reopen it, a Ped. sign has been added, which you must remove after reopening (and afterwards it no longer appears)
• Similarly, the manual addition of a line with brackets in the corresponding palette fails (what is copied is not what you drag)
• More generally, a file which you reopen is not systematically exactly as you saved it
• Selection of time signatures: please enable it (see above)
• As I mentioned above MuseScore Studio is very stable when working; there is nevertheless a problem when the computer falls into sleep mode, where the software systematically crashes (not the case for Muse Hub)
• All fonts are not accessible for titles, etc. on Windows 11 platform, even if the fonts have been properly installed for all users (many questions on the forum on this question). I wonder whether it is not due to the Qt API that you use: please try to correct the bug. I know that the complete instruction "C:\Program Files\MuseScore 4\bin\MuseScore4.exe" --platform windows:fontengine=directwrite solves that bug, but it introduces other problems

Attachment Size
Leiho - Excerpts.pdf 218.49 KB

Comments

As you know, you will be asked to break this list down into individual topics so they can be properly discussed. Which is the purpose of the forum. Developers rarely are found here.

In reply to by bobjp

Thank you for your precious comment.

No, I did not know that this kind of post would not be useful for developers. So, as you suggest, I will break down this global post into individual comments/requests, hoping that they will be useful to the community.

Regards,
Pascal Garin

In reply to by Pascal Garin

Your extensive list is difficult to wade through. The way this works is like this: A user has a problem. They post in the appropriate forum. Another user often has an answer that takes care of the problem. There is input from other users. If a solution can't be found, a formal issue is created and posted on GitHub. This is often done by the person with the original question. GitHub is where the developers are. You shouldn't go there first because things need to be in a certain format. Most, but not all, problems users have are cleared up in the forums. You noted some things that people have asked for before. It is possible that most of those issues are already being looked at. But there is no timetable for when or if they will be fixed.
Good luck.
And this General discussion forum isn't quite the place for any of your topics.

In reply to by bobjp

Thank you so much, Bob, for this very detailed and useful information.

I now better understand the way it works, and the reasons for that.
It is probable that most of my concerns have been already tackled in one the forum topics, bit I will carefully check.

Have a nice day!
Pascal Garin

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