MuseScore 4 is OUT NOW!

• Dic. 14, 2022 - 00:17

UPDATE - March 13, 2023: MuseScore 4.0.2 has now been released.

This patch release release fixes loads of issues, and also includes some important usability improvements as well as a ton of engraving enhancements.

All the details about this version can be found here on Github.

UPDATE - January 13, 2023: MuseScore 4.0.1 has now been released (see changelog).

This announcement is available in other languages. See links to translated versions below.

Hey everyone,

Today, we are delighted to announce the release of MuseScore 4 along with our new orchestral playback library Muse Sounds!.

To install:

  1. Visit
  2. Click the main Download button for your operating system
  3. This will download the Muse Hub installer, which allows you to install MuseScore 4 and Muse Sounds

Linux users need to click the "Download AppImage" button to install MuseScore, and also the text link "Muse Hub (for Muse Sounds)" directly below in order to get Muse Sounds.

For those wanting to download a Windows or Mac version of MS4 without the Muse Hub, please use the appropriate text links at

Watch our release video

YouTube video: Announcing MuseScore 4 - a gigantic overhaul!

What's new in MuseScore 4?

  • Our new orchestral plugin, Muse Sounds
  • Saving to cloud on is now working
  • An improved system for publishing to
  • A simple toggle for switching between playback profiles (MS Basic and MuseSounds)

An entirely new interface
- 400 new icons
- customisable colours
- A new Home tab which includes recent scores, plugins and video tutorials
- A new, friendlier onboarding process

An engraving overhaul
- New system for horizontal spacing
- New system for slurs and ties
- New system for beaming and cross-staff beaming
- New, heavily revised version of Leland and Leland text
- System objects can appear on more than one system (although this is currently only available on certain templates)
- Hundreds of other smaller fixes and optimisations for lyrics, articulation placement, tremolo marks and general positioning
- For a more comprehensive explanation of the engraving changes in MS4, please see this document.

Multiple workflow improvements
- The Properties panel (formerly the inspector) is now much more responsive, easier to understand and filled with lots of useful options
- The capabilities of the note input bar have been expanded and the toolbar itself is now much easier to customise
- Customisable 'Tempo Lines', (accel, rit, etc.) that work with playback
- Scrollbars on the score
- Parts are easier to discover, edit and alter (using the new 'Instruments' panel)
- The experience of setting up a new score has been simplified to be more welcoming to new users
- Improved instrument definitions
- A new tuplets toggle
- New articulation buttons
- A new toggle for cross staff beaming

A new mixer


VST instruments and effects support
- Please note that we will be building additional tools, like automation and MIDI mapping in later releases, once MS4 is out

Accessibility improvements
- A new keyboard navigation system that follows best practices to allow users to quickly move around the interface
- Improved screen reader support (in particular, we really need people to test and provide feedback on this)
- An editable high contrast mode

Incompatible features we will re-introduce in later releases

  • There are other features that have not played nicely with our new systems at all, and which will need to be replaced in later releases, namely: the plugin creator (which we want to rewrite completely as a priority), the score comparison tool and the 'Documents side-by-side' feature.

Read this announcement in other languages

These translations have kindly been provided by members of our community:

Or you can use Google Translate to view it in other languages.


In risposta a by eupho2052

What are your system specs?
I have found that 8 core CPU and 16g ram handles full orchestration with some intermittent pops and clicks I real time. Exporting to audio file creates a clean rendition. I am guessing that you are running into a memory resource and computing issue. Try exporting the concert band piece to .wav and see if it is clean. Also try setting all instruments to MS Basic sounds.

Anyone else having this problem? When i start up an old score from v3 into v4, it just randomly closes the app and i cant access it. When I try to reopen the quit score it doesn't work. Can someone help?


2 questions:

  • where can I provide feedback about accessibility and keyboard shortcuts etc, as you asked in a post?
  • Where can I download latest portable version of MS? It seems, that 4.0 version is not portable.


In risposta a by Marc Sabatella

I contacted support and they didn't answer my questions and told me to come post here. Which I found quite infuriating as I really don't enjoy this kind of environment. I've been paying for the pleasure of using Musescore and the website features and they've completely eliminated everything I enjoyed about it. I started with the first Musescore. Loved Musescore 2. Musescore 3 was even better from the get go!

I looked at the issue tracker and saw that a lot of other people are having the same issues and the answers they're getting is that the issues will be fixed in a later release. Pointing at the release notes showing that they knew it was incomplete before release and we should have read about all the missing features before installing. They just wanted to get it out.

I then get an email today stating that "The completely overhauled release of MuseScore 4 is available right now" which I took for them stating that they fixed the product. No. I opened Musescore, checked for the update and it came back saying I already had the latest version. They hadn't done anything yet. The "of" in the email was misleading.

I realize I'm being pedantic but this has been a BS experience. I just want to get back to writing and this has been the program I have used for over a decade, now.

In risposta a by Jacob B D

I'm not sure what you mean about "contacted support" - there is no "support" for the free and open source music notation program MuseScore. Maybe you tried contacting the support staff for the commercial score-sharing website Indeed, the staff of that website is not able to help with issue relating to the free and open source music notation program MuseScore, nor should they be expected to. They simply have nothing to do with the free and open source music notation program MuseScore - only with the commercial score-sharing websitecom. You've been paying for the commercial score-sharing website, not for the free and open source music notation program MuseScore. Two different things.

Anyhow, as I said, if you are experiencing some sort of problem you'd like to see the developers investigate and fix, step one is to actually report the problem. The first step is to report it to the community here, using the issue tracker on this website. Until you report the problems you personally have observed, there is no way the anyone else can know about your unique use cases and the unique problems you are experiencing. If on the other hand you are saying that you've seen someone else has already reported the exact issue you have been encountering, great - but then the next step is to make sure this issue then is also reported where the devloeprs (oas opposed to just us volunteers here in the community) can see it. That's on GitHub.

BTW, also - yes, of course MuseScore 4 is "incomplete". Every single piece of software ever released is incomplete. There is always a list of bugs left to be fixed, features left to be implemented.

Also, the email you got is referring to MuseScore 4 being overhauled from MsueScore 3, which is absolutely true. There are no more complete overhauls planned - just bug fixes and incremental improvements.

In risposta a by Jacob B D

Don't know what you want to hear... You made inaccurate statements that showed a lack of understanding of the MuseScore environment. Then Marc gave you correct information, as with what you can do to effect your grievances. And let you know as a .0 release of a full overhaul, it isn't unexpected to have some shortcomings. He made no attack against you, just gave you information. What you chose to do with that information is up to you.

I've been looking now for close to an hour, but where do I have to click to install MuseScore and the Muse Hub on a different drive than the boot drive? And is there a button to have the Muse Hub behave like normal programmes, rather than disappearing into the system tray together with the volume mixer?

I have installed MuseHub and when opened it just shows some sort of error message as seen in the attachment. Is there any way to fix this? or download the sounds online and then bring them into the program?

Allegato Dimensione
MuseHub Error.png @dimensione MB

