MuseScore 3 features not implemented in MuseScore 4

1 maand geleden bijgewerkt


    • This list is a work in progress. Some of these features may be implemented before 4.0 is actually released. Others are already planned for a post MuseScore 4.0 release, although there may be a new design.
    • Some might even exist but in a different form that those of us accustomed to MuseScore 3 have not discovered yet.
    • The MuseScore 4.X Github project page tracks features that will be implemented post MuseScore 4.0.
    • The release announcement for the latest MuseScore 4 development milestone gives a high-level indication of features not in the current development build, but expected to be implemented before MuseScore 4 reaches General Availability. Current milestone as of Aug 10, 2022: MuseScore 4 Alpha.
    • This list is organized by general topic area, and within each topic area, are sorted more or less by priority.


    Playback of invisible instruments

    • Currently, setting an instrument invisible forces it to also be muted, with no way to override.
    • There is a simple solution, though - set the staff to be invisible instead of the instrument. Which is often preferable anyhow, since many use cases for invisible staves for playback have them paired with a visible staff for notation. So mostly, it will just be a matter of re-education.
    • The biggest issue will be import of existing scores that rely on this.
    • There is an open issue on this -
    • There is an open PR to convert invisible instruments into invisible staves on import -

    Selecting sounds within SoundFonts

    • The Mixer in MuseScore 3 allows you to select, for each instrument, which sound is used. Thus, if your SoundFont has 12 different piano sounds, you can select which one gets used. Or, if your SoundFont isn't General MIDI compatible, this is how you'd tell MuseScore where the flute sound is, etc.
    • In MuseScore 4, there is no such control. You are stuck with the default General MIDI assignments, so only the default sound for an instrument when using a General MIDI SoundFont, and no way to tell MuseScore how to find the various instrument sounds at all if you are using a non-GM SoundFont.
    • At one point there was a proposed design (on Discord?) for how this selection might work- a multilevel selection scheme when selecting the SoundFont within the Mixer, kind of like how submenus work. Seemed very clean and could be implemented with no real changes to anything else in the UI.

    Velocity controls not working

    • MuseScore 3 allowed you to set velocity of dynamics, and of individual notes (for instruments not using SND)
    • These controls are present but non-functional in MuseScore 4
    • It seems likely that these will be fixed, but only in a much more limited fashion than MU3
    • See

    Tuning controls not working

    Guitar bends not working

    Independent muting of staves / voices

    • The MuseScore 3 mixer had controls to allow you to mute individual voices and individual staves of an instrument
    • These controls are missing in MU4, with no obvious workaround

    Independent control of subchannels

    • Currently, in MuseScore 4, there is no way to independently control the different subchannels for instruments that produce different sounds, like violin (arco & pizzicato). So the relative volume of arco and pizzicato is controlled entirely by the soundfont, not by the user.

    MIDI and other controls for staves in mixer

    • In the mixer, setting up the MIDI port and channel, color, and muted voices is no longer possible. The MIDI channel there also controlled assignment of channels in MIDI file export, thus right now, creating MIDI files with specific channel assignments is not possible.
    • For some details and an image of the missing controls, see forum post Musescore 4: Where have all the ...MIDI controls... gone?.

    MIDI mapping

    • Mentioned as missing in announcement MuseScore 4 Update: Alpha 2 is now released!, section "VST instruments and effects support"
    • Not clear if this actually includes anything not already listed above. There was a MIDI tab in the staff text properties dialog, but it may not have ever been functional.


    Piano Roll Editor

    • This is expected to be redesigned and reimplemented for MuseScore 4.x.

    Audio device selection

    • There are some high-level controls for selecting audio devices, but lower-level controls a la MuseScore 3 are not necessarily planned. It remains to be seen how much of an issue this turns out to be in practice.

    Capo playback

    Zerberus SFZ Synthesizer

    • Not planned; people wishing to use SFZ files will hopefully be able to use VST players.


    User Text Styles missing in Properties tab

    Fix to line

    • MuseScore 3 had a facility to force notes of any given pitch to display on a specific staff line. This is used for a wide variety of purposes, including customizing slash notation, notating string harmonics, handling clef changes within cross-staff notation, differentiating multiple voices under ottavas, suppressing visibility of ledger lines, and other more esoteric but not completely off-the-wall use cases.
    • Currently, there is no plan to bring this functionality back - instead, the hope is to come up with native ways to handle each of the different use cases.
    • See

    Hook settings

    Verse controls

    Other functionality

    Advanced workspace

    Apply current palette element command

    Zoom to page width command

    • Currently not implemented, but should not be difficult.

    Ctrl+click to select overlapping elements

    Plugin Creator

    • This is expected to be redesigned and reimplemented for a post MuseScore 4.0 release.

    Plugin API

    Score comparison tool

    • The UI would need to be updated to work with MuseScore 4 but presumably, the underlying code would still be usable.

    Split display

    MIDI import panel

    Image capture tool

    • This feature has not been implemented in MuseScore 4.0 but is on the list for a post MuseScore 4.0 version. It is an important feature for educational uses.

    Language switch

    Shortcuts for Key Signatures, Time Signatures, Symbols

    • Shift+K, Shift+T, and Z are non-functional. You can access controls via View / Master Palette, so, Shift+F9 followed by K, T, or S.

    Shortcut for elision

    • Ctrl+Alt+- was added as the shortcut for the elision character in 3.6, relevant especially for lyrics, but this was not fully ported to MuseScore 4.

    Stacking order

    • MuseScore 4 provides useful controls to send forwards / backwards / to front / to back but lacks direct control over the stacking order of MuseScore 3, which allowed for precise setting of values for custom elements you want to resume in multiple places in a score.
    • Something that will be missed by advanced users mostly.

    MuseScore Drum Line (MDL)

    • Will not be available for MuseScore 4.0 since MDL depends on the Zerberus player.
    • The plan is to add a much nicer sounding version of drumline in a post MuseScore 4.0 release.

    Features not present in MuseScore 3

    These are features that were either removed prior to MuseScore 3, or implemented afterwards but never part of any official release, that are worth noting here.

    Multimeasure repeat playback


    • Feature was removed during the transition from MuseScore 2 to MuseScore 3.
    • It was mostly reimplemented for MuseScore 4 as a GSoC project that was never merged.
    • It is expected to be redesigned and reimplemented for a post MuseScore 4.0 release.

    Chord editor

    A GSoC project never merged.