Why Upgrade to 4.0 when 3.6.x works just fine
Your software philosophy leaves much to be desired. There's a whole host of features that 3.6.x has that 4.0 does not. Usually, upgrades are exactly that. They add more features, not take them away. I see no reason to move to 4.0 as it is NOT A TRUE UPGRADE
Comments
I agree in part. I feel it is less an upgrade and more just a different program. Different features. Different workflow. Different sounds.
It just depends on what someone is after. Playback is the most important for me, so MS3 is not "just fine". There are some pieces that are dull in MS3 that come alive in MS4. Is MS4 perfect? No. But it is coming along.
After reading your post allow my to sharpen your question to the following wording: "Why downgrade to 4.0 when 3.6x works just fine."
I will try to answer that question: You could do so in order to get a better look and sound
and pay for that with functionality, performance and stability.
However, that's nothing I would do. You can still use both versions though:
MU3 for writing, MU4 for audio export.
In reply to After reading your post… by oMrSmith
Both versions have merits. I almost wish they would be completely distinct, so that there's absolutely no way that file changes could arise by accident. I know that some think this doesn't happen, but it does, and until MU4 is much more stable and secure then some users will experience problems. Eventually most of the problems with MU4 may be solved, at which point most people may be happy to migrate.
In reply to After reading your post… by oMrSmith
I think that MU4's lack of stability should not be understated. I find it crashing often (especially when changing MIDI devices or audio outputs), and files regularly get corrupted (which can only be fixed by unzipping the mscz file and opening it in MU3). For me, the superior playback is definitely amazing, but that is pretty much the only thing I find myself wanting over MU3.
In reply to I think that MU4's lack of… by excel8392
Can you post a link to the specific GitHub issues you've filed that are getting in your way? Work is progressing on 4.0.2 and they're trying to fix all reported crashes and corruptions.
Actually, almost all known corruptions are already fixed for 4.0.1, so you shouldn't still be seeing new corruptions. But FWIW, just today I discovered an interesting fix for some cases where parts got corrupted previously - open the part, then go to the instruments panel, click the settings icon for the instrument in question and "Reset all formatting".
There's actually a pretty small number of features missing, but indeed, if you happen to rely on one of them and the available workarounds don't work, that could be a problem. But to be clear: the improvements are enormous. The default playback has gone from the worst among the major notation programs to the best, and same is almost true with respect to the default engraving (Dorico can probably still claim to be better). That plus improved workflows and a host of other improvements, make it a non-brainer for the vast majority of people.
In reply to There's actually a pretty… by Marc Sabatella
Well, your definition of small doesn't match mine, but here's the full list: MuseScore 3 features not (yet) implemented in MuseScore 4
In reply to Well, your definition of… by Jojo-Schmitz
That list is already somewhat out of date, but most of these are very minor things that the vast majority of people would never even notice, or that have trivially simple workarounds. The number of things that actually impact workflow in a significant way for a significant number of people is what I consider to be relatively small.
In reply to Well, your definition of… by Jojo-Schmitz
Doesn't include lack of text formatting for most line styles. That is the major thing I will have to re-edit on every MS4 score.
In reply to Doesn't include lack of text… by memeweaver
IIRC that is a known issue
In reply to Well, your definition of… by Jojo-Schmitz
Really glad to see you have that list. At a superficial level MU4 is an improvement on MU3, but some of the problems start to become more obvious with more complex scores, and using multiple libraries. Some of us have been trying to write pieces to test MU4 out. See https://community.masteringmusescore.com/c/musescore4-discussion/ and https://community.masteringmusescore.com/c/share-your-music/
Sometimes it works well, but other times it falls over. Even "stupid" things, like not being able to abort the program without forcing it to Quit don't always work. Sometimes for no very obvious reason, playback will default to just one instrument line - and here I don't mean the now known issue about not selecting bars rather than notes before hitting space or the the play "button".
The MU4 project is going in a good direction - but it's nowhere near a fully workable system yet.
In reply to There's actually a pretty… by Marc Sabatella
The Development Teach should take down 4.0 until all the bugs are fixed and until 4.0 does everything the previous version does. The release of 4.0 was PREMATURE!
In reply to The Development Teach should… by DavidJustinLynch
The best way out of this, I could suggest, is to simply re-release MU4 as Early Access.
In reply to I see only one good middle… by oMrSmith
There had been Betas and an RC, you should have used those to test and report bugs.
In reply to There had been Betas and an… by Jojo-Schmitz
So I did. What I mean is this: An early alpha doesn't become a full version just by changing the label.
I have been watching the development closely and all of a sudden - 1000 issues open on github - MU4 had been released. I opened the program and it took me 30 seconds to find out that chord symbols of transposed instruments would play back transposed. Not even the numpad was working on initial release. In the meantime these two have been fixed. But clearly MU4 hasn't been tested properly. In fact the testing is happening now. The only problem is that people are not informed that they are taking part in an experiment which can even corrupt their scores.
Found after 10 seconds:
![Unbenannt 2.JPG]( "Unbenannt 2.JPG")
In reply to I did so. What I mean is… by oMrSmith
And by the way: Why does clicking on the old hide symbols
(which don't work no more and should have been gone anyway)
change something on the key signature lane?
In reply to And by the way: Why does… by oMrSmith
It's not clear what you are referring to here, but if you believe you have found a bug, please start a new thread and describe it in more detail. Then if it is confirmed to be a real bug. you can open an issue on GitHub.
In reply to It's not clear what you are… by Marc Sabatella
https://github.com/musescore/MuseScore/issues/15211
In reply to It's not clear what you are… by Marc Sabatella
I don't believe that this is a bug, I know it is which is why I have already filed it on github last year.
It's not an important issue though, more like clutter that hasn't been cleaned after ending the construction side. What it shows is a lack of systematic testing.
In reply to I did so. What I mean is… by oMrSmith
@oMrSmith. But the fact remains that MS4 was released. I think that the way forward is to use it and report things that don't seem to work. And move on. All the complaints about being released too soon don't help anything. We all have our list of things that need improvement. My list below doesn't stop me from preferring MS4 to MS3. If everyone just quits using MS4, how will it get improved? I don't tend to use many of the things people say don't work. But that's just me.
In reply to @oMrSmith. But the fact… by bobjp
I use Musescore 3 to render organ music. I cannot change soundfont sounds mid-staff in version 4. That makes the program mostly useless to me.
I keep hoping this will get fixed, I have reported it, and I'm not seeing a whole lot done about it. I hope to heaven someone will fork version 3, or something like that, so it will continue to be improved.
In reply to I use Musescore 3 to render… by Chuck Bermingham
I'm using the 3.7 fork which has fixes and enhancements over 3.6.2
See: https://musescore.org/en/node/342126
In reply to I use Musescore 3 to render… by Chuck Bermingham
Actually, you can change soundfonts mid-staff, bvy adding instrument changes. What you can't do is change sounds within a single soundfont. But this is planned for 4.1. Meanwhile, since you can change soundfonts, you can use a collection of separate soundfont files instead of one file containing multiple sounds. Or, use VST instruments, which are generally superior anyhow.
In reply to Actually, you can change… by Marc Sabatella
Unless Mr Bermingham uses Linux of course (he does, see https://musescore.org/en/node/329280)
It is remarkable that the possibility is not even considered anymore.
Are you serious about 4.1 being released in a couple of weeks? VST (and lv2) for Linux may be be planned for 4.1, but i don't think anybody really believes this. We will see.
In reply to Unless Mr Bermingham uses… by graffesmusic
VST is indeed not hyet available on Linux, but split soundfonts are, and 4.1 will support selection of individual sounds on all platforms. The last announced projected schedule called for July, and I haven't heard anything to make me think that can't happen, but as with all projections, it's just an estimate, and it may slip until Linux. So far I haven't heard any of Linux-based developer sufficiently concerned about VST or LV2 support volunteer to implement it, so if they don't step up and get to work soon, it may wait for another release. Hard to say - as is always the case in the open source work, things get implement when people with an interest in it volunteer to do the job, and so far no one with an interest in this has volunteered.
In reply to VST is indeed not hyet… by Marc Sabatella
Yeah, if it is not done, it is because nobody showed up to do it.
One can put anything in a github project.
In reply to Yeah, if it is not done, it… by graffesmusic
I sense that you meant that to be sarcastic, but to be clear: the first sentence is absolutely true, and the second is false. One can of course put anything into one’s own fork, but to then have your changes merged into the actual release, they need to be approved by the design & development teams. But they already announced they have pre-approved the design. So it’s just a question of whether the code works and follows the appropriate style guidelines etc. the team works regularly with the community on this sort of thing; that process is very much in place already. So it really is back to your first statement.
In reply to VST is indeed not hyet… by Marc Sabatella
4.1 does not allow me to select individual sounds; instead, I must use Marc'ssoundfont splitter.
He did do a nice job of organizing the MS Basic split soundfont into categories, but those categories do not appear in the mixer.
I guess we will have to wait and see. Meanwhile, back to actual work on 3.6.2.....
In reply to 4.1 does not allow me to… by Chuck Bermingham
Indeed, you have special sound font needs. I get it. Just like I have no use for MU3. None. For actual work.
In reply to Indeed, you have special… by bobjp
Maybe so, but it's been said that the soundfont management would be in 4.1 and it's not. Since I need that to work, I use 3.6.2. You're perfectly free to have no use for whatever software you desire to have no use for.
In reply to I did so. What I mean is… by oMrSmith
As you should be well aware, there were months of testing - public alpha and betas. But you cannot possibly find every single bug during alpha or beta testing. Expecting any piece of software of this magnitude to be 100% free of bugs is absolutely ludicrous. It's never once happened in recorded history, and if it ever happens in my lifetime, I will buy you a house.
In reply to As you should be well aware,… by Marc Sabatella
To be fair, some of the bugs that were pestering us in 4.0.0, had been reported well before public Alpha. Like the shortcut issues, reported last July already, IIRC.
In reply to To be fair, some of the bugs… by Jojo-Schmitz
Indeed, but also, it's hard to know the scope of some of those issues. For example, every release of MuseScore has had issues where some people on some operating systems with some language settings and some keyboards had issues with some shortcuts. It was by no means apparently before release of 4.0 that the issues in 4.0 would turn out to be more widespread. And with respect to some missing features - like abiltiy to select individual sounds within a soundfont - it was a conscious decision not to delay the release, hoping that for most people, ability to use VST and Muse Sounds would be a more than acceptable workaround. Again, it's difficult to predict just how many people would actually be affected. I personally would have chosen to make sure that particular feature was implemented that before releasing if I were king of the world, but then I probably would have let something else slide that would have annoyed someone else. It's virtually impossible to please everyone all the time.
In reply to The Development Teach should… by DavidJustinLynch
I, for one, vastly prefer MS4. Even with the problems. I stopped working in MS3 some time ago.
In reply to The Development Teach should… by DavidJustinLynch
That's simply preposterous. Not a single piece of software ever in the entire course of human history has been bug-free. If the metric was "don't release until all the bugs are fixed", we'd still be using the abacus.
Meanwhile, as mentioned, if yhetre is a specific MU3 feature you need that you can't workaround, simply keep it installed. No need to deprive the vast majority of users of the ability to enjoy the enormous improvements in MuseScore 4 while those few remaining features are being worked on.
In reply to That's simply preposterous. … by Marc Sabatella
An Open Source mantra is "Release often, release early". MuseScore at least did the latter ;-)
In reply to That's simply preposterous. … by Marc Sabatella
Whats wrong with the abacus? Are you an anti-abacustite?
In reply to There's actually a pretty… by Marc Sabatella
True. Playback is much better. But hardly Best. Instruments also need separate vibrato and legato fonts. And combination vibrato legato. Slurs need to work. And a setting to control percentage of note length. Not to mention all the many instruments that are missing. How about that reverb? And string instrument swell? Really?
In reply to There's actually a pretty… by Marc Sabatella
Marc,
I know that I have already pushed back on you in other areas related to Jack. But I have to say again, that this response "There's actually a pretty small number of features missing" is... well I can't say what it is without sounding accusatory, but it's either ignorant or it is gaslighting. M4 is missing entire suites of features that M3.x (and even M2) had. Some features that seem like they are singular (like piano roll) are actually a description of an entire editing suite, with loads of power related to midi data and porting to instrumentation.
If you need people to sing the praises of the new play engine and the Muse Sounds, I'll happily be the first in line to do it. It's phenomenal. In the right hands, it's easily the best and I wish that the interface would let me use it in a streamlined and productive way for media music composition. But the criticism remains... they threw out about 80% (and that's probably a conservative estimate, as I didn't use everything that M3 had to offer) of what the program could do. Granted, it might be an 80% that you personally never used, but it is gone now. The fact is that many of us with the 'know-how' could already make M3.x sound pretty amazing using these tools that are gone with external sample sets and DAW integration. We welcome the new engine, but the new engine has limits that won't and can't satisfy needs regarding control at the note by note midi level that we had with M3. Listening to Tantacrul talk about the playback upgrade related to traditional midi playback engines, one could wrongly get the impression that midi is an antiquated platform. It isn't. It is the "varsity league"... and as such it isn't particularly user-friendly for the average person. But nonetheless, if you want your music software to be powerful, you will need to incorporate a suite of midi controls like what M3 had.
I saw a suggestion made by you on another thread when this came out about how the M4 playback engine could replace a DAW. That can't be true. They have made a great engine that works off of the notation, but the control and routing that a DAW provides is not something that the M4 engine can overcome without providing note by note data access and working portability to external instruments. And even then, it operates on literacy in notation (which obviously is the point of a notation program), but music playback isn't necessarily about notation. The notation is extremely 'relative' and they can't generate an algorithm or sample set that gets it "right" even most of the time without some level of note by note access to the underlying data.
I just think that this whole release as the flagship was premature. It creates the 'sense' that the clock is ticking down on powerful, work-driven features that will be lost forever. That may not be true, but that is the sense that is there and some folks (like me) won't be satisfied until someone flatly says "We are bringing all of this back, in time. Feel free to use our available and highly recommended M3 release for your day to day work until we get all of your tools integrated again." Nobody is committing to any such endeavor. On the contrary, the situation very much feels like a turn on the 'chopping block'.
In reply to Marc, I know that I have… by cfirwin3
Please refrain from the personal attacks.
I stand by my statement: in the grand scheme of things in a program with literally thousands of features, there are only a handful missing, many of them niche features that 99% of users never probably even knew existed. That doesn't meant won't be great to someday have them reimplemted, and I'm sure that will happen over time.
Anyhow, so indeed, if you personally happen to need one of the missing features and the workarounds are not sufficient, that could be a reason for you personally to stick with an older version. But for the vast majority of users, there simply is no reason whatsoever not to be using MuseScore 4.
In reply to Please refrain from the… by Marc Sabatella
I'm not attacking you. It's just that these claims about missing features (quantity and use) aren't true and I'm trying to understand why you are saying them. I'm not compelling folks to stay away from M4 at all. I have already used M4 in professional work since its release, where I only needed traditional instrumental sheet music and the benefit of a good mockup audio file (that's what the program can do right now). I also don't see how this '99% of users' language is useful. 99% of users don't use the professional production features that other notation programs offer either. But the features matter because they are used by the folks and studio environments that need them. And again, because apparenty isn't being heard, being told to use the old program isn't a good option if those features are terminated in the future. Some of us in the 1% are looking for some empathy and assurances here and coming up empty. For some context, I have zero interest in being among the 99%... who wants to be among the 99%? That can't be a forward-thinking model for revolutionary software, can it?
Marc, I respect your commitment, time and effort. I will walk away and avoid negative engagement in the future. I understand that I have overstayed my welcome on this issue and I have more than spoken my peace. I am very sorry for any offense that I have committed. Offense isn't my goal.
Thank you for taking the time to respond as you have.
In reply to I'm not attacking you. It's… by cfirwin3
I have stated nothing that is not true. But calling me ignorant is a personal attack. I too will be bowing out of this discussion, as time is too precious to waste arguing. Thanks though for the apology.
In reply to Marc, I know that I have… by cfirwin3
Yep, well written. The dismissive explanation of "just one feature" is definitely gaslighting. imho.
To use a vehicle analogy, it's like comparing removing the motor, to removing a wing mirror. Both are "features", but one affects the operation profoundly more than the other.
You're not the only one who feels the chopping block has definitely had a workout.
The homepage announces MS4 as a "gigantic overhaul" – which it clearly is – but it doesn't explicitly state that it's an upgrade.
Anyway, 12-months from now the dust will have settled and a stable version of MS4 with missing features added will be being enjoyed by 1000's of score writers alongside 1000's of other score writers happily using MuseScore Classic, (3.6.3, 3.7.0 etc. which already has many 3.6.2 issues fixed).
So, a huge thank you to all the developers who have contributed to this amazing project.
In reply to The homepage announces MS4… by yonah_ag
Could you give me a hint, where I can find MuseScore 3.7? Didn't even know about it.
In reply to Could you give me a hint,… by oMrSmith
It doesn't really exist, but as a development build, see https://musescore.org/en/node/342126
In reply to It doesn't really exist, but… by Jojo-Schmitz
Which shows that it does really exist – it's just not a released version and doesn't have an installer as it runs more like a portable, alongside 3.6.2 and without interfering.
In reply to It doesn't really exist, but… by Jojo-Schmitz
Hui, this looks like a huge update! So I just have to figure out, how to make a portable version of it...
In reply to Hui, this looks like a huge… by oMrSmith
It is sort of portable, in the sense that it doesn't need to get installed (it even cannot get installed)
In reply to Hui, this looks like a huge… by oMrSmith
You don't need to make anything. Look thru the details of the thread above and you will find that you only need to unzip it twice, (I put its main folder into Windows\Program Files), and it's ready to run.
In reply to You don't need to make… by yonah_ag
The github page overwhelmes me. Is there like a link, that leads directly to the zip archieve,
you have mentioned?
In reply to The github page overwhelmes… by oMrSmith
Start with https://musescore.org/en/node/342126#comment-1173267
In reply to Start with https://musescore… by Jojo-Schmitz
Ok, thanks, I will work my way through it. Are you also working with this build?
In reply to Ok, thanks, I will work my… by oMrSmith
I made it ;-)
(the build was done by GitHub CI, but the PR is mine, and I largely work with my own build, made from the same source locally on my computer)
In reply to I made it ;-) by Jojo-Schmitz
Nice, this version already puts headers and footers inside the page margins...
In reply to Start with https://musescore… by Jojo-Schmitz
Ok, I got it! Thx. Didn't know it was so easy.
In reply to The github page overwhelmes… by oMrSmith
Would it be worth a step-by-step installation guide in the Dev forum?
In reply to Would it be worth a step-by… by yonah_ag
I would like step by step instructions. :)
In reply to I would like step by step… by xavierjazz
Then try the one linked to my n the link above...
Or here: https://github.com/musescore/MuseScore/wiki/Downloading-and-running-tes…
In reply to Then try the one linked to… by Jojo-Schmitz
Nice instructions: saves me some work.
Note that for Musescore 3 you run Musescore3.exe rather than Musescore4.exe in the bin folder.
You can also move the top level folder to anywhere that's convenient, e.g. Windows\Program Files and then pin the .exe to your start menu. (If you rename the .exe first then it will have that name when pinned, e.g. MuseScore 3.7.0, MuseScore Classic etc).
In reply to Nice instructions: saves me… by yonah_ag
I've added those instructions to the PR now
In reply to Then try the one linked to… by Jojo-Schmitz
Thank you.
In reply to The homepage announces MS4… by yonah_ag
That 3.6.3/3.7.0/Classic/... is a huge and good news!!
MS4 could be someday a great MuseScore version, but for the time-being it is not. IMHO, not integrating the Plugins is the biggest mistake done by the core development team.
In reply to That 3.6.3/3.7.0/Classic/… by parkingb
? What would it even mean to "integrate the plugins"? The whole point of a plugin is to provide functionality above and beyond what it makes sense to incorporate into the main application.
In reply to ? What would it even mean to… by Marc Sabatella
> What would it even mean to "integrate the plugins"?
Please read "implement a working Plugin mechanism in MS4.0".
As @yonah_ag, my workflow relies heavily on plugins. Including my own Duration Editor, Batch Convert, and many other ones. 60% of the plugins I'm using are just not working in MS4.
And as per Tantacrul's last comment having a working and complete plugin mechanism in MS4.x does not seem for soon.
In reply to > What would it even mean to… by parkingb
Most of them probably just need simple changes to start working. The plugin interface has never been "complete: by any reasonable definition, more a set of cobbled-together properties and functions. It is definitely planned to overhaul this and actually make plugins more fully functional than ever before. But, holding up the entire 4.0 release over that did not seem wise.
In reply to Most of them probably just… by Marc Sabatella
> Most of them probably just need simple changes to start working.
This is a common argument among the MS4.0 dev team (which, btw, is really optimistic). And trust me, I tried to migrate most of my plugins, with little success.
But anyway, this discussion is labelled "Why Upgrade to 4.0 when 3.6.x works just fine ?". And I gave my opinion. This plugin issue is a show-stopper for MU4.0 for anyone using plugins in his workflow. That's one reason for not using 4.0. Among others.
In reply to > Most of them probably just… by parkingb
It's a showstopper for anyone who relies on one of the specific plugins that can't be made to work easily, you mean - most really do work or can be made to work simply - it's optimistic because it's good news and true :-). But indeed, if you happen to completely rely on a plugin that is not easily fixed, that could be a reason to stick with 3.6.2 for now. That probably applies to around 0.1% of users, so it's important to be extremely clear that this really doesn't apply to the vast majority of users.
In reply to ? What would it even mean to… by Marc Sabatella
The point is: The plugin interface allows everybody to add features to musescore
without having to wait for them to be recognized as essential or important enough to get
worked on. For example: I wouldn't write bigger scores with a notation software, which doesn't allow me to copy system breaks between score and parts. MU3 can do so with the help of a plugin.
In reply to The point is: The plugin… by oMrSmith
@oMrSmith which plugin are you using for this?
In reply to @oMrSmith which plugin are… by parkingb
https://musescore.org/en/project/export-layout-breaks-parts
All it does is to copy the system breaks of the score to all parts,
but still this saves me hours. I can't live with random system breaks.
In reply to https://musescore.org/en… by oMrSmith
Can you explain more about your use case? It would be pretty incredibly rare in any real world use cases for all parts to use the exact same breaks, and virtually unheard for them to have the same breaks as the score. The musical content is normally way too different for this to make sense. Better to start a new thread for that discussion, though. Probably whatever it is you are trying to do is better done a different way, but it isn't clear without examples.
In reply to Can you explain more about… by Marc Sabatella
We can open a new thread but I'll try to give you my short answer already: I like to control the system breaks for all parts and not let spacing determin them but the musical form, which I also try to lay out in the score as much as space allows... All parts share the same musical form. This does of course not mean that all my parts will end up with the same layout, but(!) starting with the layout of the score gives me a much better starting point. The plugin is not perfect and does not give me as much control as in Sibelius but it is still better than not beeing able to copy systembreaks at all. In general it would be helpful to copy and paste systembreaks.
In reply to We can open a new thread but… by oMrSmith
FWIW, the plugin works as soon as you edit it to replace Qt.quit with just plain quit, same as most other plugins. Also the version check needs to be fixed. And it could use a title. But as far as I can tell it works perfectly otherwise.
In reply to Can you explain more about… by Marc Sabatella
Other use case: I'm writing jazz pieces. And I like to have all the parts laid out the same way. So that I can produce 1 part per voice, for C and Bb instruments. So that whoever is in the band that day, he receives a score with the same structure. It is easier and faster for the musician for reading the score and switch from voice, if we decide to switch who is playing what.
I also like to structure my pieces wit 4 bars/line. So I set a small measure width to ensure that even 4 dense bars fit on one line and I use line breaks every 4 bars to get the expected visual structure.
In reply to https://musescore.org/en… by oMrSmith
Try this
In reply to Try this by Jojo-Schmitz
This will definitely be helpful for those who are using MU4! The next thing I'm gonna try though is MU Classic from Meister JoJo.
In reply to This will definitely be… by oMrSmith
And you should. It works fine here. (linux x64)
In reply to That 3.6.3/3.7.0/Classic/… by parkingb
It looks like the priority was to make a first release featuring the new sound system. The plugin API is also a major part of my workflow but I don't know whether most users rely on it. Managing stacking order and using ctrl-click are also important to me but these are not included, and are almost certainly not high on many wish lists.
I'm confident that the developers made their choices carefully and that these features will come in future updates.
The workaround for all missing features is to use MS3 for scoring and MS4 for playback. Just keep an eye on the release details to see when MS4 has the features that you need.
Almost every time I use Musescore 4.0.2 it crashes. I thought that with 0.2 that issue would be fixed, nut seemingly nothing has changed. I just lost the start to a piece that I hadn't saved yet, and it no longer allows me to reopen unsaved sessions, so I get to spend the next hour trying to remember what I wrote. There have been literally zero noticable improvements to Musescore 4, so I am just going back to 3.6.