If I download sounds from MuseHub on a device with internet connection, am I able to copy the files from the downloads folder onto a computer without any internet connection and then use them in MS4?

I wish i could use Musescore 4 but when i try and d/l it with Muse_Hub the installation process stalls very quickly and the only thing installed on my computer is a 21.3 Mo prog ... and when I d/l it without Muse_Hub i cannot use Soundfonts any more ... very disappointing ... even more disappoitning not to have any answer to my requests on Muse Hub page, except than "reboot your computer" which I had thought of doing before !
I am using windows 11

In risposta a by philippe888

If you download MuseScore without Muse Hub, you can definitely use soundfonts - the only thing you need Muse Hub for is Muse Sounds.

It is Christmas time of course, so no surprise if the developers are a bit slow about responding to issues this week and next. But there are pretty much always volunteers here on the forums able to help. if you are having trouble accessing soundfonts in MuseScore 4, just start a new thread in the Support forum and describe the problem in more detail.

In risposta a by philippe888

Well, the sounds are one area of improvement, but for me, the really exciting thing is the vastly improved engraving. So it's still very much worth using even if you can't yet install the sounds. Note you don't need MuseScore from Muse Hub to use the Muse Sounds - if MuseScore 4 is running already, you can forget trying to download it from the hub, and just focus on downloading the sounds themselves. Could be whatever went wrong when you tried downloading the sounds was just a fluke - the server being temporarily overwhelmed - and it might work to download the sounds if you try again. Start with just the harop, which is the smallest and should download in no more than a minute or two on most connections I think - that will let you know if it's working at all.

In risposta a by BanjoJake

There are tools to convert ABC into XML (and viceversa) which can be opened in MS4. Moreover you can have both 3.6 and 4 in your system without having to go through the hassle of installing and uninstalling, (well, at least in Linux, don't know about non free operating systems)

In risposta a by reblues

I am aware of EasyABC which can convert ABC into XML, but which tools do that within MS4 ?

Windows 10 allows both versions to co-exist. The reason for installing and uninstalling would only be to see if ABCImpEx appears in the plugin manager list. And that is inconvenient, compared to checking a web page every few weeks.

Here is another review video for MuseScore 4 showing a real-world project and the benefits of the new Muse Sounds for proof-of-concept rendering. I cover a solution for some of the trouble that Linux folks might be having with the Muse Hub back-end service that isn't running in some cases. I also cover navigation for the soundfont sounds which is done from the instrument panel rather than the mixer (which is where Muse Sounds are applied). As others have suggested, this navigation should probably be more universal from the mixer... but if you have been missing out on some of the MS Basic sounds that you have used in the past, or if some sounds are lost when you import older scores into MuseScore 4, I show you where to find them and how to apply them:



The program will not run after downloading 'MuseScore4'.

When I heard that MuseScore was released as a new version, I ran an upgrade on 'MuseScore4.'

I tried running 'MuseScore4' after the update, but the file did not open.

So I removed 'MuseHub' and 'MuseScore4' from my computer and reinstalled it, but it still doesn't work.

My computer is using 'Window10', and the computer operating system is based on 'x64'.
And the audio interface is using 'U-PHORIA UMC204HD', a product of 'Behringer', and 'Current Sample Rate' is '48000Hz'.

I'd like to know why this problem occurred and how to solve it.

Why does Muse.service run all the time and chew up CPU when neither MuseScore nor MuseHub client are running? It frequently shows up as the top consumer of CPU in "top" when nothing else is running except a terminal window showing the results.

In risposta a by ubuntourist

It runs in the background to allow automatic updates and community acceleration. You can disable these in Muse Hub settings, and you can also simply stop the service process.

Being the top consumer of CPU when nothing else is running shouldn't be so surprising - after all something has to be the top consumer, and if you have nothing else actively running, that doesn't leave many alternatives. But it should be a negligible amount of actual CPU cycles. E.g, 60% of next to nothing is still next to nothing.

In risposta a by Marc Sabatella

Well, I have to disagree with this.
As soon as my computer goes to standby mode, my processor fan starts working, which means that processor is intensively used. So no, it' not 60% of next to nothing, but almost 100% of one of my processor cores.
Btw, that is just one of many things that don't work as should with all these new updates. In fact, there are so many things that look untested and unfinished that although I was quite enthusiastic to embrace MuseScore4, I've decided to wait for more stable release.
But, I know that things like these take a lot of work, and we are receiving your product for free so please don't take my words as harsh criticism. I think that the whole team has made many nice improvements and that MuseScore has very bright future if you continue in this direction.
I really hope that we'll get first upgrade very soon because I really want to switch to MuseScore4.

In risposta a by MarinR

Hmm, something seems to have gone wrong with your installation - what you describe should not be happening. Unfortunately, since this problem does not seem to be occurring for others, it’s not going to fix itself in an update - you’ll need to report it on along with enough system details to help the Muse Hub developers understand what is going wrong in your system specifically.

Meanwhile, though, you might try simply uninstalling & reinstalling.

If there are other bugs you encounter in MuseScore 4 itself, you’d need to make sure these are reported in GitHub before they can be investigated and fixed. Don’t just assume others are seeing the same issues you are.

As much as I looked forward to MS4, I cannot use it. On Windows the resizing to allow MS4 and another app is such that I cannot put them side by side or up and down. Also in Windows, the latency issue is horrible, even if the buffers are adjusted. You might want to look at Jack in Linux to see how it adjust buffers. Unless you use a Debian package in Linux, you don't receive the Hub. And using the Deb package of Hub you don't receive the demo charts. For right now I will go back to 3 until a see a new update to 4 is made available. Good Luck !!!!

In risposta a by tinkjt

Update...installed the latest Xubuntu Linux Distro and then installed MS4 and Musehub. MS4 worked well. I couldn't resize the windows to allow MS4 and Google to line up side by side on one full screen. But I could line them up horizontally on the same screen. Got to play with this more.

Hello, I'm sorry, but that would be nice if you could let us edit how long the sidebar(s) would it be (See 1st picture). Also, when I try to change the time signature, MuseScore crashes, literally, constantly, it is impossible to change the time signature in the ongoing score. Thirdly, I don't know if it is for me, but sometimes when typing notes and playback comes laggy, not always, but pretty frequently. But, in general, there is better than MuseScore 3 version, and very aesthetic and modern looking, only to change the edges, because now they take up a lot of space, and at least for me, it is impossible to concentrate on the score, and I know that it is a new version, and for stability, it will take some time, but this is just observations. And I remembered, it would be nice to have the "Synthesizer" tool as it was in MuseScore 3 to edit reverb, lows, and highs, maybe there is, but I cannot find it. :)

Allegato Dimensione
Ekrano nuotrauka 2022-12-27 195617.png 249.76 KB

In risposta a by Lukas Lazinka

Sounds like you are encountering some sort of bug involve a particular score, so do be sure to open up an issue (either on the issue tracker or on GitHub) and attach the score and precise steps to reproduce the problem.

Effects are now provided by VST, so you'd need to find a reverb that provides the controls you like. It's expected a future update might provide additional options within MuseScore.

