MuseScore 3.3 Beta Release
Today we are pleased to announce the Beta release of a significant update, MuseScore 3.3.
Download MuseScore 3.3 Beta Release
See MuseScore 3.3 Release Candidate announcement.
Highlights
Complete redesign of the Palettes panel
Palettes panel is one of the most commonly used UI elements in the editor. By the way, there are a lot of reports from users who don’t understand how to customize palette cells, how to add custom elements and rearrange existing palettes.
In a collaboration with @Tantacrul, we focused on simplifying the interaction with the palette elements and ease of customization. We made the interactions more intuitive and integrated the semantic of Master Palette to the palette panel.
Check out Beta version and let us know what you think can be improved!
Chord Symbol Formatting
Past releases of MuseScore have supported superscripting and within chord symbols, but only when using the Jazz style and the corresponding MuseJazz font, and only the fixed amount built into the font. With MuseScore 3.3, you can now set superscripting options within Format / Style / Chord Symbols, whether using the Jazz style or not. There are separate controls for the size and position of extensions and modifiers (the "7" and "b9" respectively in "C7b9").
Roman Numeral Analysis
MuseScore 3.3 adds native support for Roman numeral analysis (RNA) through a new command, font, and style settings. To add RNA to your score, select a note or rest and use Add / Text / Roman Numeral Analysis (or define a shortcut for this command). You can then type your analysis using ordinary characters, like "IV64", and it will be rendered with appropriate formatting using the new Campania font and the Roman Numeral Analysis text style settings. You can then use Space or any of the other shortcuts used when entering chord symbols to enter additional analysis on other notes.
Nashville Number System
MuseScore 3.3 adds native support for Nashville notation through a new command and style settings. To add Nashville notation to your score, select a note or rest and use Add / Text / Nashville Number (or define a shortcut for this command). You can then type your notation using ordinary characters, like "4m7/6", and it will be rendered using formatting similar to that used for chord symbols and the Nashville Number text style settings. You can then use Space or any of the other shortcuts used when entering chord symbols to enter additional notation on other notes.
Other Improvements and Fixes
New
- Add support for Roman numeral analysis & Nashville notation
Improvements
- Implement adding symbols to barlines
- Play Panel layout
- In Edit mode, keyboard arrows now change leading space rather than horizontal offset
- Multiple accessibility improvements
- Multiple improvements to the Plugin API
- Make use of the existing accordion palette
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
- Note symbols were truncated in Tab Preview
- Some Buttons looked grayed-out in dark mode
- The presence of fretboard diagrams prevented input of chord symbols in other staves
- Removing a custom workspace caused a crash
- Multiple fixes for MusicXML Export/Import
- Letter score in landscape orientation exported as A4 in score+parts PDF
For a complete list of changes, see the MuseScore 3.3 Beta release notes.
Important notes
- New kinds of chord notation won’t be rendered correctly in previous versions of MuseScore
Comments
About New Palettes
I know that, one of the goals of redesigning pallets is to provide access for visually impaired people and keyboard access.
But is there any need to disturb regular users in doing so?
In reply to The unity of these palettes… by Ziya Mete Demircan
If you have enough time, can you create issues each with a single problem?
In reply to If you have enough time, can… by Howard-C
No!
You guys break it, then we'il complain. That's how the world works.
They all make sense when they're all together.
If you separate them and divide them into small issues, they become meaningless.
If it needs to get into the issue tracker, you can do it.
In reply to No! by Ziya Mete Demircan
Ziya is always right! I totally agree, again. This will be really cool when fixed.
In reply to No! by Ziya Mete Demircan
I would say when there are specific standalone bugs, they should be submitted individually, but I agree general discussion about how to improve the palettes belongs n the forum. Probably better, though, in ne of the threads specifically dedicated to the palettes, and not here in the release announcement.
In reply to The unity of these palettes… by Ziya Mete Demircan
I agree there is work to be done on the visual appearance. But to me, the behavior is mostly good. In particular, I find it a gigantic win that users don't have to magically discover they need to create a new workspace just to customize their palettes. I can't think of any other program that makes me do anything like that. I suspect this will dramatically increase the number of users who now will experiment with customization. Most users will not care or need to know that a new workspace was created for them. But even if you do decide to delete one of these workspaces, the option to do so is right where it always has been, so I don't see how that aspect inconveniences existing users.
I think the main goal wasn't so much about accessibility (although that is a huge side benefit) but about ease of customization for new users.
BTW, if you delete a palette item, it just moves to "More" so it's easy enough to get back. A message to that effect the first time you do it (eg, via a "Tour") seems like it would be in order.
In reply to I agree there is work to be… by Marc Sabatella
I for one very much feel that this is a step in the right direction. I never customized the pallet. I opened up musescore to write, not fiddle with the UI. Maybe I'll need something, Maybe I won't. I definitely don't want to hunting around for something I accidentally removed. But this makes it so easy to do while I'm working. And so easy to recover from a deleted item. Ziya Mete Demircan mentions the extra vertical space as if this is a bad thing. To me it just makes everything easier to read and use. Especially for something I'm using constantly. And of course better for my touch screen, but this is a side benefit..
One thing I think could improve it. Dummy that I am, at first glance I didn't realize the "Add more pallets" was a separate button. I thought it was text labeling the search function.
Also how do I close the search so I can press "Add more pallets button" once it is covered up?
Aside from that, great job
In reply to I for one very much feel… by Joshua Pettus
Once you press search icon, you need to press "esc" key on your keyboard to turn it off.
Sometimes it doesn't close *1. Workaround: Click on the search field and press "esc" key.
*1 : Click on the search icon, type something in the search field (for example: clef), click any clef icon in the Clefs palette. Now, you cannot close the search box with the "esc" key. So, use the Workaround above.
In reply to Once you press search icon,… by Ziya Mete Demircan
I'll do that, thanks! But this is an area it could definitely be improved. True common convention is to hit the esc key, but you'd be surprised how many people will miss that. When designing a visual interface there has to be some visual way to do things.
In reply to I'll do that, thanks! But… by Joshua Pettus
You're right.
I've been testing 3.3beta since last night, and this search box has puzzled me.
especially the first time use.
In Edit mode, keyboard arrows now change leading space rather than horizontal offset
This is backwards. Prior to this release leading space was changed in edit mode, it now changes the horizontal offset.
In reply to In Edit mode, keyboard… by mike320
It's about keyboard arrows, not dragging a note around.
In reply to It's about keyboard arrows,… by Anatoly-os
That is correct. It's stated correctly in the release notes but not in this document.
I think you can put that more in the menu. The menu button (...) could be aligned in centre vertically.
In reply to I think you can put that… by David Copperfield
Also, the Add More Pallettes icon could be replaced with +
In reply to I think you can put that… by David Copperfield
The dark mode doesn't work well with the new pallet.
In reply to The dark mode doesn't work… by David Copperfield
See #294068: Palettes text on dark theme still black in MuseScore Beta
Merci pour cet impecable travail.
Est~ce qu'il y a pas moyen d'exporter une partition video dans le musescore ?
Merci.
Je suis BAHATI Wellars au Rwanda
In reply to Merci pour cet impecable… by BAHATIWellars
Bonjour,
Pour les question en Français, veuillez les poser dans la section Française https://musescore.org/fr/forum/15
Il est possible d'exporter sur Youtube, c'est une fonctionalité de musescore.com.
Program always crashes whenever I start it.
In reply to Program always crashes… by Hinners Leung
I am having same experience too. Program immediately crashes each time I lunch it...Need help please?
In reply to I am having same experience… by ndy
It usually crashes the first time I start it, but when I do it again immediately, it succeeds. I am told the problem is known and fixed.
In reply to I am having same experience… by ndy
There is a known bug that can cause this. If you go to the Download page (see menu at top of this page) and scroll down to where the nightly builds are listed, you can download a build that fixes this. Or wait for the next beta update which should be coming soon.