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.0as 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!
In reply to The update on Muse Hub will… by shoogle
The 4.4.3 update is now available on Muse Hub.
In reply to The 4.4.3 update is now… by 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
In reply to Hi there. I used the test… by 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?
In reply to This update is great, but it… by Kid Cass
It never was, as a standalone m, as far as my can tell
In reply to It never was, as a… by 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.
In reply to It was, at least in… by 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.
In reply to I have just updated to 4.4.3… by SteveBlower
Has m been used as a separate dynamic mark before MuseScore Studio? How is r, s and z played back?
In reply to Has m been used as a… by Magnus Johansson
Jojo - your own post from over 4 years ago https://musescore.org/en/node/305631
In reply to Jojo - your own post from… by 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?"
In reply to Jojo - your own post from… by rothers
So it is not a dynamic by itself, but works upon the previous one
In reply to This update is great, but it… by Kid Cass
I have this exact same issue!
For those who don't know that the m "Mezzo" Dynamic Marker does, it restarts the Dynamic value of an instrument to the default one that an instrument has, before placing any other Dynamic Marker such as p, f, etc. It has a significant effect on mallet instruments while using MuseSounds.
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.
In reply to Thank you Community, Could… by 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!
In reply to Consider my suggestion for… by MichelCA
You can have that today already (and ever since), by creating new scores from a copy of the same score.
In reply to Consider my suggestion for… by 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
In reply to Hej! Im working in latest… by Bjarke Langkjaer
Known issue, already reported, see https://github.com/musescore/MuseScore/issues/25321#issue-2615915876.
In reply to Hej! Im working in latest… by Bjarke Langkjaer
Workaround seems to be to readd the shortcut
In reply to Workaround seems to be to… by Jojo-Schmitz
Thank you. It works when you define it again.
Sorry...
Hello!.. I simply want to express my concern about a change I believe it happened on this update; v4.4.3, or the previous one; v4.4.2. I am not certain of when did this change happen, but it comes out as stated next:
The "m" Dynamic Marker, which I believe it is for "Metzo" or Medium is broken now and has no effect, it would usually reset the instrument's Dynamic to the default value when using MuseSounds Instruments Library (As how it would sound like a middle point Dynamic in the Playback, before adding any other dynamic like p, mp, mf, f, etc.) which I really use a lot on my Music in order to get the best Playback results. However, now the "m" Dynamic Marker simply doesn't has any effect since the last Update. That implies most of my Playbacks are going to need a Rework, because the Dynamics I intended for instruments such as Marimba or Xylophon are now going to use either "mp" or "mf" Dynamics...
This means that they're going sound too quiet or too loud from the Dynamic I used and worked for the Timbre I had intended them to sound in the Playback, and as someone who really cares about detail, this little inconvenience really sets me down...
My question is: Was this change intentional or simply an oversight that needs to be patched? If so, I'd love to hear that this is reverted as how it was initially, I'll leave an example of my Music below.
Than you very much for reading, I really appreciate the work you are doing for this amazing Software, and I'm ears up for any sort of help or input!!
In reply to Hello!.. I simply want to… by cactusowoceo
Patch of mezzo dynamic planned in version 4.5: check https://github.com/musescore/MuseScore/issues/25309#issue-2613881180.
Having issues with velocities and dynamics.
If there exists a dynamic marking already eg. the beginning, and the velocity of a note gets changed, the note will now have that velocity as an absolute velocity and no longer is affected by any dynamics/volume modifiers.
This persists even after clicking reset velocity on the note. The only way to fix it, from what I've found, is to enter 0 for velocity to reset it to 64, or delete the affected notes and place them again. Steps to reproduce are in the test file.
I'm pretty sure it was this update, but on Mac pressing "T" does not enter a tie anymore.
In reply to I'm pretty sure it was this… by dre7
Yes, some Mac users are finding they need to go to Preferences / Shortcuts and reset that shortcut also a couple of others. It appears another update will be coming soon to address that and a couple of other minor inconveniences.
In reply to Yes, some Mac users are… by Marc Sabatella
There's also a playback issue, which I don't believe 4.4.3 addressed:
When I leave the application (MuseScore 4) open, and my computer sleeps or I close the lid, and reopen it, the sounds won't play as I select the notes or press space. Hopefully this can be fixed.
(A quick fix I have noticed for this, without having to restart the application, is opening Preferences > Audio & MIDI, and change the Buffer Size—then they do sound in playback.)
Thank you
In reply to There's also a playback… by dre7
What you are describing shouldn’t happen And doesn’t for most users. Sounds like your OS is changing the device ID’s upon waking and not informing all applications of the change. Are you perhaps connecting or disconnecting some while the computer sleeps? See if you can find a setting in your OS to control the behavior in terms of assigning device ID’s, either globally for the system or maybe specific to the audio device you are using with MuseScore.
In reply to What you are describing… by Marc Sabatella
I'm just using the speakers on a MacBook Pro. I did create an IAC Driver in the past (but didn't know much about what I was creating) and am not sure how to delete it.
I just unchecked "Device is online" in the driver's properties. I expect this might solve the problem.
In reply to What you are describing… by Marc Sabatella
It turns out putting that IAC Driver offline also didn't work.
I remember user @bobjp had similar issues with the playback, and that he said that he also has to close the application each time and reopen for the notes to play.
I turned up Buffer Size to 2048. Audio device is 'MacBook Pro Speakers' but maybe I'll just choose 'System default'...