I downloaded the "MuseScore-4.0.0-x86_64.AppImage" file onto Ubuntu and set the "executable as program" property and when I double-click or right-click "run" nothing happens. No screen flash, no images or dialog or error and system monitor indicates there is nothing running associated with this install. Downloaded more than once.
i have had 3.6.2 running for a few days while starting to learn it.
ADDED: When I tried to execute it from command line I got the notice I have to use FUSE to run it. It that correct? I have installed AppImage files before without this step.
ADDED2: I installed test-snapd-fuse-consumer and got the message the file could only be extracted.
I attempted an extract and got a lib error. My limited tool kit has been expended.

In risposta a by graffesmusic

THANK you so much. For others who cannot execute the install onto Ubuntu from Files:
sudo apt install libfuse2
sudo ./MuseScore-4.0.0-x86_64.AppImage

Installed and loaded into a window in seconds.

In the introduction pages which popup on startup, nothing is clickable. Not the video or the training links which come up afterward. I assume I'm missing some library or player which does not come with default Ubuntu home.

As a person still learning Muse out of the box my impression was 3.6.2 I used pretty much worked out of the box. When I load a score into 4.0 the interface is much more spread out with my most-often clicks on opposite side of the screen. 3.6.2 would play the score or notes in the synthesizer immediately. Now not only does the synthesizer not play at all when I click a note, but the play command stays at the start and will not move.
Any clicks anywhere in the UI to external sources (bugs, everything is help, etc) do nothing.

In risposta a by Jojo-Schmitz

OK. Thanks for your help. Double clicking on the AppImage now runs the MuseScore app but does not install it. I have no idea how to install the app from the AppImage.
when I try to "open With" snap or installer they produce errors.
I was able to get the MUSE HUB installed with only a small annoyance.

ADDED: I seem to have been able to solve the problem functionally (though there may be a better way):
I copied the AppImage to the Ubuntu desktop and I right click on the icon and select "Run as Program."
External links in the program working as expected. As before, previous score created with 3.6.2 will not play back. The play cursor does not move and the synthesizer does not play when i click a note. The only audio device I'm able to select is "system default" which is the same device being used in the Ubuntu system Sound Settings which work in 3.6.2 and Audacity. I suspect the way I'm trying to run the program disables some of its features.

In risposta a by Jojo-Schmitz

I've explored all the possibilities so far to the best of my knowledge.

last attempt:
sudo install MuseScore-4.0.0-x86_64.AppImage /MuseScore4
This created a new file when run behaves exactly as before with severely broken features such as play and sound.
I then installed AppImageLauncher so the new file ( as near as I can understand is just the appimage with a new name and icon) so the image is now in my Ubuntu Show Applications with other Snap applications.
Nothing changed but the ease of starting the app.

The conclusion I've come to is this app will not run properly on my Ubuntu home system in its present state unless I'm missing some library.

Allegato Dimensione
Screenshot from 2022-12-29 15-48-37.png 239.03 KB

In risposta a by pvarn

Technically you don't need to install an AppImage, but you do need to set the file's permissions so that your user can "execute" it. See instructions @

However, I just learned today that you can invoke the AppImage with an 'install' option and it will set up the permissions, icons and launchers for you.

For the MuseScore AppImage:
Open a terminal
CD into the directory you have the AppImage file in.
From that directory execute the command: ./MuseScore-4.0.0-x86_64.AppImage install

In risposta a by pvarn

Really that's not surprising. The whole point of an AppImage is that it be a self-contained runtime and once you set permissions to execute it should just run when double-clicked. As far as I can tell the install option integrates it into your desktop with a launcher and the icons and such, but in principle wouldn't have any effect on how it runs or performs.

Though in all honesty I can't find any documentation on the AppImage install option. Until today I didn't know it existed, so maybe it is possible that AppImages can do something upon an install invocation that could affect how it runs. But in your case apparently not.

In risposta a by rocchio

The problem is not running the program which I have done in several ways but no matter how I run it behaves exactly the same. I don't think it's possible for it to run as intended on my system. 3.6.2 is working but would like the nicer sample sounds although the UI positions don't seem as friendly to me in 4.0. Everything I tried runs exactly like clicking the appimage raw. I assume the image of the diagnostics I sent above are not that useful.
The program detects I have Mus Hub installed but doesn't seem to be able to access it. When I select a measure to play from and tap the spacebar, there is a narrow line placed at the play point (instead of the wider translucent bar) and it does not move.

In risposta a by pvarn

I wish I could help you further; but alas I have no add'l ideas or suggestions for you. For me, I am running the MS4 AppImage on fedora-35 and all is well. I will note two things, fwiw. One, I have not made any attempt to install MuseSounds, so only using the basic soundfont with fluidsynth subsystem (because my instrument, Mountain Dulcimer, isn't included in any advanced soundpacks so there's no point). Second, since I use a custom soundfont for the Mtn Dulcimer upon first loading I also had no sound, but that was because I needed to point to my soundfont in the settings, then use the mixer to point each instrument channel to my soundfont. My guess, tho, is that none of this helps with your situation.

In risposta a by rocchio

Thanks for considering my situation. I started using 4.0 all in defaults and have not attempted to change anything, I'm not able to select any audio devices at all since originally starting the program by directly clicking on the appimage. I only explored suggestions about installing at the suggestions here when I noted much of the program appeared non-functional. I do have a wimpy laptop with Fedora on it but that machine is far from a comfortable platform for this work. I was hoping Ubuntu not being updated as aggressively would be a more supported Linux for musician use. When I use 3.6.2 there are many devices to choose from although only one works at a time depending on how I have the audio connected up. Right now I'm using a Behringer audio-digital-MIDI interface. All my other sound apps- MuseScore 3.6.2, music player, Audacity, FireFox, system sounds, etc. all play through that device fine. MScore 4.0 won't even let me select it.
Now that I think more on it, this may be the core issue in that 4.0 only lets me use the "System Default" audio device while 3.6.2 allowed scanning for devices and let me select the ones that worked. If I plug into the headphone or back panel jacks I lose all functionality on the Behringer which is not suitable for my purposes. Hopefully the programmers will consider allowing a more flexible audio device scan/select in an update.

In risposta a by rocchio

I have ALSA installed but don't know anything about Pipewire.
Will investigate.
According to this article Pipewire, WirePlumber and Pulseaudio are already installed by default in my version of Ubuntu:

This is not helping me solve the problem though as I don't know if or how to get Muse to use it.

ADDED: I made a small amount of progress by installing Studio Controls. When I press spacebar to play the play bar now moves, mixer channels light up but still no audio and still no options to select anything but "system" in the IO Audio.
Still trying to find among the complex combo of settings one which allows both the playbar to move AND get sound without disabling my other apps. Nightmare incorporated.

In risposta a by pvarn

First - the Pipewire controls are accessed via the Operating System and your desktop environment - in my case KDE - not from within MuseScore. That little speaker icon in my screenshot was on my KDE desktop's control panel, not in MuseScore.

