Entering feature-freeze for MuseScore 4.2
Hi everyone,
We’re about a month away from the release of MuseScore 4.2, which means that now is a great time to help test all the fantastic new features that will be included in this release:
Guitar
- Support for alternate string tunings
- All-new system for inputting bends and customising their playback
- Bend playback currently requires SoundFont or VST. We’ll update this post when support for bends is added in Muse Sounds.
Parts
- Better synchronisation between the score and the parts
- Ability to exclude certain elements from the score or the parts
Harp pedal diagrams
- Support for glissando playback with correct enharmonics
Engraving
- Support for arpeggios spanning voices
- Options to place ties ‘inside’ or ‘outside’ of notes and chords
- Various other fixes (see list)
Accessibility
- 6-key Braille input via the Braille panel
Mixer
- Ability to choose specific sounds within a SoundFont
Import/export
- Support for Music Encoding Initiative (MEI) format
- Various MusicXML fixes and improvements
Share to Audio.com
- Ability to update existing audio
- Option to publish to MuseScore.com and Audio.com at the same time
Performance
- Optimisations for note-input
To test these features, simply head over to the nightly builds page and download the latest build for your platform. On Linux and macOS, you can run the nightlies like you run the regular program. Windows users have a choice of using the portable .paf.exe
(simply download and double-click it), or the .7z
compressed archives (extract these with 7zip, then double click on MuseScore4.exe
inside the bin
folder).
If you find something buggy, please report it on GitHub. As always, please check first that the issue hasn’t already been raised.
We have now entered a feature-freeze, meaning that no new features will be added to 4.2. However, we will continue to fix bugs throughout this period, so it’s worth checking you have the latest nightly build before you report any issues.
We will release an official ‘beta’ for 4.2 shortly, but this is mainly to test the installation and release processes. Do check out the beta when it lands, but for bug testing it’s best to stick to nightly builds as these will be updated continuously.
Thanks all, and happy bug-hunting!
The MuseScore Team
Note for plugin authors: if your plugin uses the TextField
component from QtQuick.Controls 1.0, please replace it with the TextEdit
component from QtQuick.Controls 2.15 (or from QtQuick.Controls 2.2 if you require compatibility with MuseScore 3). See issue #19326 for details. Thanks!
Comments
This is cool!
I expected it to be released in December, and that's right. Considering many situations, it is expected to be released in late December (the last week after Christmas).
Has the Dynamics updated mentioned in this post https://musescore.org/en/node/354177 been postponed? I was really excited for that; is there any update as to when that will be released?
In reply to Has the Dynamics updated… by messiahsmiley
You can track progress on V 4.2 here https://github.com/orgs/musescore/projects/27
And see in particular https://github.com/musescore/MuseScore/issues/13326 which has status = "Done".
In reply to You can track progress on V… by SteveBlower
Rather as "not planned"
In reply to Rather as "not planned" by Jojo-Schmitz
I thought I had deciphered how Github statuses worked. Obviously I haven't mastered it yet.
In reply to I thought I had deciphered… by SteveBlower
It points to https://github.com/musescore/MuseScore/issues/19137 which is still open
In reply to It points to https://github… by Jojo-Schmitz
What should I understand from this then?
In reply to What should I understand… by SteveBlower
https://github.com/musescore/MuseScore/issues/19137 is on the 4.3 milestone now so it's targeted for version 4.3.
In reply to https://github.com/musescore… by RobFog
That sounds good news, but apart from reading RobFog's post here how could I find that myself? If I look at Github Issue 19137, I don't see anything that tells me it is on the 4.3 milestone.
In reply to That sounds good news, but… by SteveBlower
Here:
In reply to Here: [inline… by RobFog
Aha!
I had to click on the "i" in a circle next to the comment button (my first guess for the purpose of that "i" was that it would tell me something about adding a comment) and then I had to enable "New Projects". A bit of a treasure hunt!