MuseScore Studio 4.4.3 is now available!
Hi everyone,
We're pleased to announce that MuseScore Studio 4.4.3 is now available.
This update addresses multiple crashes and resolves various issues related to interaction, playback, and engraving. Additionally, it includes a critical fix for Windows users, resolving several graphical problems.
Windows Qt 6.2.9 update
In this release, we're switching to from Qt 6.2.4 to Qt 6.2.9 on Windows. This resolves a number of issues:
- Graphical issues of various natures, for example where the main window looked transparent (#24857, #24579)
- Popups appearing on the wrong monitor or not at all (#24232)
- Problems in certain older dialog windows, such as the Format > Style, directly after changing the accent color (#24667*)
- A crash when opening and closing the Mixer panel very quickly (#23505*)
- Unexpected score dragging when double-clicking an instrument name to open the Staff/Part properties dialog and then clicking Replace instrument (#24613*)
Issues marked with * also occur on other platforms than Windows, where we could not yet apply the Qt update; on these other platforms, these issues will be fixed in MuseScore Studio 4.5.
Stability fixes
Crashes were fixed that occurred when
- joining measures (#25257)
- opening a score with a hidden staff containing grace notes whose beams were modified (#24862)
- opening some specific scores (details not known) (#24802)
- using the on-screen piano keyboard or an external MIDI device with percussion instruments (#24679)
- hiding staves containing Voltas or similar objects under certain circumstances (#24657)
- dragging slurs (#24726)
- adding title text to certain scores (#24795)
- deleting staves and then selecting a tie (#24841)
- opening the Measure properties dialog using a custom keyboard shortcut (#19425)
- when opening part scores in some files (#25192)
Score interaction fixes
- Entering notes in voice 2, 3, or 4, at a rhythmic position that overlaps with an existing note in the same voice, no longer corrupts the score (#24809)
- Problems with dragging/resizing images, frames, and tuplet numbers were fixed (#24791, #24608, #24738)
- Lyrics text styles are now also applied when moving to the next syllable (#24742)
- Slurs can be extended to the next system again using Shift+Right arrow (#24803)
- Staff/system text can now be dragged from the Palettes onto multi-measure rests again (#24758)
File saving/reopening fixes
- On small staves, modified stem lengths are now correctly preserved again (#25004)
- Hairpin height is now preserved again when closing and reopening a file (#24737)
Text layout fixes
- For lyrics, the placement of dashes between syllables has been changed back to match the behaviour of MuseScore Studio 4.3.2 and older (#24621)
- The vertical placement of lyrics above the staff has been fixed (#24549)
- Extender lines no longer unexpectedly extend to the end of the score (#24519)
- The sizing of Segno and Coda symbols has been reverted, so that they now follow the font size again (#24330)
- When using the MuseJazz style, Segno and Coda symbols no longer have a frame around them (#24899)
Other engraving fixes
- Enabling pitch name note heads via Staff/Part properties > Advanced staff properties no longer causes augmentation dots to disappear (#24610)
- Dynamics centred between staves no longer interfere with harp pedal diagrams (#24225)
- Vertical alignment of tempo markings and gradual tempo changes now also works when multi-measure rests are enabled (#24738)
- The minimum tie length setting is now respected at the beginning of a system also if it starts with a forward repeat (#21667)
- When using the experimental "Display note values across measure boundaries" option, no more spurious stems are rendered for whole notes (#24717)
- The "Show first" setting in Style > Bar numbers" is now respected again after section breaks (#24809)
Playback fixes & improvements
- The niente dynamic now works as expected (#22812)
- Hairpins in combination with compound dynamics (e.g., fp) now produce better playback (#24569)
- Audio devices with more than two channels are now supported on Windows too; the first two channels will be used, i.e. stereo audio is produced (#17648)
- Fermata durations are calculated correctly again (#24852)
- Newly added parts are now muted as expected in existing part scores (#24985)
- The playback cursor no longer disappears when switching between the Score and Publish tabs during playback (#24769)
MusicXML import fixes
- MuseScore Studio failed to parse XML files containing comments in certain locations; this has been resolved (#24704)
- Accidentals in chord symbols are now imported correctly from MusicXML files created by Cubase (#24865)
- Various issues around ottava markings have been fixed (#24729)
- The import of ties under certain circumstances has been fixed (#24620)
Accessibility improvements
- Screen readers now announce the group name when navigating between menus on Windows and Linux (#24151)
- Orca properly announces pressed shortcuts in the Preferences > Shortcuts > Define shortcut dialog on Linux (#22637)
Miscellaneous fixes
- The Linux AppImage now contains
libopengl.so.0
as a fallback library, which should enable it to run on systems where this library is not installed by default - MEI export of invisible rests has been fixed (#25106)
- In some templates, the instrument numbers were fixed (#25046, #25124)
- Some issues with (custom) keyboard shortcuts on macOS were fixed (#24177, #24938)
Facilitating fixes in third-party distributions
While we are not responsible for distributions of MuseScore Studio via FlatHub or OS-specific package managers (most relevant on Linux), we are happy to accept changes that facilitate fixes in such distributions:
- On distributions where MuseScore Studio is built with Qt 6.5 or higher, the menu bar and the Home/Score/Publish toolbar were missing; this has been fixed. Thanks GitHub users @Vogtinator and @kbloom for the fix! (#24097)
- A case of undefined behaviour that led to an assertion failure on certain distributions has been fixed; thanks @Orivej! (#20878)
A known issue on distributions that build with Qt 6.5+ is that the Mixer panel, or any other dock panel, fails to open, because the version of KDDockWidgets that MuseScore Studio uses is not compatible with such Qt versions. This is tracked at #24866, and will be solved in MuseScore Studio 4.5.
Get involved!
We would like to thank everyone who helped us making this release possible, either by contributing fixes, or, also importantly, by testing pre-release versions and reporting their findings.
This was the last release in the 4.4 series; the development of MuseScore Studio 4.5 is already in full swing! If you ever find yourself bored waiting for the next update, you could consider contributing to MuseScore Studio yourself. For example, you can help translating MuseScore Studio into your own language, or if you know a bit about programming, you can consider fixing an issue yourself. See this page for more information: https://github.com/musescore/MuseScore/wiki/Contributing
Soon, we will be back with an announcement about the Handbook for MuseScore Studio; and we're planning to post an update about MuseScore Studio 4.5 and beyond. Stay tuned!
Comments
The update on Muse Hub will go out later today. We'll post here when it's ready.
Also, we've created a Code of Conduct for ourselves and the contributor community: https://github.com/musescore/MuseScore/blob/master/CODE_OF_CONDUCT.md
Want to suggest new Muse Sounds? We have a survey here: https://po415hli6k2.typeform.com/to/U5GjYgOm
Thanks!
Antwort auf The update on Muse Hub will… von shoogle
The 4.4.3 update is now available on Muse Hub.
Antwort auf The 4.4.3 update is now… von shoogle
Hi there. I used the test version 4.4.3.242921234-x86_64.msi . I am thrilled to be able to use Musescore again! All functions worked. This is the first fix that I've been able to open and use. I finished a big band score. While everything worked, it stalled often. I am using windows 11. NOT FOUND: Thinking About Pharoah Sanders -big band score.mscz
Antwort auf Hi there. I used the test… von Frank Southecorvo
here is the file
Thank you very much!
This update is great, but it caused a new problem. Now, the mezzo dynamic doesn't do anything, and notes play as whatever the last dynamic was before it. There were a few compositions that required the mezzo dynamic as the right middle ground between mezzo piano and mezzo forte, and this didn't happen in previous versions. Did something change with this update? Is mezzo no longer functional?
Antwort auf This update is great, but it… von Kid Cass
It never was, as a standalone m, as far as my can tell
Antwort auf It never was, as a… von Jojo-Schmitz
It was, at least in MuseScore 4, and I used it frequently. It has a distinct sound from other dynamics, and to activate it all you had to do was add the m. Now adding the m doesn't change playback. I can't imagine why this feature would be removed.
Antwort auf It was, at least in… von Kid Cass
I have just updated to 4.4.3 and m is there in the More section of the dynamics palette.
It would be better to use the Support and bug reports forum https://musescore.org/en/forum/6 for things like this rather than cluttering up the announcement.
Antwort auf I have just updated to 4.4.3… von SteveBlower
Has m been used as a separate dynamic mark before MuseScore Studio? How is r, s and z played back?
Antwort auf Has m been used as a… von Magnus Johansson
Jojo - your own post from over 4 years ago https://musescore.org/en/node/305631
Antwort auf Jojo - your own post from… von rothers
Do you believe I am Jojo? Nevertheless, thanks for the link. It is worth reiterating the question from the post of it: "Are they [the separate markings m, r, s, z and n] familiar to the music community?"
Antwort auf Jojo - your own post from… von rothers
So it is not a dynamic by itself, but works upon the previous one
I love the enthusiasm and pace of MSS development. Kudos to all involved!
Thank you Community,
Could somebody over on the sound team check out the Muse Sounds dynamics for trombone? It's specifically the mf, mp, and p dynamics I'm concerned about. From experience, I believe these current dynamics should be bumped up a little to give a more honest sound, since when I score these instruments alongside other brass, it tends to not support itself; and trombones know how to hold/give support LOL.
Antwort auf Thank you Community, Could… von Jordan_Morrison
To make requests or submit bug reports regarding Muse Sounds, please use the appropriate support button within Muse Hub.
Consider my suggestion for musescore 4.5 to really be able to open templates with pictures, header and footer and names. It's really frustrating to do it from scratch every single time especially when you are transcribing or arranging for multiple customers, like me. Also I find it helpful if some composers are really creating a template for a set of pieces for example. Just bring this feature in the next update please!
Antwort auf Consider my suggestion for… von MichelCA
You can have that today already (and ever since), by creating new scores from a copy of the same score.
Antwort auf Consider my suggestion for… von MichelCA
Templates already support header and footer, since those are style settings. Not sure what you mean by "names", but if you mean instrument names, that is also part of the template. But images are considered content, not structure or formatting, and thus not currently part of templates. If you have a concrete proposal for how that could be addressed, be sure to open an issue explaining it, on GitHub.
Hej! Im working in latest update 4.4.3, and the shortcut for tie (shift+T) does not work on my Mac. It works when I use the symbol in the command line on top of the window, but not using the shortcut.
B.W. Bjarke Langkjær, Denmark
Antwort auf Hej! Im working in latest… von Bjarke Langkjaer
Known issue, already reported, see https://github.com/musescore/MuseScore/issues/25321#issue-2615915876.
Antwort auf Hej! Im working in latest… von Bjarke Langkjaer
Workaround seems to be to readd the shortcut
Antwort auf Workaround seems to be to… von Jojo-Schmitz
Thank you. It works when you define it again.
Sorry...