Probably you are using the GNOME desktop. I've never used that (well, not since back in 2002 or thereabouts). You should try to find the Audio settings panel in GNOME.

I have a bheringer mixer with a basic digital, USB, interface. I just now plugged it into my PC. From my KDE Audio settings panel (screenshot of that attached in case it help provide any context) I can redirect MuseScore output to it - or to any of my output-capable audio devices. Again, I'm doing this in fedora/KDE, not from within MuseScore.

Apologies I can't be of more help.

Allegato Dimensione
MS4_KDE-Audio-settings.png 407.88 KB

In risposta a by rocchio

I have considerable access to all my sound devices. I have 6 other programs including Audacity and MuseScore 3.6.2 all working with the Behringer. MScore 4.0 is the only app which cannot access the Behringer AND it's the only of my audio programs which does not let me choose the sound device from its UI.

The screenshot has a sample of the default Ubuntu with it's audio controls and the Studio Control panel which gives me control over the various Jack, Pulse, and ALSA sends to the Behringer.

Allegato Dimensione
Screenshot from 2022-12-31 08-41-10.png 290.92 KB

In risposta a by pvarn

I didn't even want to bring up Jack; that's another whole rabbit hole. I've only used Jack with the Ardour DAW. In that context Jack let's me do virtually anything I want with the audio. In principle Pipewire will let you do the same complex routing that Jack will, tho I haven't really tried anything complex with Pipewire as yet. I would also note that MuseScore 3.x explicitly had a setting to tell it to use Jack; I don't see anything similar in MuseScore 4.0.

What I'm not seeing in your screenshot is any listing of the apps, or "audio streams." You want to "wire together" your Behringer and MuseScore. In the Jack world you'd see those two items, as boxes, in QJackCtl and you'd simply drag wires between the two. In my KDE Audio settings I just use a dropdown box to tell KDE to tell Pipewire to connect MuseScore to Behringer. To my mind you should be able to find something in Gnome that shows 'MuseScore 4.0' as an Audio source along with some controls to be able to tell it where you want that audio stream directed to. (Maybe you do see that in your Ubuntu Sound settings dialog and I just don't see it in the clipped screenshot?)

Finally - maybe take a look at Helvum (see the graphical representation at the below link): "if your Linux desktop is running PipeWire, trying installing Helvum to graphically monitor and edit your multimedia graph! It is currently packaged on Fedora, Arch Linux, Flathub, and others." @

In risposta a by rocchio

All the apps "just work" using their own internal audio selection properties. In Muse 3.6.2 I'm able select between many detected interfaces until I found the one that worked. 4.0 does not let me select anything.
Pipewire is installed by default in my current version of Ubuntu. Firefox streaming and YouTube "just works"

I'll check into helvum. At this point everything works including Muse 3.6.2 all seamless with the Behringer (MIDI I/O, data storage sharing, audio.) Why 4.0 is the standout seems ridiculous to me now.
Screenshot taken with Qjack one with Audacity playing and one with MuseScore playing (note the mixer lit up on the far lower left)

In risposta a by pvarn

Sadly, I have no further suggestions for you. If you are unable to see an entry for MS4 from within one of the Pipewire routing tools, then my belief is that you simply will not be able to achieve your goal with MS4. As to why your particular system's pipewire subsystem will not detect MS4...I really have no good answer for that.

In risposta a by rocchio

Strangely it started working (mostly.) There is nothing I can see that I've done to make it work. However it's not consistent. Some days it works right away and some days it will not work at all even through I've changed nothing and my default system audio assignments haven't changed. I've stopped working with the QJack Control. It messes with my system default assignments I created to access the Behringer as soon as I start it and have to reboot to get them back. As a guy who's been doing desktop support (though not much on Linux) I found ms4 to be a challenging experience but over all I'm pleased in the choice of Ubuntu 22.10 as it has all the features to support professional audio tools out of the box as opposed to Windows which is is a driver maze.

I finally got to access the MuseHub and pleased with the quality of the sounds. Although somewhat limited (especially in the drum kit) I know a lot more work is being done and I think it's a valuable asset to the program.

Yeah, it may look good on Windows, but has any of the developers ever tried MuseScore 4 on a Linux desktop with fractional scaling (like 125%)? It looks god-awful. You need to port it to QT 6. See the screenshot which features another QT app, "Strawberry", which uses QT6.

Screenshot from 2022-12-29 01-57-14.png

In risposta a by musescore_king

FWIW, it's working fine on my Linux machines using fractional scaling factors (eg, QT_SCALE_FACTOR=1.25). I'm wouldn't be so sure the difference you are seeing is just about Qt 5 vs 6, could be other aspects of how these apps are interacting with your display, including how the scaling is being performed.

But work to migrate to Qt 6 is underway. Lots of issues to work out still from what I understand, but I see progress is being made regularly - PR's being submitted and updated etc.

extremly unstable. Have found 4 bugs in less then 10mins (2 of them beeing program crashes), I posted them in forum as the bug report system doesn't even list 4.0.0. With so many bugs you should have implemented a bug report function (like most modern systems have) that auto-collects data from crashes or on request. I guess MuseScore 4 needs a looooot of work before it becomes usable at all.

In risposta a by roninho aguiar

It’s important to understand, it already does work for many. But for some it doesn’t. This was also the case with every previous version of MuseScore. There are too many different keyboard layouts in the world to be able to guarantee perfect success with all of them. And that’s one reason why the ability to customize shortcuts exists in the first place.

I'm a music teacher who is pretty comfortable with software and technology. I've used MuseScore for many years to create sheet music for students and ensembles. Musescore 4 in its current iteration is unusable for me, and probably for most of my students and non-techy music teachers. This is because of the computing power recommended for using it, which is not going to be on the average person's several-years-old home computer or laptop. Secondly, I wasn't able to simply download the software and start using it.

Right "out of the box" on my two computers, Musescore 4 is unusable. On my studio computer (2 cores, 4G RAM, Windows 10) I can enter notes and play them back, but the sound is laggy and scratchy as has been mentioned in many other bug reports I've read. On my office computer (4 cores, 8G RAM, Windows 10), there is no sound on note entry and playback does not work at all. I've tried implementing the two main fixes that have been recommended elsewhere: changing the buffer size in Musescore preferences, and changing the sample rate for my speakers in the Windows Control Panel. (This second fix is way beyond the comfort zone of people looking for plug-and-play software.) I'm not going to dig further for any other deeply-buried Windows settings to adjust, because I don't think your software should demand this much tinkering from the average user.

I'm requesting that the Musescore 4 development team keep in mind the average CPU capabilities and default sound settings of "home users." The full product I've seen in demo videos looks amazing, but it will be unfortunate if the majority of your user base will not be able to access its many features, or even get the software to work upon installation.

I will try to install and use version 4 again in a month or two as bug solutions are implemented, but it may never be an option for me to use on my studio computer. Will Musescore 3.6 remain available for download for people who need a less resource-intensive alternative?

In risposta a by jmelin

All versions of MuseScore are available for download if you find the right places to look 9eg, GitHub).

