Release notes for MuseScore 3.3 (October 31, 2019)
This page shows old instructions for MuseScore 1.
For MuseScore 4 users, see Release notes for MuseScore 3.3 (October 31, 2019).
For MuseScore 4 users, see Release notes for MuseScore 3.3 (October 31, 2019).
Build number | Date | Announcement |
---|---|---|
macOS 10.10+: 3.3.0.24090, Windows 7+ (32 and 64-bit): 3.3.0.8737, AppImage: 3.3.0. (revision: 4761df6) | 2019-10-31 | https://musescore.org/en/3.3 |
New
- Complete palettes redesign
- Note Input workflow improvements
- Native support for Roman numeral analysis and Nashville notation
Improvements
- Chord Symbol Formatting not only for MuseJazz has been supported
- Symbols can be attached to barlines
- Multiple improvements to the Plugin API
- Implement changing palette and palette cell properties on fly
- Current workspace is automatically saved on each action that changes the workspace
- Palettes and workspaces can be reset to the default state defined by the workspace you started customisations from
- Improve algorithm for determining start point for note input
- Move the viewport to show actual changes in the score if they are outside of the current view
Fixes
- NVDA screen reader didn't work
- Various MusicXML Import/Export fixes
- Various fixes for the playback of tied notes, muted voices and notes being edited in parts
- Sticking was not linked between score and parts
- The presence of fretboard diagrams prevented input of chord symbols in other staves
- Loop playback was set incorrectly in parts
- Shortcuts navigation across the palettes was broken
- Palettes and palette cells were not translated
- It was impossible to enter successive sticking elements
Complete list of issues resolved
- MuseScore 3.3 Beta release notes
- MuseScore 3.3 Beta Update release notes
- MuseScore 3.3 Release Candidate release notes
- MuseScore 3.3 Release Candidate 2 release notes
- MuseScore 3.3 Release Candidate 3 release notes
- #296127: Can't use CMD+SHIFT+Drag to copy on Mac
- #296171: fix triggerLayoutAll() for spanners
- #296271: Crash by undoing/redoing in main score a copy-paste made in the parts