MuseScore 4 Update: Announcing our Beta Release!
Today, we are delighted to announce the Beta release of MuseScore 4! The links below are for our new Muse Hub installer application, which can be used to install and update MuseScore and download / install our new orchestral plugin Muse Sounds. See the bottom of this post for more information and help with Muse Hub installation.
Note: For the beta release, MuseScore must be installed using the Hub for Muse Sounds to work
Linux users will need to install MuseScore 4 separately. Here are the links to install the beta release directly:
Please note that the Muse Hub is not yet working with screen readers. For those wanting to download a version of MS4 directly, please use these builds. Please note that these builds do not work with Muse Sounds.
Known Issues for MuseScore:
We have tested the Muse Hub on various Linux distros but are expecting issues with others. For those experiencing problems with any aspect of the Muse Hub on Linux, please log your issues on the MuseScore GitHub: https://github.com/musescore/MuseScore/issues
There are some remaining performance issues with Muse Sounds. For example, with larger scores, playback may sometimes take a few moments to 'catch up' after you press the play button. You may also experience lag and dropouts. If so, please first try going to preferences > I/O and setting the buffer size to 2048. If you still experience problems, please log your issues on Github (link below).
When saving a score privately to MuseScore.com, it can sometimes get marked as a public score
When using Muse Sounds, audio feedback during note input can often be marred by delays, stuttering or repeats. This does not occur during playback
Some instruments are mapped incorrectly to Muse Sounds. Bear in mind that Muse Sounds does not cover the entire instrument list anyway, so many niche instruments will simply revert to MS Basic.
Piano pedal markings are not producing sustain effects reliably for Soundfont, VST and Muse Sounds
Features added in Beta
- Our new orchestral plugin, Muse Sounds
- Saving to cloud on MuseScore.com is now working
- An improved system for publishing to MuseScore.com
- A simple toggle for switching between playback profiles (MS Basic and MuseSounds)
What else is in MuseScore 4?
An entirely new interface
- 400 new icons
- customisable colours
- A new Home tab which includes recent scores, plugins and video tutorials
- A new, friendlier onboarding process
An engraving overhaul
- New system for horizontal spacing
- New system for slurs and ties
- New system for beaming and cross-staff beaming
- New, heavily revised version of Leland and Leland text
- System objects can appear on more than one system (although this is currently only available on certain templates)
- Hundreds of other smaller fixes and optimisations for lyrics, articulation placement, tremolo marks and general positioning
- For a more comprehensive explanation of the engraving changes in MS4, please see this document. https://musescore.org/en/node/330793
Multiple workflow improvements
- The Properties panel (formerly the inspector) is now much more responsive, easier to understand and filled with lots of useful options
- The capabilities of the note input bar have been expanded and the toolbar itself is now much easier to customise
- Customisable 'Tempo Lines', (accel, rit, etc.) that work with playback
- Scrollbars on the score
- Parts are easier to discover, edit and alter (using the new 'Instruments' panel)
- The experience of setting up a new score has been simplified to be more welcoming to new users
- Improved instrument definitions
- A new tuplets toggle
- New articulation buttons
- A new toggle for cross staff beaming
A new mixer
VST instruments and effects support
- Please note that we will be building additional tools, like automation and MIDI mapping in later releases, once MS4 is out
- A new keyboard navigation system that follows best practices to allow users to quickly move around the interface
- Improved screen reader support (in particular, we really need people to test and provide feedback on this)
- An editable high contrast mode
- We strongly prefer issues to be reported on GitHub until we release MS4 (this requires a GitHub account): https://github.com/musescore/MuseScore/issues
- Alternatively, you can submit any issues you find on our issue tracker: https://musescore.org/en/project/issues/musescore
The largest changes we have made have been to playback - a technical investment we decided to make now. It is the sole reason why the timeline of MuseScore 4 was extended beyond 2021. Once you hear Muse Sounds, you'll understand :)
- The audio engine in MuseScore 4 is completely new
- There is an entirely new playback events system, which can produce much finer and detailed instructions. These translate to both MIDI and also MIDI 2.0 (which will be advantageous once MIDI 2.0 libraries and products start to become available). The advantages of this system will be properly realised once our new orchestral library, Muse Sounds is ready (in the Beta release).
- It is also worth mentioning that we have not been able to carry over the systems for mapping and prioritising sounds from MS3. There are two reasons for this: the first is that it is quite technically incompatible with our new system. More importantly, it is not a universal system that could also work with VST. As a result, our highest priority for MuseScore 4.1 is to reintroduce universal systems to allow users to assign sounds to articulations and text instructions. We will also be adding other types of standard VSTi capabilities too, including key switches and automation.
- We anticipate that there will still be issues with various different VST plugins. We would greatly appreciate it if you would submit any issues you find
- Please note that when first loading MS4, there is an option to download Muse Sounds. This option will not work until the Beta release
Incompatible features we will re-introduce in later releases
- There are other features that have not played nicely with our new systems at all, and which will need to be replaced in later releases, namely: the plugin creator (which we want to rewrite completely as a priority), the score comparison tool and the 'Documents side-by-side' feature.
Muse Hub Troubleshooting
- If you find that the downloads aren't starting:
- You may need to reinstall the helper application. Right click on the HUB logo and choose "reinstall helper". You may then need to restart the hub itself as well.
- Make sure you're connected to the internet and have access to the web
- If Muse Hub fails to start
- Check your version of macOS or Windows
- Check you have permission to run apps on your OS
- Check macOS Gatekeeper security settings to ensure that you are allowed to run apps from the App Store and Identified Developers.
- On Windows, you may need admin permissions to install the Hub depending on your security policy
To uninstall the Hub
- On macOS, trash the application from your Applications folder
- On Windows, use the Apps & Features page from Windows Settings to uninstall the Hub
- On Linux, use Software Manager to uninstall the Hub.
Known Issues with the hub
- Changing language requires a restart of the app
- You may experience slow download speeds as few Hubs will be online initially. We are adding additional web seeds to help speed up testing.
- MuseScore must be restarted to detect newly installed Muse Sounds and MuseFX
- Language translations are machine translated; there may be translation errors that need correction.
- Project files downloaded from the inspiration page have a machine-generated filename