But I'm guessing the problem isn't your computers not being powerful enough - almost certainly it is something else. It really does work for most people using default settings. So anything you can do to help track down what is getting in the way on your systems would be very useful, both in finding a solution for you right now, but also to improving MuseScore to better handle similar situations in a coming update.

In risposta a by Marc Sabatella

Thank you for your reply. Musescore 3.6 works fine on my computers with all existing settings. I haven't found any insights when combing thru various threads on what may be the problem with my systems besides the buffer and sample rate as mentioned. There is nothing unusual about my systems (run-of-the-mill Dell and HP All-in-One computers running Windows 10, no special sound cards etc.) that wouldn't be replicated by many others who are already reporting bugs in detail. So I will wait for future updates.

I love the muse hub sounds and the enhancements. My only problem, is saving to YouTube. I go through the usual procedure but my new compositions do not appear in YouTube. Maybe I'm doing something wrong but....

Warning! Attention!
call of
c:...\musescore4.exe -o /file.mscx /file.mscz
on computer (Windows 10)
- just running my backup - not absolutley sure what was deleted, but most under \user\*

Amazing I just downloaded and started a new arrangement on it but I got a problem. I downloaded the orchestral suite from the HUB, but I'm using a Midi keyboard and I find a high latency problem worse than in musescore 3. I can't find the panel in I/O where tyou could choose what audio motor engine use to reduce latency. Any solution?


I'm wondering on how I can connect my Roland FP-30x in here using Bluetooth MIDI. I was able to connect both Bluetooth audio and MIDI in my android phone and it's working fine but even my windows laptop says the MIDI is 'paired', Musescore doesn't detect it. If it's plugged via USB cable though, it's detected. I'm kinda new with this bluetooth MIDI thing, so apologies if I missed something. Any ideas if this is possible or how can I resolve this? Is this a Windows thing? Thanks!

Allegato Dimensione
musescore1.png 99.81 KB

Hi there,
I usually use an organ sound bank under Musescore v3.6 "Orgue de salon.sf2", which can be found here:
This sound bank inherently has many different organ stops. I imported it under Musescore v4. Musescore detects it well for me in the choice of instruments, but unfortunately, I no longer have the possibility of choosing one of the particular organ stops offered in this entire sound bank. It's a shame, I see this as a regression.
Is anyone else having this problem ?
thanks a lot for your help

Hi, I have noted a problem with the sound of the bb note of the grand piano and the associated chords such as Bb or Gm for example. There is an unsollicited high harmonic that should be deleted, I believe.

Estuve revisando la nueva versión de musescore, y sin duda se han agregado nuevas características y algunas ya existentes se modificaron. Sin embargo, y por curiosidad no encontré la función de "Captura de imágen", lo cual para mí imprescindible, ya que al momento de terminar de editar una partitura, me toca copiarla a otros programas que utilizo, tales como Word o Power Point. Espero que pongan atención a ese detalle, o me digan cómo puedo encontrarla en la nueva versión.

Strategies for improving Muse Brass playback:
I provide plain score and playback score comparisons and also live reference material in a discussion on strategies for making final Musescore 4 mock-ups. We also discuss the power of MIDI sequencing philosophy and how to apply it to notation play engines.




Começo elogiando o incrível trabalho. O Musescore é impressionante. A usabilidade é maravilhosa, o resultado e a execução também.
Gosto e uso a ferramenta desde a versão 2. É a melhor alternativa para o Avid Sibelius, que até parei de usar depois de ter experimentado o Musescore 3.6.2.
Queria de agradecer e elogiar o trabalho de todos vocês.
Gostaria também de relatar que, em meu computador, o Musescore 4 fica muito lento, a ponto de ser inviável utilizar, muitas vezes fechando inesperadamente, o que me faz perder parte do meu trabalho musical. Eu sei que pode ser um problema no meu computador mesmo, e não no Musescore. Eu uso Windows 10, Ryzen 7 2700, 16GB de RAM e 1TB de armazenamento. Não acho uma configuração tão ruim, mas vai saber... Gostaria de saber se mais pessoas estão passando por isso ou se tem alguma coisa que eu possa fazer, como usuário, para melhorar o desempenho e evitar que o Musescore feche na hora errada.

Muito obrigado pelo trabalho. Vocês são extremamente talentosos e empenhados.

P.S.: Não tenho imagens para postar como evidências dos problemas que descrevi, porque estão relacionados a desempenho.

The update was automaticly, but in this new version 4.0.1 I lost the mixer, I am trying by F10, Menu or select into quick access and doesn's show it, please could you fix or sent to me the previous version in order to continue work.
See the image attached.

Allegato Dimensione
Error.jpg 201.55 KB

When I said previous version I mean Musescore 4, because a version 4.0.1 I had the issue.
You sent to me a link in order to get any 3.x version.
I've created many pieces and this are not compatible with any version 3.x

Or try to fix the issue ir order to use the mixer.

Allegato Dimensione
Error.jpg 201.55 KB

I love MuseScore. I've been creating music with it (with my best friend, an ocean away) for approaching ten years now. I also just finally got to uploading some of our work to my profile, as a demonstration of what we use it for.
I am excited for version 4. But unfortunately, I'm one of those diehard Sf2 users; being able to switch between instruments on a single soundfont, manually, is a necessity for the kind of music I produce. And I am also a Linux user, so relying on older versions is.. less than ideal. (I can never get the UI to format at an appropriate size. Can't even add new drum notes, thanks to this. But that's what happens when you change computers; UI for deprecated software gets lost by the wayside.)
I'm not here to complain, nor question, nor rush the developers. I am here to vouch support for them and at least lend my vote to "yeah, implementing manual instrument preset switching is a Good Idea! that functionality has been crucial to at least one MuseScore user!"
I would love to make use of version 4. It looks, in all respects, absolutely ideal, refined, professional, convenient. I await that day with bated breath.

Hola a todos:
He instalado Musescore 4.0.1
En ppio. abría, y después de descargar librerías de sonido, ahora, al clikar acceso directo, abre 3 segundos, el cartel de inicio dice "cargando" y se cierra automáticamente, así siempre.
¿Alguien reconoce y ha solucionado este error?
Mi ordenador / computadora es un I5 11ª generación, 32Gb RAM, Disco duro NMWE M2

Generally speaking, I love musescore and was looking forward for any update.
Musescore 4 is so disappointing, makes it unwokable for me.

