MuseScore Studio 4.6 alpha
We're pleased to announce that the alpha release for MuseScore Studio 4.6 is now available for testing. You can download it for:
- Windows (MSI installer)
- macOS (DMG)
- Linux (x86_64, ARM64)
Once the alpha is installed, it will show up on your machine as ‘MuseScore 4 Testing’. You can install it alongside your current version of MuseScore 4, but note that the two versions will share preferences and workspaces. Also, scores saved with 4.6 cannot be opened in older versions of MuseScore 4.
If you find any issues, please report them on GitHub. As always, please check first that the issue hasn’t already been raised, and ideally try to reproduce it in the latest nightly build before reporting.
What about beta?
For Windows and macOS users, we’ll be making the beta release available via MuseHub. This is to streamline the installation of new beta sampler and sound library builds. We expect this to be ready in about 2 weeks’ time.
Registration will be required for beta testing. If you’re interested, please sign up here.
Beta builds for Linux will continue to be distributed here on musescore.org.
What's new in this update?
Playback improvements
- Realtime playback now recognises velocity and key durations when using a MIDI keyboard. Sustain pedals should also be recognised. At alpha, this is supported for SoundFont & VST only (For MuseSounds, see more below).
- Count-in is back! Find it in the Playback toolbar > Playback settings.
- VST3 support for Linux has finally arrived. As with VST on macOS and Windows, we expect that certain VSTs might still not play nicely in MuseScore Studio. If you find any problems, please raise an issue in GitHub.
Engraving improvements
For more details on all of these features, see this article (still in draft state)
- New options for selectively hiding/showing empty staves, both in Properties and via an in-score popup when staves are hidden
- Style options for Chord symbols have been extensively reworked
- System markings, including measure numbers (!) can now be placed beneath the bottom stave of a system via the Layout panel
- Many new style options for Measure numbers
- Play count text can be exposed (via Properties) when selecting an end-repeat barline
- Text and coda symbols have new options to control alignment and symbol size
- Free choice of SMuFL fonts
- Free choice of font for tablature numbers
- Improvements to frame layout
- A new Handbells palette with symbols
- New rest alignment options
- Improvements to horizontal spacing
- New settings for tuplet layout
- New options for showing barlines before key and time signatures
- Lyric text: new options for dashes
- Partial slurs: new options to control the position of the ‘hanging’ end of a partial slur
- Volta alignment: new options for where the left hook starts
- New option for controlling minimum system header distance
Guitar features
- Fretboard diagram legend: When a score contains chord symbols, you can automatically add their corresponding fretboard diagrams to the top of the score via Add > Frame > Insert fretboard diagram legend
- Fretboard diagrams can now be automatically created from chord symbols
- “H” and “P” symbols can be added for hammer-ons/pull-offs, and new symbols for tapping have also been introduced (See Guitar palette, and corresponding options in Styles)
- Bends can now be drawn to grace notes after the main note (playback supported)
Workflow improvements
- The Selection filter now lets you select individual notes in chords
- A new text styles widget allows quick styling of highlighted text
- You can customise the number of drum pad columns in the Percussion panel
- Minor tweaks to the UX for Workspaces
Accessibility
- A new shortcut to Pause and select playback position (Alt+Space/Opt+Space)
- Improved screen reader support
Other
- A new welcome screen
- New Save to cloud button in Publish tab, and slight reorganisation of options there
- Slight reorganisation of File menu options
New MuseSounds features
Various features specifically for MuseSounds will be available for testing only when we reach beta. These will include:
- Playback support for guitar hammer-ons/pull-offs/tapping
- Playback support for handbell symbols
- Realtime improvements (key duration, velocity, pedal)
- Fix for the fade-in heard when commencing playback
In addition, our new online sounds integration with Cantai will also be ready for testing when we hit beta. Read the announcement to learn more.
We’ve updated Qt to version 6.9.1 in this release
This should resolve a substantial number of issues (See here). We’re especially keen to hear from testers who have previously encountered UI problems—please try this build and let us know if those issues are now fixed. Many of these problems couldn’t be reliably reproduced by our internal team and only appeared in specific environments or with certain hardware/software/driver combinations.
Known issues
Important!: Some palettes may need resetting to enable various new features (specifically when testing the Layout, Guitar, and Handbells palettes). To do this, click the three-dots menu icon for the palette in question, and choose Reset palette. We will fix this for release so that a manual reset is not required.
We are also aware of issues with uploading scores to musescore.com. At this stage, score uploads are likely to fail, or may upload incorrectly. Our backend team is working on this issue. To this end, it's recommended to test using locally saved scores only.
Links to various videos or handbook pages (e.g. in a popup or the new welcome screen) are placeholder for the time being.
As with any alpha release, be prepared for bugs big and small! While we’ve done a lot of work to get the release ready for testing, all other known issues have been logged in the 4.6 project on GitHub (you can also check out our roadmap to see which ones are being tackled in preparation for the beta release).
Thank you for your support! If you’re interested in learning more about what’s in store for future releases, check out Our near-term plans for MuseScore Studio.
Comments
Great! I think I´ll wait for the beta to test hammer-ons and pull-offs playback.
"Also, scores saved with 4.6 cannot be opened in older versions of MuseScore 4."
Is this true beyond alpha and beta releases?
In reply to Great! I think I´ll wait for… by Ruben Remus
If you don't test it now, bugs might not getting found and fixed for the Beta...
Any yes, what's is the case for practically all 4.x versions. Just don't save, esp. do not overwrite existing scores, save to a different place ot with a different name
In reply to Yes, what's is the case for… by Jojo-Schmitz
Will 3.7 read 4.6 files?
In reply to Will 3.7 read 4.6 files? by OldScores
Yes, of course! ;-)
In reply to Yes, of course! ;-) by Jojo-Schmitz
3.7 FTW
In reply to Yes, what's is the case for… by Jojo-Schmitz
+1 for Jojo's comment.
The hammer-ons/pull-offs and tapping feature is actually a two-parter: one part engraving, one part playback.
All the engraving stuff is there in alpha and ready for testing, so if you want to get a head start on some guitar scores now, please do so! There are also lots of options in Styles for these symbols if you'd like to check them out :-)
In reply to +1 for Jojo's comment. The… by bradleykunda
Is the playback of these effects supported by VST sounds and/or Basic Sounds?
In reply to Is the playback of these… by yonah_ag
Playback for these guitar features will only be supported by MuseSounds at this stage.
It is interesting that arguably the biggest feature for Linux users - finally VST support - many years after Windows and Mac users - didn't even make the list of what is new in 4.6.
i'd like to test the handbells.
In reply to It is interesting that… by graffesmusic
This was actually just an oversight. Thanks for pointing this out–I've updated the announcement to include this.
Note that - al least on Linux - all shortcuts to plugins you have in the previous (4.5x) release, will be deleted when you start the 4.6 alpha version. (you can recreated them in 4.6, but they are deleted on a restart)
https://github.com/musescore/MuseScore/issues/29054
Make sure you have a backup of shortcuts.xml.
I have downloaded yesterday the new MuseScore 4.6.0 - Alpha in my PC ASUS- F55OV , 8 GB Ram. and OS Ubuntu 22.04 LTS and when I press the "playback" button the cursoe stays fixed at the start of the measure, and no sound comes up. Also by entering the notes, I can not hear any sound. Musesampler hat found everything required and all the switches for playback´actions are on.
The same problem happen to me with the last 2 MuseScore-nightly (from august) releases. The playback function in MuseScore 4.5.2 , Musescore 3.6.2 and Musescore 3.7.0 function correctly. Maybe a problem cause by the use of the new Qt. 6.9.1 library used in connection to Ubuntu 22.04 LTS?
In reply to I have downloaded yesterday… by puggbma
I confirm this does not work with Ubuntu 22.04.
See https://github.com/musescore/MuseScore/pull/23939
This is a new audio driver for Linux, that uses the Pipewire API, (and therefore will only be used when Pipewire is installed and running). For system that do not have pipewire, it will fallback to ALSA automatically.
On 22.04, pipewire is installed out-of-the-box and runs as background service automatically. But it is not used by default for audio output. There are tutorials everywhere on how to make pipewire default.
I tried to make it work with recent Appimages, but did not succeed. (could be me being stupid, evidently)
Anyway, Marc pointed out that, as a workaround, an environment variable can be set:
MUSESCORE_FORCE_ALSA=1 ./MuseScore-Studio-4.6.0.252301442-x86_64.AppImage
which works fine on Ubuntu 22.04.
In reply to I confirm this does not work… by graffesmusic
Thank You very much for your answer. Unfortunatelly I was setting the environment variable MUSESCORE_FORDE_ALSA=1, but the result was the same. MuseScore 4.6.0 do not produce any sound.
I was using some small script:
!/bin/bash
pwd
ls -l
echo " set the new environment variable MUSESCORE_FORCE_ALSA=1 "
MUSESCORE_FORCE_ALSA=1
echo "MUSESCORE_FORCE_ALSA=$MUSESCORE_FORCE_ALSA "
echo "continue enter JA "
read antwort
echo "Your answer is = "$antwort
echo " ... Calling.. MuseScore-Studio-4.6.0.252301442-x86_64.AppImage ... "
/home//Downloads/MuseScore-Studio-4.6.0.252301442-x86_64.AppImage
echo " ..End of program.."
MuseScore 4.6.0 function as expected, sound libraries and everithing is found, but no sound will playback.
It would be nice if someone can publish the script to be use in order for the MuseScore 4.6.0.252301442-x86_64.AppImage to work under Ubuntu 22.04 LTS.
In reply to Thank You very much for your… by puggbma
Export it?
export MUSESCORE_FORCE_ALSA=1
In reply to Export it? export MUSESCORE… by Jojo-Schmitz
Thanks a lot I was including this command in my script and MuseScore 4.6.0 -Alpha could make playback correctly.
Thakns again.
In reply to Thank You very much for your… by puggbma
What can i saY. On my old 22.04 system, just typing
MUSESCORE_FORCE_ALSA=1 ./MuseScore-Studio-4.6.0.252301442-x86_64.AppImage
on the command line produces sound. You do not need a script.
Difference in log:
./MuseScore-Studio-4.6.0.252301442-x86_64.AppImage
/lib/x86_64-linux-gnu/libjack.so.0
/lib/x86_64-linux-gnu/libnss3.so
/lib/x86_64-linux-gnu/libOpenGL.so.0
/lib/x86_64-linux-gnu/libpipewire-0.3.so.0
[I][00096.357960] pw.context | [ pipewire.c: 668 pw_init()] version 0.3.48
[I][00096.360159] pw.conf | [ conf.c: 415 conf_load()] 0x55ed4c150960: loaded config '/usr/share/pipewire/client.conf' with 5 items
[I][00096.360203] pw.conf | [ conf.c: 847 pw_context_conf_section_for_each()] handle config '/usr/share/pipewire/client.conf' section 'context.properties'
[I][00096.360233] pw.context | [ context.c: 293 pw_context_new()] 0x55ed4c200d00: parsed 1 context.properties items
[I][00096.362886] mod.protocol-native | [ local-socket.c: 91 try_connect()] connecting to 'pipewire-0' runtime_dir:/run/user/1000
15:55:15.954 | INFO | main_thread | audio::IAudioDriver> makeLinuxAudioDriver | Using audio driver: Pipewire
versus:
MUSESCORE_FORCE_ALSA=1 ./MuseScore-Studio-4.6.0.252301442-x86_64.AppImage
/lib/x86_64-linux-gnu/libjack.so.0
/lib/x86_64-linux-gnu/libnss3.so
/lib/x86_64-linux-gnu/libOpenGL.so.0
/lib/x86_64-linux-gnu/libpipewire-0.3.so.0
15:55:53.359 | INFO | main_thread | audio::IAudioDriver> makeLinuxAudioDriver | Using audio driver: ALSA
In reply to What can i saY. On my old 22… by graffesmusic
Thanks a lot. Your proposal has function correctly. Now I can hear the sound in my PC with Ubuntu 22.04 LTS. The proposal of Jojo-Schmitz works also correctly.
Thanks again.
Wow, you have actually fixed bar numbers! Looks like a massive improvement. This was the main issue preventing me from migrating from Sibelius. Huge thanks!
When are you going to allow for custom coloring of the dots on the fretboard diagrams, such a simple but needed feature?
In reply to When are you going to allow… by tihomihaylov
Feel free to request that feauture on GitHub
In reply to When are you going to allow… by tihomihaylov
Probably when someone asks for it. I've been reading the forums for something like 8-10 years and I've never seen any discussion of this topic.
You will want to begin by making a post in the Feature Request sub-forum (https://musescore.org/en/forum/7). This sub-forum does not actually make the request of the developers. Instead, it opens discussion among the regulars here in the forum. Perhaps there is already a way to do this. Perhaps there is already a request in the pipeline and you should add info there rather than open a new request. Once there is sufficient discussion, you will post the formal request on GitHub. (In the discussion, ask for the URL: I don't know it off the top of my head.)
Good luck :-)
Hello, many thanks for your work !
I have just tried the possibility to add custom Smufl fonts.
To begin, I wanted to add available free fonts.
I decided to add SMuFL font 'privately', because in the past, I have had a problem with a music font being too present in Libreoffice.
To obtain a list of fonts, I have read this page:
https://www.smufl.org/fonts/
I have succesfully installed "Sebastian" and "Leipzig" fonts.
However, I did not manage to install the fonts from Finale available here:
https://makemusic.zendesk.com/hc/en-us/articles/1500013053461-MakeMusic…
because the .json files are not present.
Do you have the .json for theses fonts, or do you know how to make them ?
Please note that I like very much the choice of fonts embedded with musescore, but I am excited to try the new features.
Best regards,
Patrice Reich
In reply to Hello, many thanks for your… by Patrice Reich
In the MMFonts.msi from that site you'd find all the .json files
In reply to In the MMFonts.msi from that… by Jojo-Schmitz
Many thanks for the quick answer. Thank you for your work. I manage to install the fonts that we can see in the attached file.
I like very much Valerio, but Cap1800 doesn't appear.
Tell me if I miss some interesting fonts.
Best Regards,
Patrice Reich
In reply to Many thanks for the quick… by Patrice Reich
Try cap1800.zip from https://forums.steinberg.net/t/1800-style-font/763178/8 (that one works for me in my MuseScore 3.7 Evolution)
In reply to Try cap1800 from https:/… by Jojo-Schmitz
Hello, thanks you for your answer.
cap1800 works with your MuseScore 3.7 but not in 4.6.
AloisenU doesn't show up in 4.6 or 3.7.
MuseScore 3.7 doesn't want to start with more than 7 font Directories.
As attached file is the screenshot of my working fonts in 3.7.
Best regards,
Patrice Reich
In reply to Hello, thanks you for your… by Patrice Reich
In 3.7, i have 24 fonts, all working.
Over here, all these fonts also work in 4.6. (including cap1800 and both AloisenU fonts - maybe try the AloisenU.json from my github https://github.com/diedeno/SMuFL-extra).
There should be some indications of possible problems in the logs.
In reply to In 3.7, i have 24 fonts, all… by graffesmusic
Hello, thanks you for your answer and your work.
There was some indications in the logs.
My files for Golden Age and Legato were corrupted, now I have the good files (That's why 3.7 refused to start, because of the corrupted files).
AloisenU works in 3.7 without the U (Aloisen.ttf) and with the metadata.json of size 1.8 Mo.
It appears in 4.6, but the result is garbage, like with Legato (Legato works with 3.7).
Cap1800 needed an uppercase (Cap1800 and not cap1800) and now works also with 4.6.
I have added Ekmelos that works both with 3.7 and 4.6
Best regards, Patrice Reich
In reply to Hello, thanks you for your… by Patrice Reich
Here all those fonts work just fine.
AloisenU.ttf + AloisenU.json and Legato are fine in 4.6.
It is all very sensitive (at least in Linux) -- case sensitity and problems with spaces and so.
I did my fair share of troubleshooting, but got it all working.
Perhaps we should somewhere create a repository with known working (open source SIL or GNU) fonts and corresponding json files? I guess there would be no legal problem.
In reply to Here all those fonts work… by graffesmusic
And they all (all the free ones at least) should be made available on musescore.com too, so score use ng then can show them online too
In reply to Many thanks for the quick… by Patrice Reich
Valerio does have an issue with its stems though, see https://github.com/musescore/MuseScore/issues/25088 and https://github.com/musescore/MuseScore/pull/25050 where I tried to fix it (but so far failed :-()
Testing 4.6 Alpha to finally replace 3.6 as count-in feature is back ...
Very first bug I have found: you can't reduce the window so that it takes half the width of the screen.
Dragging the resize moue icon blocks when the window is about 2/3 of the laptop screen width, and drag and drop the entire window to the left (or right) which should make it 50 of screen width also refuses to make the window less than 2/3.
My display is 1920x1080, and I can resize MuseScore 3 any size I want, and drag to left or right screen honors the 50% size request.
In reply to Testing 4.6 Alpha to finally… by frfancha
Thanks for testing the alpha build. As mentioned above, please report any bugs you find directly in our issue tracker (https://github.com/musescore/MuseScore/issues), being sure to first check that they haven't already been raised.
Reports of issues here in the comments will not help the development team. Instead, we need to see specific reproduction steps, as well as information about your OS. Moreover, in this case a screen recording is essential.
In reply to Thanks for testing the alpha… by bradleykunda
That's not a new issue with 4.6, but ever since 4.0
See https://github.com/musescore/MuseScore/issues/18580
In reply to That's not a new issue with… by Jojo-Schmitz
Thanks Jojo, I have updated the github issue.
Unfortunately that makes V4 unusable for me, my workflow requires to be able to display pdf or image on the other half of the screen.
In reply to Thanks Jojo, I have updated… by frfancha
I split the screen half and half as well. I've had no problems. MuS is only a little larger than half my screen and I just slide part of the window out of the display area. Perfectly workable.
Annoying, yes, but workable.
In reply to I split the screen half and… by TheHutch
Of course depends on the width of the screen
In reply to I split the screen half and… by TheHutch
Sorry but no, it is not at all "perfectly workable"
I can't make it smaller than 70% of a 1920px screen that's ridiculously large
In reply to Sorry but no, it is not at… by frfancha
Sorry but 1050 pixels width is what I get on my 1920 width screen. So just a little under 55%.
I use windows key + left/right arrow to move the window in position.
And pdf in the remain 870 pixels width is perfectly fine.
Other option is to split top/bottom half instead of left/right.
Or a (portable) second monitor, works very nice as well.
In reply to Sorry but 1050 pixels width… by Henk De Groot
"Buy a second screen"
Oh yeah sure because musescore is unable to resize properly we would buy another screen???
Sorry but no, musescore 3.6.2 behaves normally and accepts to be resized the way you want.
That bug in V4 is just ridiculous
In reply to "Buy a second screen" Oh… by frfancha
It's been more than two years since I've used v 3, but my recollection is that it was limited as to how small you could make the window in the same fashion. Obviously, I may be mistooken.
Try hiding toolbar and status bar if you're going for vertical split, or Palettes, Layout, and Properties panels for horizontal.
In reply to It's been more than two… by TheHutch
It is restricted too, but can be made much much narrower