Release notes for MuseScore 3.3.4 (December 4, 2019)
| Build number | Date | Announcement |
|---|---|---|
| macOS 10.10+: 3.3.4.24412, Windows 7+ (32 and 64-bit): 3.3.4.9066, AppImage: 3.3.4. (revision: 7684abe) | 2019-12-04 | https://musescore.org/en/3.3.4 |
Fixes
- Palette names were scrambled and nearly impossible to read (Windows 7)
- Scale of palette was incorrect for high and low DPI displays
- Courtesy accidentals disappeared after an octave change using Ctrl(Cmd)+Up/Down
- Crash reports could not be sent
Complete list of issues resolved
Here is a complete list of the issues resolved in this update:
- Plugin API: allow Cursor.addNote() add a note to existing chord
- Plugin API: add Cursor.prev() function
- #297957: Ties extended in region after time signature change
- #297893: [MusicXML import] subtitle placed incorrectly
- #297287: Scale of palette incorrect for high (or low) DPI displays
- #292648: Courtesy accidentals disappear after an octave change using Ctrl + Up/Down
- #296682: Palette names are scrambled and nearly impossible to read (Windows 7)
- #298061: Crash on set as style operation if score ends with a frame
- #297614: Resetting slur jumps to beginning of score
- #297326: Crash on opening Musescore 2.x file that uses leading space setting on the initial clef
- #291085: cursor.addNote doesn't update internal segment reference
- #297688: MusicXML: problems with generated MusicXML when Title frame has a "Dedication" field
- #297468: Critical bug - crashing and not able to read damaged file
- #298061: Crash on set as style operation if score ends with a frame