I do like some new features, but things that used to be so intuitive are no longer such.
couple of examples: hit tab, to skip to next measure when you writing chords.
no longer support tabs for different projects.
No camera for snips (or maybe there is, and I haven't noticed?).

There were more, but I really went back to musescore 3, which I hope they will continue and support, so I don't remember it all.
Completely different experience, and I hope with feedback, they will improve it.

In risposta a by fixingahole2

The shortcut for next measure in chord symbol edit mode simply changed, from Tab to Ctrl+Right (same as it is in note input and normal modes), both for consistency (and hence more intuitive to new users), but also to make Tab available for its usual function with respect to accessibility, which is extremely important.

The image capture tool is indeed temporaroluy gone while awaiting a redesign to fit the new UI, but meanwhile, all OS's provide similar functionality builtin (eg, Windows+Shift+S), so you can certainly continue to do the same sorts of things.

Separate tabs within a single are indeed no longer viable given the need to support the new playback possibilities. It only worked in MU3 because it forced all open scores to use the same soundfonts, but this just isn't practical with VST and Muse Sounds.

In risposta a by Marc Sabatella

Hi Marc, I read the manual and discovered the right arrow later, not sure why they had to change it though.
I appreciate all the updates, but this one seems drastic to me, but I will try to get used to it, to keep up.

Not really sure what the tab is doing now, it's just bringing a weird pop up, that I didn't try to get to the bottom of it, because I was trying to achieve something.

Re image, yes, I do this with windows + Shift + S, but it was a nice feature.

The lack of tabs is a big one, but again, I would rather stop complaining and try to learn it better.
As always, I am willing to help to make this product better, as I did in the past.

In risposta a by fixingahole2

As I explained, the change from Tab to Ctrl+Right is both for consistency with how you navigate measures measures in other modes - and consistency equates to intuitiveness - but more importantly, because Tab has a very special meaning for accessibiltiy, and accessibility is taken very seriously. Tab needs to be available for its primary purpose of navigating the UI and not also used as a command within the program, otherwise keyboard access to the program itself is compromised and blind users are locked out. Pressing Tab moves the keyboard focus from the score to the status bar, and from there to other controls, so that every control on the UI is always available without requiring a mouse. That is how Tab is required to work by standard UI guidelines provided by all OS vendors and accessibility standards.

The image capture facility will likely come back once there is time to redesign and reimplement it. But for now the OS builtin facility does well.

Not sure why the lack of tabs would be an issue on Windows - only macOS has the issues where multiple tabs all take space on the taskbar. On Windows and Linux, it's perfectly normal for documents to open in multiple windows, allowing you to easily cycle between them with Alt+Tab and also select from among your open documents by clicking the taskbar icon. But in any case, there is also discussion going on about how it might someday be possible to implement something that does allow multiple documents in a single window without the performance downsides that would normally result from this.

I'm super happy with the release of 4.0.1. As a light user, it really addressed two of the most important issues I've encountered (score corruption and NumPad keys).
You guys really nails the priorities. Thanks for the effort.

On 20 December, 2022, while testing Musescore 4.0.0, I posted:
"4. Another basic observation was that I did not hear anything when changing or entering a note.
The mixer window (F10) was completely empty, although I have selected the "Organ" instrument.
I simply restarted Musescore 4 and the playback/instrument issues were solved."

Unfortunately, this happened again, including with Musescore 4.0.1.
I even needed to close/restart the application several time before getting a populated mixer window and the ability to click on the play button.

I am aware that this is difficult to handle as this is not a systematic bug and there is no special trigger, the actions simply being:
- start Musescore
- click on one of the recently opened score
- press F10 to see the empty Mixer window.

Actualicé de M3 a M4 y funcionó unos días,al actualizar al 4.0.1 empezaron los problemas y ahora no se ejecuta,he instalado la versión anterior y tampoco, aparece la ventana azul y o bien se cierra o aparece una ventana de Windows que dice que hay un problema, las versiones 3 de Musescore si funcionan.
A alguien mas le pasa?

Anyone know if theres a way I can use musescore 3 while I wait for them to polish out this rough new development? I tried to just click on it but it wouldn't launch

In risposta a by Jojo-Schmitz

Thank you for the information; it works indeed now.
When Musescore 4 was released, simultaneous running did not work - thanks for having fixed this.
It will allow me to regularly test M4, although I still code my scores with M3, after a few stability problems with M4 and difficulties due to a few subtile changes in the keyboard shortcuts (even after fixing the numeric keypad issues).
I know that there are probably good consistency reasons for that, but it makes it difficult to keep blind typing skills with both versions. So I will do the switch when M4 maturity will be improved after more users feedback.
An example of difficulties: I just encoded a solo song + piano. I like to select only the song view on the screen when playing it for training, but M4 does not play the piano if it is not selected as visible.
Why can't I decide what I wish to hear?
Isn't this the role of the mixer?
Why is unmuting blocked in the mixer ?

In risposta a by Flying Roger

No, actually, MuseScore 3 & 4 have always been able to run simultaneously. I think it may have been the case that on macOS, depending on exactly how you went about doing the update, MuseScore 3 might have been uninstalled in the process, but it was always possible to have them both as well.

There were indeed a very small number of shortcut changes, these have been discussed extensively elsewhere so I won't repeat those discussions here, but bottom line - the changes were made for very important reasons, like improving accessibility for blind users, adhering to standard UI guidelines followed by other programs, and also making it possible to finally have default shortcuts for accidentals.

Regarding the muting, this change has to do with how parts work now, In the past it was never possible to add instruments to a part after the part was created, nor to remove them. Now both are simple. The way this works does indeed tie instrument invisibility to muting. But it's also simple to hide a staff without muting it, by hiding the staff instead of the instrument itself. This wasn't even possible in MuseScore 3.

If you have further questions, please start a new thread in the Support forum rather than responding here - it's much easier to keep the discussion focused that way.

In risposta a by Marc Sabatella

I am running Windows 10 and I confirm that during the tests of the initial version, Musescore 3 crashed when I launched Musescore 4. Maybe a sound or midi drive conflict?
Concerning the shortcuts, I understand that changes are justified; no criticism there; I just need to get used to the new shortcuts.
Being pragmatic : my encoding speed is drastically reduced if I have to regularly switch between M3 and M4, while M4 can read M3 scores and not the opposite. Therefore I still encode in M3.

Today, I had the idea that I should reset all shortcuts to defaults to benefit from recent fixes.
Indeed much better. I still need to get used to the "+" replaced by a "T", but i realise that it makes sense in English (Tied note). Less obvious in my language (French: note liée) ;-)
I have now added T for tied note in Musescore 3 to facilitate my transition. ;-) and I will regularly test my encoding performance with M4.

Update: concerning the mute/invisible issue, I found two interesting links:

In risposta a by Flying Roger

I like your idea of customizing MU3 to use the shortcuts that become the default in MU4, to help ease the transition! And yes, it's kind of unfortunate that so-called "mnemonic" shortcuts like "T" for tie end up being very English-centric. Of course, the same is true of a ton of other shortcuts, like "S" for slur, "R" for "repeat selection", etc. Sometimes they happen to line up in some other language, but often they don't. Anyhow, a nice advantage of "T" over "+" is that it is located near the letters you'd normally be using to enter notes, so so it fits the hand better if you're accustomed to using RH for duration, LH to enter notes.

And yes, that GitHub issue on the muting of invisible staves is a good read if you're wondering why the decision was made in the first place and what the complications are regarding changing it. But I do believe they have a good handle on how to address this going forward. Meanwhile, it does and presumably will continue to work to just hide the staff instead of the instrument - which in many cases is better anyhow, because often you don't actually need a whole new instrument just to have some notes play that don't appear in the score.

