Release notes for MuseScore 3.3 Beta Update (September 17, 2019)

Updated einem Monat ago
Build number Date Announcement
macOS 10.10+: 3.3.0.23686, Windows 7+ (32 and 64-bit): 3.3.0.8331, AppImage: 3.3.0. (revision: b45221c) 2019-09-17 https://musescore.org/en/3.3beta2

Improvements

  • Various accessibility improvements
    • Made more elements available for screen readers
    • Improved the information interpreted by screen readers

Fixes

  • "Single palette" option was not implemented
  • Palettes appearance was broken and wasn't aligned with the MuseScore styling
  • Dark theme was not correctly supported in new palettes
  • Note value repeat section: setting "Never" was broken
  • Undo didn't restore a deleted frame
  • NVDA screen reader didn't work

Complete list of issues resolved

Here is a complete list of the issues resolved in this update:

Layout and automatic placement

  • #288169: Line drawing does not work when 90 degree T hooks are combined with another hook.
  • #294297: Cross-Measure Beam Custom Position Not Restored

UI/UX

  • "Single palette" option was not implemented
  • Palettes appearance was broken and wasn't aligned with the MuseScore styling
  • Dark theme was not correctly supported in new palettes

Commands/Properties

  • #293897: [Tablature] Note value repeat section: setting "Never" broken
  • #293707: UNDO does not restore a deleted frame
  • #289374: Tuplet numbers: Follow staff size not working

Corruptions and/or loss of data, crashes

  • Fix crash related to new palettes initialisation. The crash occasionally happened when running MuseScore 3.3 Beta.
  • #291969: Crash on load of score with staff type change on measure 1
  • #293894: Crash on next-element when editing fingering with user text style
  • #294120: Insert measures in mmrest mode leads to corruption/crash
  • #294156: Incorrect segment type for fermata
  • #294010: Hanging on startup

Accessibility

  • #292510: Accessibility navigation skips frames
  • #293671: Screenreader should read staff name in addition to number
  • #293169: Screenreader fails to read accidentals in key signatures and notes without explicit accidental
  • #293300: Optimize screenreader info information during score navigation
  • #292928: Scrolling among staves with keyboard shortcut
  • #293971: I cannot use tempo marking in NVDA
  • #294237: Accessibility: don't read staff text and other extra info for each note of chord

Miscellaneous

  • Update Qt version for Windows builds to Qt 5.12.5
  • #294125: Tooltip / screenreader feedback for "space" on Special Characters palette is noteLongaSquareDown
  • #294006: Symphony Orchestra template has wrong patch for pizzicato
  • #293981: double ampersand in palette names