In risposta a by Marc Sabatella

T is not a problem as soon as you know about why it is "T" (same as for slur).
I have now adapted the shortcut in M3 and I am already getting used to it; easy when you do not need to change between M3 and M4.
Concerning RH/LH, I had rather considered that adding a tied note is kind of defining the duration, isn't it...? ;-)

In risposta a by Flying Roger

A tied note is indeed related to duration, obviously, but defining that duration is what you do before pressing T. Pressing T is what actually puts the note onto the score, same as pressing a letter. So, just as 6 C enters a half note, 6 T also enters a half note. The 6 is the duration, the C or T enters the notes itself. So if you're into a rhythm or L/R/L/R/L/R etc, T maintains it, whereas "+" breaks it.

In risposta a by Jojo-Schmitz

Yes, but I understand that the updated program would have the same or more functions than the old one. For me, that source is essential as I do a lot of methods for Recorder. Although Musescore 4 is more worked on and there have been several improvements, I will still be stuck with 3.6 due to the simple fact of font incompatibility. All that I said is just an observation. I've been using Musescore for over 4 years and I don't contribute anything financially. It's just an observation.

In risposta a by roninho aguiar

In general, all fonts that exist on your system should work in MsueScore - no changes were made that should affect fonts in any way. If you are having trouble with a specific font, please open a new issue, attach your score, the font itself, and give precise steps to reproduce the problem. Please do not use this Announcements forum to report issues.

In risposta a by roninho aguiar

I can't see how a video would help. What is needed is the font itself, the score itself, and precise steps to reproduce the problem. If the problem is that the font doesn't appear in the list at all, then a score won't be needed, just the font. But the support forum won't be seen by the developers - you need to open an actual issue, on GitHub (…).

I know you already have a million comments—but I've been using MS4, and I'm so impressed, I had to pass along my admiration.

The new interface is brilliantly clear and well organized. The combination of the new music font, and the more intelligent handling of note placement, ties, and other elements has completely overcome any perceptions I've had that MS wasn't "ready for prime time".

Out of curiosity, I tried Dorico SE, Steinberg's free basic version of their notation app. Even for this free version, you're required to create an account, install various security-related packages, and go through an elaborate online authentication/registration process. (A third-party app called "eLicense Control" also enters into it, though I'm still not sure how or why.) And while many people say Dorico's the easiest, fastest notation system, I found it scattered and unintuitive, and had to search the Web even for some basic operations. (Sure, it's not as bad as Finale—but is that saying much? 😁)

By comparison, MS4 is like a cool, refreshing breeze. One-click installs with Muse Hub (including the incredible new sounds!). No mysterious security packages or license/registration hoop-jumping. And everything's right there in the workspace, not hidden away in layers of complexity.

I think MS is in a position to revolutionize composing and arranging. Now any kid in his bedroom with the desire to learn about music has an entire scoring system and virtual orchestra at their disposal. It's so easy to use, and the results look and sound so good. You're doing more than providing tools for experienced musicians... You're encouraging new musicians to learn, create and grow.

Many people have commented on how much pop music has declined over the last few decades—how bland and formulaic it's become. I predict we'll soon see a new wave of musical depth, creativity and meaning, as MS empowers a new generation of composers and arrangers.

Thanks for all your hard work. What an amazing project MS has become. Cheers!

Posted in the 'made with MuseScore' forum, but here it is again.
I took the last couple of days to write the last piece in a suite of works dedicated to my family. This one is for the "hero" of the household, my wife.
As has been the experience, writing inside of MuseScore 4 is extremely volatile right now. If I were to file a bug report at this stage (4.0.1) it would read "M4 crashes... when I write music". I actually had to resort to writing and editing in MuseScore 3 while working on this. I know that they will work out all of the MANY bugs that are creating measure corruptions and unstable note/articulation/sample combinations that are causing crashes.
The good news is that the MusicXML export is working and all data transfers cleanly to M3 and then directly back to M4, as a workaround while writing (although a major headache). The render is a mastered copy of the .wav export directly from MuseScore 4 using the Muse Sounds. I am finding that the sample set is improving weekly and the results are absolutely stunning:

Will post a play through and breakdown video on this when I get the chance.



I can't believe how much of an improvement MuseScore 4 is over v 3. Most obvious are the new Orchestral Sounds. Incredibly good !
I am astounded by the intelligence and hard work in order to make so many amazing improvements. MuseScore 4 with these new great sounds, makes Finale, Dorio, and Sibelius, tremble with jealousy !
Certainly worth donating to help such great development, which is what I 'm going to do.

Thanks a lot,


Thanks for the v4.0.2.230651553 corruption-handling improvements!

I can't speak for everyone (that's my wife's job, LOL)—but on the rare occasions MS has told me a score was corrupted, it was because an edit I did had caused it to lost track of the beats in the 2nd voice of a staff. I've found that if I open the file (disregarding the warning) and erase and re-enter that bar, the file is OK.

So if you get the "corrupted" message in a score with multiple voices, look for one or more bars with missing rests and try redoing them. ;?)

Congratulations for the new update! A question: the glissando (as portamento) playback for woodwinds and brass removed, or temporarily not working? (Diatonic, chromatic, white & black keys glissando works, but not portamento - portamento works only for strings). In a previous score in MuseScore 4.0.1 a flute portamento-glissando (semitone) is played perfectly, even the file is opened with MuseScore 4.0.2 ! But I do not hear flute (or clarinet, trombone etc) portamento-glissando written in new scores with MuseScore 4.0.2.
I tried to write a portamento type flute glissando inside the score I was written with MuseScore 4.0.1 (but opened in 4.0.2) - the portamento-glissando played perfectly!

In risposta a by George Hatzimi…

It still works for soundfonts. The new Muse Sounds orchestral library currently has only limited support for it - only those instruments and note combinations for which recorded samples exist. Muse Sounds does not electronically simulate this or other effects the way a soundfont synthesizer does. That is part of how it gets its realism - when it works, it works great. But it does mean some things won't work, because there aren't recorded samples available currently.

In risposta a by Marc Sabatella

Thank you very much for the reply and for your time. With all due respect to you, and if I am not becoming tedious, I would like to ask again, because maybe it was remiss of me not to mention earlier that in the score I made with 4.0.1 that played the winds portamento-glissando I used the new MuseSounds (not soundfonts). So how is it explained that then it was implemented and now in 4.0.2 it is not. I think, if I'm not mistaken, that the portamento-glissando even in the sample libraries are done by electronic programming, not by sampling. And to make it more clear to me, let me add the following question: All kinds and any rhythmic texture portamenti-glissandi that are still performed in 4.0.2 (with MouseSounds) on the strings are the result of sampling or programming?

The instrument dynamics in Musescore 4 are very bad they have drastic volume changes when they aren't notated to. A mp sounds like pp and the flute part randomly jumps drastically in dynamics from mp (what is notated) to around ff. Does anyone know what this is or how to fix it?

I got around to testing Musescore 4. I have tried it during the beta and I'm still amazed by the work you do. The program would be incredible, if... well, if it was usable. I remember the first time I tried M4 and it had playback issues, dynamic issues and performance issues in general. 3-4 months down the line, two patches released, and as if nothing has changed. The same issues are still in the application.

The playback doesn't play some sounds or it plays them with delay. I thought it might be a problem with Muse Sounds, but it happens with the basic sounds too. If you don't open the mixer, then the playback is just unusable. The program in general has a lot of lag, which makes it hard to use. The dynamics in M4 are just terrible as other commenters have pointed it out, I can't even explain what is happening there because the workings of the dynamics are basically incomprehensible.

I know you have a lot of work to do, but these issues need fixing. I might need to reinstall the program or I don't know, but I don't think it would fix the problems. I hope you get around fixing these problems as soon as possible. Until then I will stick with the M3 version I still have on my computer. Best of luck!

In risposta a by gyurto

Sorry to hear you're having trouble! It isn't really clear what you mean here about playback in general - there are indeed some documented issues affecting a small number of systems, and there are workarounds for most, so I encourage you to start a new thread in the Support forum and describe your specific problem and your system configuration (OS, audio harware & settings, etc), and then someone may be able to assist. Also, if you have a specific score where dynamics aren't working as you expect, please open a separate thread for that. In general, dynamics should be working normally, but there are a handful of open issues involving specific notes on specific instruments being louder or softer than they should be. it's possible your score is demonstrating one of those known issues, or it might be a different issue, or it might simply be a misunderstanding about how the new velocity system works.

We're here to help, so I look forward to seeing your threads in the Support forum!

In risposta a by Marc Sabatella

Dear Marc,
I am surprised to read that these problems "only affect a small number of systems".
My experience is the same as described by gyurto, except that I did not specifically test sounds dynamics.
I regularly test M4, looking for a possible update solving the problems, but despite appreciating the new interface, I stopped using M4 due to the same other basic issues. These have already been extensively described on bithub by several users, including myself.
On top of that, crashes have regularly occurred without doing anything special, and it is hard (often impossible) to get midi-out working despite proper selection of the I/O in the options. I only hear a very weak piano note, in sync with the beat (even if the metronome is not selected). Strangely, midi-in works fine.
I regularly test on on my desktop PC (Windows 10), and sometime also on my laptop (Windows 11).
My latest tests today were on Musescore 4.0.2 and I did not observe any improvement on these problems.
So again, back to M3.

In risposta a by gyurto

I'm glad I read this comment. I have the exact same playback issues and lag! The lag is really bad when trying to insert notes using your keyboard. With M3 it used to be effortless. I think the improved sound of the notes have something to do with this lag in M4. I'm sad to hear that two patches have been released with no change. (I only installed M4 yesterday).
Once you hit play trying to stop the music doesn't work either. It will continue to play until the end. And then the beach ball comes.
I will also be going back to M3 today.

This company, behind musescore, charged twice , total almost $ 200.00 for something I did not sked for and have not refunded the money. SHAME on them

So why does my Musescore 4 keep opening instances of the app each time I open a scores. Musescore 3 opened them in tabs in the same windows. This is nuts. I have 5 scores open in different 5 different instances. My dock has 5 icons of musescore.

Please help.. Its impossible to work like this. :(

Allegato Dimensione
Screenshot 2023-04-11 at 17.32.49.png 30.31 KB

In risposta a by newmozart

It's not impossible at all, although macOS does indeed make it more awkward than need be (the dock icons should be all combined as they are on other systems). Anyhow, the reasons for this are explained in various posts on the Support forum and have to do with allowing different playback setups per score, which wasn't needed when all you had were soundfonts but is pretty crucial when dealing with Muse Sounds and VST instruments.

If you have further questions about how to use your operating systems for managing between open applications (eg, use of Cmd+Tab), please ask on the Support forum.

In risposta a by newmozart

That's not quite what I said. the need for multiple instances is to make sophisticated playback options possible within making switching scores painfully slow. That is unlikely to change. However, the fact that macOS makes working with multiple instances slightly less convenient than other systems is unfortunate, so workarounds or alternate approaches are being investigated.

Meanwhile, it really isn't that hard to work with multiple instances even on macOS. I encourage you to ask for help on the support forum and describe what issues you are finding using Cmd+Tab and the other capabilities that are provided, and other Mac users can probably assist. There is no reason to have to forego the incredible advanced in engraving, playback, and overall usability just on account of a few extra icons!

In risposta a by Marc Sabatella

thank you all this time to explain, Marc! You're a star!
Yes, Mu4 is really great and I will try to make it work once the playback issue is sorted.
If Musescore can someday get it to work like, lets say, pages or preview or finder windows, where a simple swipe down with four fingers will reveal all the open instances of that app (yet keeps only one icon) now THAT would be super!!

Sorry.. I seem to have another problem.. When I play back the score (Crotchet = 80) The first two bars plays at 80 and then it defaults to 120. and what is really weird is the playback Beam that follows the notes during playback seems to go at =80 . Then the entire things would just get stuck .. and the beach ball would make its appearance.

So sad.. :( Is there anyway to downgrade to Musescore 3 please?

In risposta a by newmozart

There is a known temporary glitch where the playback is incorrect at first after making certain types of changes, then fixes itself as soon as the playback info is regenerated. In order for us to understand and assist, please start a new thread in the Support forum and attach the score so we can advise better.

In risposta a by newmozart

If you are encountering a bug, again, please ask for help on the Support forum so we can assist and guide you in reporting it to the developers if it turns out to be one not already known. Therre are no known issues that should prevent anyone from using MsueScore 4, so if you are encountering one, it must be something very unique to your system or your score, and we'd need your help in confirming it. So once again, *please8 asl for help on the Supprot forum so we can understand and assist. Bugs can only be fixed once they are properly reported.

In the Hebrew version, the openeing screen is being cut as in the attached photo. I believe that the same thing happens to all right written languages such as Arabic. I don't believe it's important, but it's the look of the software.

Allegato Dimensione
תמונה2.png 765.2 KB

It's been a few months since Muse Sounds was officially released and I was wondering if there is still work being done on it? For example, is there a plan to implement fixed velocity/manual velocity adjustments to Muse Sounds? Because right now, articulations and dynamics are incredibly inconsistent. This is most noticeable when writing/transcribing chamber music (e.g. imbalanced sounds and clumsy articulations) .

Best regards. Will the audio effects in the mixer of the Linux version be useful in the future? Support for vst and lv2? Will this vitally important part only serve on windows and mac? Thank you for your answers.

Allegato Dimensione
Musescor no fx.png 204.95 KB

In risposta a by discarlosrobl1

VST for Linux is listed on GitHub as being a priority for 4.1, and "contributions from the community are very welcome". The effects on Windows and macOS are already based on VST, so presumably that would come for free. But also a new aux send system and native reverb is being worked on, and what's there so far is already working on Linux. LV2 is also listed as being on the roadmap for 4.1. I guess it will come down to how much the community steps in to actually implement this...

Hai ancora una domanda senza risposta? Effettua l'accesso per prima cosa per porre la tua domanda.