MuseScore 4 Update: Announcing our Beta Release!
Hey everyone,
Today, we are delighted to announce the Beta release of MuseScore 4! The links below are for our new Muse Hub installer application, which can be used to install and update MuseScore and download / install our new orchestral plugin Muse Sounds. See the bottom of this post for more information and help with Muse Hub installation.
Note: For the beta release, MuseScore must be installed using the Hub for Muse Sounds to work
Linux users will need to install MuseScore 4 separately. Here are the links to install the beta release directly:
Linux - https://github.com/musescore/MuseScore/releases/download/v4.0_beta/Muse…
Please note that the Muse Hub is not yet working with screen readers. For those wanting to download a version of MS4 directly, please use these builds. Please note that these builds do not work with Muse Sounds.
Windows - https://github.com/musescore/MuseScore/releases/download/v4.0_beta/Muse…
Mac - https://github.com/musescore/MuseScore/releases/download/v4.0_beta/Muse…
Known Issues for MuseScore:
-
We have tested the Muse Hub on various Linux distros but are expecting issues with others. For those experiencing problems with any aspect of the Muse Hub on Linux, please log your issues on the MuseScore GitHub: https://github.com/musescore/MuseScore/issues
-
There are some remaining performance issues with Muse Sounds. For example, with larger scores, playback may sometimes take a few moments to 'catch up' after you press the play button. You may also experience lag and dropouts. If so, please first try going to preferences > I/O and setting the buffer size to 2048. If you still experience problems, please log your issues on Github (link below).
-
When saving a score privately to MuseScore.com, it can sometimes get marked as a public score
-
When using Muse Sounds, audio feedback during note input can often be marred by delays, stuttering or repeats. This does not occur during playback
-
Some instruments are mapped incorrectly to Muse Sounds. Bear in mind that Muse Sounds does not cover the entire instrument list anyway, so many niche instruments will simply revert to MS Basic.
-
Piano pedal markings are not producing sustain effects reliably for Soundfont, VST and Muse Sounds
Features added in Beta
- Our new orchestral plugin, Muse Sounds
- Saving to cloud on MuseScore.com is now working
- An improved system for publishing to MuseScore.com
- A simple toggle for switching between playback profiles (MS Basic and MuseSounds)
Tutorials
- Saving to cloud: https://youtu.be/6LP4U_BF23w
- Installing Muse Sounds: https://youtu.be/n7UgN69e2Y8
What else is in MuseScore 4?
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. https://musescore.org/en/node/330793
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
Reporting issues
- We strongly prefer issues to be reported on GitHub until we release MS4 (this requires a GitHub account): https://github.com/musescore/MuseScore/issues
- Alternatively, you can submit any issues you find on our issue tracker: https://musescore.org/en/project/issues/musescore
About playback
The largest changes we have made have been to playback - a technical investment we decided to make now. It is the sole reason why the timeline of MuseScore 4 was extended beyond 2021. Once you hear Muse Sounds, you'll understand :)
- The audio engine in MuseScore 4 is completely new
- There is an entirely new playback events system, which can produce much finer and detailed instructions. These translate to both MIDI and also MIDI 2.0 (which will be advantageous once MIDI 2.0 libraries and products start to become available). The advantages of this system will be properly realised once our new orchestral library, Muse Sounds is ready (in the Beta release).
- It is also worth mentioning that we have not been able to carry over the systems for mapping and prioritising sounds from MS3. There are two reasons for this: the first is that it is quite technically incompatible with our new system. More importantly, it is not a universal system that could also work with VST. As a result, our highest priority for MuseScore 4.1 is to reintroduce universal systems to allow users to assign sounds to articulations and text instructions. We will also be adding other types of standard VSTi capabilities too, including key switches and automation.
- We anticipate that there will still be issues with various different VST plugins. We would greatly appreciate it if you would submit any issues you find
- Please note that when first loading MS4, there is an option to download Muse Sounds. This option will not work until the Beta release
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.
Muse Hub Troubleshooting
- If you find that the downloads aren't starting:
- You may need to reinstall the helper application. Right click on the HUB logo and choose "reinstall helper". You may then need to restart the hub itself as well.
- Make sure you're connected to the internet and have access to the web
- If Muse Hub fails to start
- Check your version of macOS or Windows
- Check you have permission to run apps on your OS
- Check macOS Gatekeeper security settings to ensure that you are allowed to run apps from the App Store and Identified Developers.
- On Windows, you may need admin permissions to install the Hub depending on your security policy
To uninstall the Hub
- On macOS, trash the application from your Applications folder
- On Windows, use the Apps & Features page from Windows Settings to uninstall the Hub
- On Linux, use Software Manager to uninstall the Hub.
Known Issues with the hub
- Changing language requires a restart of the app
- You may experience slow download speeds as few Hubs will be online initially. We are adding additional web seeds to help speed up testing.
- MuseScore must be restarted to detect newly installed Muse Sounds and MuseFX
- Language translations are machine translated; there may be translation errors that need correction.
- Project files downloaded from the inspiration page have a machine-generated filename
Comments
I have uninstalled Muse Sounds and reinstalled it, I have uninstalled and reinstalled MuseScore. Nothing is working. The program is for some reason not acknowledging Muse Sounds. I go into playback setup, and all I see is MSBasic, and Muse Sounds greyed out with faint letters on it saying "inactive". I tried the mixer too, it isn't working. I do not know what else to do. I have installed everything from Muse Hub.
I've just been playing around with M4 and Muse Sounds these last couple of days, and this is just fantastic work! Still bugs, of course, but it sounds great and the app is (still) nice. :-) Fantastic work!
I have some thoughts on cymbals, though, and I'm not sure how to best report it. It's not really a bug, but more of a consistency thing. Should I then add it to github with other issues?
Basically, I'm thinking about naming of instruments involving cymbals, and which sound they correspond with from Muse Sounds. The musescore instrument "cymbal" adds "piatti" from muse sounds. Cymbal is singular, while "piatti" is plural, meaning they're two cymbals hit against each other (also called cymbals (plural)/a2 cymbals/clash cymbals/chrash cymbals/orchestral cymbals). There is no instrument that adds the suspended cymbal (singular, hit with mallet/stick), which is represented in Muse Sounds, as far as I can see.
My suggestion is to remove the instrument "cymbal", and then add "Suspended cymbal" and "Piatti" (or orchestral cymbals) in stead.
How do I adjust velocity of the dynamics? I can't access the option by going into the element properties like in MS3.
In reply to How do I adjust velocity of… by jlizhiyi
We are in the process of revamping velocity so it is represented in one place. At present velocity settings are on notes only, set to a default of 64.
After the initial launch, we will allow dynamic markings to affect the velocity settings on notes too. After that, we can create a visual lane where users can draw velocity settings themselves (and override dynamics as needed).
Unfortunately, we could not build all of this for V4.0. But we could also not persist with the older system, which is incompatible.
This all means that we will ultimately have a far better and faster system for controlling velocity that matches patterns found in other applications. This is a priority for us.
In reply to We are in the process of… by Tantacrul
Just today I was hoping we'd get user/offset velocity on chord symbols. Has that been considered?
I hope to have a first look at the beta within the next few weeks. Very excited to see the progress.
scorster
In reply to Just today I was hoping we'd… by scorster
Right now chord symbol playback is still a work in progress. You can track the status of the issues on GitHub. See for example https://github.com/musescore/MuseScore/issues/13327
Do you think we could expect a marching band version of Muse Sounds in the future?
In reply to Do you think we could expect… by bynumlandon01
An update for MDL has been teased about for more than a year, so likely a MuseSounds version of that will happen at some point in the future.
I have a question - when is the tentative date that the final version of MuseScore 4 might be released to the general public? Thank you so much!
In reply to I have a question - when is… by musicbetweenl
The answer remains unchanged: As soon as all blocking bugs have been resolved.
In reply to The answer remains unchanged… by jeetee
I Think The final release of Muse Score 4 is expected as early as the end of December this year. However, given the progress (such as bug fixes), it may be postponed to the first half of next year.
In reply to I Think The final release of… by chaejunsu0902
You may think what you like, the answer still remains unchanged :)
As soon as all blocking bugs have been resolved.
Congratulations on the beta release! It is happy to see Musescore evolving with a brand new outlook and features in the new version.
I have just tried updating the second alpha to the beta with Muse Hub. However, after some attempts to use the beta, the software crashed and I cannot open it anymore despite attempts of computer restarts, re-install from Muse Hub and re-install through the separate version of the software. I am using a Surface Pro 8 running Windows 11.
I also wonder about the playback of the repeat sign - I usually write drumset parts with the groove on the first bar and use the repeat sign in each subsequent bar. When I played one of my works on MuseScore 4 the groove stopped after the first (fully-written) bar. May I know if it is just for me or if I can change my configurations to play those bars with repeat signs?
Thanks so much!
In reply to Congratulations on the beta… by Felix T.
I have the same problem with bar repeat. Posted it 2 times without getting an answer
In reply to I have the same problem with… by roland bublitz
Not sure where you posted, but the issue is reported in GitHub and is already fixed in current nightly builds.
Is there any news on a potential time frame for the official MuseScore 4 release?
In reply to Is there any news on a… by RJohns21
Just, whenever it's ready. I'd guess more than week, less than three months. The thing that will help it go better is, more people helping test the beta release.
In reply to Just, whenever it's ready. … by Marc Sabatella
Thank you!
In reply to Just, whenever it's ready. … by Marc Sabatella
Where can I download the Beta versions?
I have the one you see in the attachment.
(OS: Mac Monterey)
Thank you
In reply to Where can I download the… by Claudio Riffero
That's the Beta
In reply to That's the Beta by Jojo-Schmitz
Latest version?
In reply to Latest version? by Claudio Riffero
Yes, as far as I can tell
There are later nightly builds though
In reply to Yes, as far as I can tell by Jojo-Schmitz
Grazie! Gentilissimo.
In reply to Just, whenever it's ready. … by Marc Sabatella
Do not hurry with official release ; if we waited so long for beta, we can spare few months more. It's better to release Beta 2, with some key bugs fixed, than repair alfa continuously as happened with Musescore 3, which was very unstable.
The key bug - as I see - with Beta 4 is that Muse sounds produce terrible echo, during playback and mp3 rendering, each orchestral score (I wrote about this elsewhere), take whatever file from Muse score.org library each produces sooner or later this effect with strings (Beethoven's 5th is classical example); why did this bug develop, I don't know. Even more terrible is "miau" echo using solo strings - take whatever string quartet form musescore.org library and you'll see how it sounds, just awful. Not to mention that dynamics is not precise (and articulation, tremolo, pizzicato etc.) or significantly lowered comparing to older versions: piano become pianissimo possibile. Why? Solo oboe, even if market forte, almost sounds pianissimo, similar solo violin, cello etc. Till this problem won't be fixed, there's no sense for official release or Beta 2. It's pity, because some sounds did improve very much. (If you try to combine new sounds with basic, there's problem with playback speed - older are faster, consequently cacophony.)
In reply to Do not hurry with official… by Chabrol
FWIW, there already was a beta 2 :-). The Muse Hub was updated a week or so ago. And also, there is a new nightly build every day. So lots of people are already testing the bug fixes. I encourage you to join this effort by testing nightly builds instead of the original beta!
As for any issues you are seeing - just be sure to report them on GitHub so the developers can investigate. There are a number of issues already reported regarding dynamics and also regarding the portamento of strings. many are already fixed in the nightly builds, others are improved, some are still being worked on. Not sure what you mean about echo though, unless you are referring to the reverb, which is normal. If you're hearing something other than normal reverb, definitely report that on GitHub with a sample score.
In reply to FWIW, there already was a… by Marc Sabatella
Hi, installed the beta about 1 month ago via Muse Hub (4.0.0.223072007): I understand there's a beta2 now: how can I get it via Muse Hub? Going in Updates it tell me that "All your apps and sounds are up to date".
Thanks
In reply to Hi, installed the beta about… by Valerio Folli
That version number is the one from beta2.
Congrats on the great progress! Super excited to try this out.
I'm rather flummoxed why for such a significant milestone, there is zero mention of this on the musescore.org homepage. I previously highlighted this issue when alpha 2 was released, which prompted a subthread of discussion, but apparently no concrete action. Please see in particular five options I suggested for solving this, repeated here:
IMHO any one of these five would be a substantial improvement on the status quo of well hidden announcements. I really think you guys are missing out here on a great low-hanging fruit opportunity to promote your amazing progress and get more beta testers involved!
Thanks again for all the incredible work!
Just took a look and this is fantastic! Just a couple key things of note:
![image_2022-11-17_165740598.png]( "image_2022-11-17_165740598.png")
-Right now tied notes do not work, it repeats the note. Also quick question, + is now bound do something else, what is the new shortcut to tie a note?
-Muse Basic sounds don't work...
-New vsts are amazing, but overall there are problems with playback, in general where things are inaccurately used.
-Even when setting the buffer size at max you still hear static. I also don't see an option to use any drivers like ASIO, the audio engine and I/O settings in general need a lot of work.
-Need more export settings, for instance quality of the wav file. You're competing with DAWs here and this is something people are going to be looking at if you want them to move from the DAW to musescore. Provided below is a screenshot of how Reaper's export feature looks for instance.
-If you can make keyswitches not be an absolute pain I will love you guys.
-new vsts sound great. absolutely love
In reply to Just took a look and this is… by mnmwert
The tied notes bug was fixed some time ago already. So, not in the beta, but in the nightly builds. Best to use those for further testing as quite a lot of other things are also improved.
Tie shortcut is "T". You can see (and customize) the shortcuts in Edit / Preferences / Shortcuts. Also, for commands like tie that have toolbar buttons, you can hover your mouse over the button to see its shortcut.
Not sure what you mean about basic sounds not working, certainly the default MS Basic soundfont works in general. If you have a specific score that shows a problem (certain instruments using non-default sounds might not work as expected), be sure to report that on GitHub.
In reply to Just took a look and this is… by mnmwert
Also just of note, after some more testing, some other things that needs improvements are the general playback of MuseSounds.
One thing I want to absolutely commend you on is that in terms of playback I cannot distinguish that this was a vst instead of a live performance, the playback of it was so good, it sounded better than even the professional VST strings software I have.
However right now the way it interprets playback, dynamics, etc. is still very buggy. It has difficulty with tremelo/pizzicatto especially. A lot of times one instrument would be at pianissimo and another at fortissimo when it was not indicated as being written that way.
In reply to Also just of note, after… by mnmwert
Note Muse Sounds is not a VST but something more sophisticated, which is how it is able to achieve such realism.
If you encounter specific problems using a current nightly build, again, please be sure to report them on GitHub as requested in the announcement above. You can check the existing issues there also to see if yours is known (a number of problems relating to dynamics are already reported).
In reply to Note Muse Sounds is not a… by Marc Sabatella
Ahhhhh that makes sense.
Anyway, I want to say I am absolutely blown away. I have never in my life heard something made by a computer sound this realistic... this is absolutely huge. it's scaring me to the point of me questioning whether or not as someone who is studying violin at university, if performers will even have jobs by the time I graduate XD
In reply to Just took a look and this is… by mnmwert
VST keyswitches are possible but a pain. Maybe not quite as bad as you're imagining, though. You can add a separate staff to the instrument and add your keyswitches there. Then mark the staff invisible when you're done.
In reply to VST keyswitches are possible… by Marc Sabatella
I think it would be really cool to have a setting in the instruments section itself, where the staff can actually be limited as to what shows up in the score. you could split the instrument into two sections, the midi range for the staff, and the midi range for the keyswitches. This way you can edit the entire range of midi notes specifically for the vst you are using.
After that all you need is to connect that to some kind of GUI view for the instrument and boom.
In reply to I think it would be really… by mnmwert
But then you'd need multiple voices - more of a pain than multiple staves. But you can do that if you prefer. I think eventually the plan is for a whole new system to simplify keyswitches, including making them automatic as you add articulations, etc.
In reply to But then you'd need multiple… by Marc Sabatella
you're totally right that would be even better!
Just keep in mind it would be good to be able to customize that per instrument because different vsts map keyswitches differently.
I'm trying to change the fermata time stretch like I used to do in M3 but I just can't find it in M4. Someone could help me with that? Thanks.
In reply to I'm trying to change the… by Toninho Zemuner
See the Properties panel (new name for Inspector), then the Playback section within that.
In reply to See the Properties panel … by Marc Sabatella
Thanks Mark, I didn't know that it was hidden under the playback section. Another question: the "+" key is no longer working for tieing two notes. Is there any changes for this shortcut in particular?
In reply to Thanks Mark, I didn't know… by Toninho Zemuner
Yes, it is now "T", as +/-/= are now sharp/flat/natural. Those are the only significant changes to shortcuts that I can think of.
In reply to Yes, it is now "T", as +/-/=… by Marc Sabatella
Yeah, I noticed that when I tried to tie a note with the "+". Thanks again.
In reply to Yes, it is now "T", as +/-/=… by Marc Sabatella
Strange, the letter T is not working.
In reply to Strange, the letter T is not… by Toninho Zemuner
Maybe try Help / Revert to Factory settings; your shortcuts may have gotten out of whack. if you continue to have trouble, please report this (and any other issue you encounter) on GitHub as per the original announcement. And be sure to include complete steps to reproduce the problem.
In reply to Maybe try Help / Revert to… by Marc Sabatella
Will do. Thanks.
Question / Concern: For MS4 nightly build of 11/18 -- the score properties dialog box (now named 'Project properties') seems to have fewer properties available to set than appear in the MS3 score properties dialogue. For me, there is one missing property that I depend on - the "workNumber" property.
I use it for version management and display it's value in my score's footers. For example: "Arrangement 1, Release 2."
I did hunt around to see if I could find, perhaps, some other place in the UI where maybe this setting got moved to, but couldn't find it anywhere.
Is it really the intent to remove some of the Score Properties?
In reply to Question / Concern: For MS4… by rocchio
I can't answer that definitely, but I can observe you add whatever you want using the "New property" button.
In reply to I can't answer that… by Marc Sabatella
Right, right, ok. I just now confirmed that I can add 'workNumber' as a custom property and that after doing so it will appear in my pre-defined footer.
I am getting 'Unable to download Musescore something went wrong, please try later' message and
2022-11-19 00:36:55.1210|ERROR|Muse.Service.Interop.ServiceCore|Error adding download: expected value (list, dict, int or string) in bencoded string [bdecode:4]
2022-11-19 00:36:55.1210|INFO|Muse.Service.Interop.ServiceCore|Error adding download: musescore: MuseScore
When I try to download MuseScore using Muse Hub
Any hints?
In reply to I am getting 'Unable to… by witor
Same!
(Don't mind what I named it.)
In reply to Same! by [DELETED] 54008466
I am having the same issue! It's giving me specific error ID's when I try to install any Musesounds as well.
I've done some more testing with the solo strings in the beta. I cannot speak for other instruments yet. But I was working with a string quartet I was writing and also downloading midi of some violin concertos to see how it performed. Here are some suggestions I have to consider.
Right now the biggest thing is that I do not have a lot of fine control over how MuseSounds interprets the notation when I should have. Preferably there should be GUI involved in this with settings you'd see in a regular vst. For instance, sometimes there will be times when the strings would play slightly out of tune as you might see occasionally in a real performance. However settings like that should be adjustable.
Other things that I've noticed:
-Musesounds struggles with finding balance between parts. It liked to prioritize the first violin as the loudest, while the lower parts I could barely hear at times. I feel like this is due to both buggy playback issues, but also it taking too much liberty with interpretations that really should be able to be finely controlled.
-Musesounds likes to make slurs even when things are notated as separate bowings. This should never be the case, it should only slur when a slur is distinctly notated.
-The audio engine struggles a lot, often times you hear artifacts and buzzing.
-Export currently messes up the audio quality
-There are a lot of times problems with the 'attack' of a note which makes it sound machinelike because the
-Musesounds cannot handle fast notes really at all, sometimes it will play it twice as slow, other times it doesn't play the rhythm accurately at all.
-On stringed instruments it plays chords incorrectly, four voice chords will always be 'rolled'. Three voice chords can either be rolled or played at the same time, but if played at the same time will have a hard attack.
-There are some parts where it sounds like the the violin sound is doubled. This tends to mix with the problems with the attack given on the violin which makes it gain a really weird robotic sound and it starts to sound more like a synth than a violin.
-Has a really big problem with any particularly large leaps.
-Still suffers from the robotic sound gained from playing notes at the same velocity (especially noticeable in the piano). This is generally fixed in professional software and DAWs by a 'humanization' feature.
Here is a video showcasing these issues:
https://streamable.com/m43ilz
I highly recommend comparing the playback of musesounds to a recording of a real person playing the piece:
https://www.youtube.com/watch?v=KDJ6Wbzgy3E
I'd submit this to the github... but I have no idea how to use github and also uh, this is more of an overview instead of narrowing down things to a singular issue. And I don't have the time to make like 50 individual forum posts.
In reply to I've done some more testing… by mnmwert
GitHub is just a website, if you know how to use a web browser, you know how to use GitHub. Click the link given, then click the "New issue" button and follow the prompts.
Please submit one issue per report. And when you do so, be sure to include sample scores, or at least precise steps to reproduce the problem from scratch.
If you're testing the beta instead of nightly builds. it's known that there is a permanent portamento effect on the solo strings; that's already mostly (but not completely) fixed in the nightly builds. The issue is still open, so it's already known there is still work to be done there - no need to submit that as an issue.
Regarding audio hiccups, try increasing your buffer size in Edit / Preferences / I/O.
And if time is limited, no need to submit issues for every quirk you notice - just focus on the most important. You might want to do a search first on GitHub first (again, it's just a website, you'll see a search box there, so you shouldn't have trouble using it) to see if something is already reported.
In reply to GitHub is just a website, if… by Marc Sabatella
Thanks! Where do I get the nightly build so my tests are accurate to where the development currently is?
Right now the buffer size is already set at max and it still gives the problem.
In reply to Thanks! Where do I get the… by mnmwert
Nightly builds are obtained from the Download / Software menu at top left of this site. THen scroll down to where it says "development" builds. Be sure to get the one that says "nightly" and "master", not the ones marked "3.x" or "beta".
In reply to Nightly builds are obtained… by Marc Sabatella
Thanks, I got it and started messing around. A lot of the issues I was talking about are still prevalent but somewhat less so. when I have time I will try to figure out how to report bugs.
btw how do I manage vsts? It's able to detect kontakt and opus/play and some spitfire plugins, but that's it, and I can't find how to add in all my other stuff.
In reply to Thanks, I got it and started… by mnmwert
Probably best to start a new thread in the Development forum with any really specific questions about how to use specific features - this thread here is really about the announcement itself and becomes hard to follow otherwise. When you do ask about VST's, be sure to mention what problem specifically you are trying to solve what you mean by "manage" them. Maybe, though, you just mean, it can only see VST3? That's true; VST2 is not compatible.
In reply to Probably best to start a new… by Marc Sabatella
Oh I see, that is probably what the issue is. Why is VST/VST2 non-compatible?
In reply to Oh I see, that is probably… by mnmwert
Totally different technology, and different license requirements that are not compatible with open source software like MuseScore. You can search this site for previous discussions.
In reply to Totally different technology… by Marc Sabatella
Unfortunately I can't exactly see a straight answer in regards to the different license requirements from previous discussions while searching. Are there any specific VST3 players that will play a VST2 instrument?
I mainly say this cause well, there's some great stuff like this plugin:
https://www.mattmontag.com/projects-page/nintendo-vst
that right now it doesn't seem I can load into musescore.
In reply to Unfortunately I can't… by mnmwert
I'm not sware of any, but this too seems like a great discussion to start in the Development forum.
In reply to I'm not sware of any, but… by Marc Sabatella
in the OP there was a link to an issue tracker, would you mind sending me the link to the development forum so I can make a post? thanks!
In reply to in the OP there was a link… by mnmwert
It’s right here alongside this very Announcements forum - so if you were able to find this, you should be able to find the Development forum the same way (eg, the Support link above). But just in case, the direct link is https://musescore.org/en/forum/687
In reply to It’s right here alongside… by Marc Sabatella
Thank you! I've posted two discussions there now, we'll see where things go :)
How do you reorder the parts in MS4? I have a score with 7 parts. The last part I created I now want to move to be the first part (so that upon PDF export it appears 1st in the consolidated pdf document). [The parts dialog in MS3 had buttons allowing you to reorder parts, cannot find anything similar in MS4 so far.]
I see that you can re-order Instruments, but not parts. Reordering the instruments affects the order they appear in in the "Main Score."
I have a few use-cases for this. One: I have an instrument with both an SMN staff and a TAB staff. I want to make a part that shows both staffs, then another part that shows only the SMN staff. It's a lovely thing that in MS4 I can actually do that. BUT now I cannot set the order in the exported PDF the parts will appear in. Bummer.
2nd Use Case: I like to make a cover page that has song background, maybe notes about the parts and such. I use Frames for this. Again, it is a wonderful thing that I can now, in MS4, create a new part and not add any staff to it, so that I can have this nice cover page. But, sadly, I cannot force that cover page part to be the first part that gets output to the consolidated PDF file.
But - maybe I'm missing something and all the above I just wrote is nonsense?? OR perhaps I should open an issue on github for this?
In reply to How do you reorder the parts… by rocchio
Generally, it's best to start new threads in the Development and Technology Preview forum for detailed discussion of specific features - otherwise this announcement thread quickly gets too overwhelming to follow.
Is it just me, or are woodwinds too loud? I tried remaking the first line of Brahms's 4th symphony in MS4 with Muse Sounds, but the woodwinds (albeit not the horn) dominate.
I would also like to note that trills and slurred fast notes get muddled up.
In reply to Is it just me, or are… by jlizhiyi
Balancing work is still ongoing. But FWIW, I don't notice this in general, especially in current nightly builds (as opposed to the original beta from a few weeks back).
In reply to Balancing work is still… by Marc Sabatella
The fast connected note issue appears in string parts, should've clarified.
In reply to The fast connected note… by jlizhiyi
I don't know about trills, but I don't think MuseScore plays slurred notes.
In reply to I don't know about trills,… by bobjp
I know for MS3 it only plays slurs/phrases for a certain set of instruments, which IIRC is piano and strings. IDK if Muse Sounds is any different.
But it's not that MS4 ignores the slurs. It does factor the slurs into the output, however the resultant sound is "warpy" rather than an authentic slur (as would be heard in MS3).
In reply to I know for MS3 it only plays… by jlizhiyi
MU3 didn't play slurs period. It "faked" slurs for piano and flute by artificially shortening other notes, but it didn't and couldn't create any true slurs.
The "warpy" sound you refer to, I assume, is a bug in the beta for solo strings only, and it has already been mostly fixed in the nightly builds (still some work left to do for a few sounds).
When I open more than one file in MS 4, it doesn't just open a new window; it re-opens the whole application. Among other things, this results in multiple MS 4 icons in my sidebar, and it just feels unnecessary to me. Is this (a) a bug that should be reported on GitHub, (b) something that is intentional, (c) something that has already been addressed, (d) something unique to beta that will not be in the full release, or (e) some other option I haven't thought of yet?
I'm running on Mac 12.6.1
In reply to When I open more than one… by chrismassa1
It is (b).
In reply to It is (b). by SteveBlower
Thanks. Why is this intentional? I've never worked with any other program that does this, and I'm curious.
In reply to When I open more than one… by chrismassa1
It is indeed b), but also known to not be ideal for people on macOS. Other systems combine the instances into a single icon so it's not really an issue, but this doesn't work on macOS apparently. And there are other drawbacks of this approach that I think the developers would like to be able to address. But so far, I don't think there is a good solution developed that would solve the other problems that the separate instance model was designed to solve (different playback profiles for different scores). At least, that's my understanding. So, 4.0 will almost certainly be as is, but there is some chance of change at some point in the future.
In reply to It is indeed b), but also… by Marc Sabatella
Yeah, it is kind of an annoyance for Mac users, and this didn't seem to be an issue in MS 3. But it's far from a dealbreaker.
In reply to Yeah, it is kind of an… by chrismassa1
It wasn't an issue in MU3 because you couldn't have separate playback profiles for different scores. Whatever soundfonts you had loaded for one score would apply to all others. This system mguht work in a work where you mostly just have a single soundfont, but it is completely incompatible with multiple VST's, Muse Sounds, etc.
Hey to all!
Congratulations on version 4 which takes MuseScore to a very high level.
I'm testing the MuseScore 4 on a laptop that has a NumPad. Trying to define shortcuts based on the use of NumPad I find that this is not possible. Also importing an older shortcuts map that I use in MuseScore 3, I again find that MuseScore 4 does not accept shortcuts related to NumPad usage. (When I try to enter shortcuts based on the NumPad digits it seems to ignore the difference between the main keyboard and the NumPad numeral digits.) Is there any related limitation? Is there something going on that I don't understand or have I missed?
Thank you for your time.
George
In reply to Hey to all! Congratulations… by George Hatzimi…
The NumPad issue is known, and hopefully being worked at
In reply to The NumPad issue is known,… by Jojo-Schmitz
Thank you very much!
In reply to The NumPad issue is known,… by Jojo-Schmitz
Hello again, and thank you for your time!
Meanwhile the update to 4.0.1 has already been released. I downloaded it.
I am reeding: "Major fix for numpad shortcuts" . I tried it. Still can't get the numpad to cooperate in creating shortcuts. It still confuses the main keypad numbers with the numpad numbers. Am I wrong?
In reply to Hello again, and thank you… by George Hatzimi…
You may need to revert the factory settings, at least the shortcuts
In reply to You may need to revert the… by Jojo-Schmitz
Thank you again!
Well, it was probably a reboot related issue.
The numeric keypad works. BUT: its shortcuts are still confused with those of the main keyboard, e.g. if I set the numpad "/ " symbol for the accent, then the main keyboard "/ " symbol follows. So I can't set different shortcuts, one for the "/ " of the main keyboard, and another for the "/ " of the numpad.
In reply to Thank you again! Well, it… by George Hatzimi…
That indeed is the case, as far as I can tell, changing shortcuts (stil) doesn't fully work, not via the UI at least. But you can edit the shortcuts.xml directly
In reply to That indeed is the case, as… by Jojo-Schmitz
Thank you very much about the idea for shortcuts.xml ... I will try it!
In reply to Thank you again! Well, it… by George Hatzimi…
/ num pad = / main keyboard: Well if that is by design I find that a good design.
I wouldn't want to have to remember that / on numpad is not same as main keyboard, and especially I wouldn't want to be unable to use my / shortcut when my external keyboard is not connected and I just don't have a numpad at all.
In reply to Hello again, and thank you… by George Hatzimi…
The main fix is to make them work at all, which they weren't for some people :-). At least, not without needing a custom XML file. But yes, I do believe it's true that if you want to reassign them to do something different from the default, and you want to be able to use the numpad and standard keys to do different things, that still requires custom XML.
In reply to The main fix is to make them… by Marc Sabatella
Thank you very much! I tried it. It works!
Musescore 4 on macOS seems to lack jack integration. Is that on purpose?
Are you planing on adding other means of synchronizations to DAW? (like MTC?)
I also would like to know your plans on native apple silicon builds - it seems you're still running on Qt5 which probably makes this harder. (But it seems there is support on 5.15 for native arm builds https://doc.qt.io/qt-5.15/macos.html#architectures) Is it planed to migrate to Qt6 at some point in the future?
P.S.: Sorry for posting that again I accentily posted it under some older article regarding MS4
In reply to Musescore 4 on macOS seems… by hpfmn
AFAIK it lacks Jack on any platform.
Yes, there is a plan to move to Qt6 somewhere in the 4.x chain of releases.
I've been using the beta musescore for the last few weeks with no issues. However, after I restarted my computer today, I'm now unable to open the app, as it keeps crashing on startup.
Does anyone know how to fix this? I've already tried deleting and reinstalling both Musehub and Musescore 4.
In reply to I've been using the beta… by Atimony12
Likewise, for both 4.0.0. and MuseScore 4.0.0.223360501 Nightly. Musescore 3.0 still opens.
system=MacOS 13.0.1, Intel MacBookPro 15-inch 2017
In reply to I've been using the beta… by Atimony12
I reported this on github with some additional comments, and got this reply "This has indeed to do with an update to MuseSampler / Muse Sounds. Very soon, we will release a Release Candidate of MuseScore, that is able to work with the updated sampler, so that it doesn't crash."
In reply to I reported this on github… by macgarvin
Thanks for the help. I agree that it has something to do with Muse Sounds. I dug around some of the Muse Hub files and when I manually removed the Muse Sounds files (except for strings), I was able to open the app.
In reply to I've been using the beta… by Atimony12
Working again for me with last night's Musescore build (for macOS)
https://ftp.osuosl.org/pub/musescore-nightlies/macos/4x/nightly/MuseSco…
Once again, congratulations to everyone on this amazing beta MS4 release and a lot of thanks to the MuseScore developers team, as well as to the supporters on this forum! MuseScore is a big part of my life now.
I've got an issue in MS4, which may not be a bug or an issue worthy of being reported on GitHub, so I am just posting it here. I have downloaded MS4 and all the sounds (Brass, Choir, Percussions, Strings, Keys, Harp, Woodwinds) from Muse Hub and have been happily using them for some time while also trying out the nightly builds every now and then. Recently, however, I have noticed that after checking out one of the latest nightly builds (I am not sure which one exactly it was and if it's really the cause of the problem) the check icons on the Muse Hub home page reverted back to "Get" icons - as if I never downloaded the sound packs at all. Does that mean that I somehow lost them on my computer? Does it mean that I have to download them all again? (I am a little bit afraid to do that as they take up quite a bit of space on my disk.) How can I check manually whether I still have them on my computer? The settings section of Muse Hub is telling me that the sounds install location can be found at this path: "C:\ProgramData\MuseHub\Downloads", but when I open the C disk on my computer I can't find there a directory named as "ProgramData". Instead, I have there a directory named "Program Files" (that's where "MuseScore 3" and "MuseScore 4" folders are) and another one named "Program Files (x86)", which doesn't contain anything related to MuseScore.
I just noticed that bendings (in guitar notation for example) are not played back. Is that intended?
In reply to I just noticed that bendings… by hpfmn
We'll be tackling guitar playback in one of our next releases. We have some significant plans there, which were too big to include in this release. Give us a little time... and there'll also be a new Muse Guitars pack coming out with it.
I've just listened to a score that uses these features (Muse Sounds mostly) and I was blown away! I literally can not put into words how amazing this stuff is!
In Musescore 3, I was able to edit dynamics and crescendos/decrescendos in the inspector (especially helpful for niente dynamics). However, Musescore 4's equivalent of the Inspector doesn't show any option to edit them when they are selected. Is this feature removed or not fully implemented yet? If it is there, is it in a different place?
In reply to In Musescore 3, I was able… by jfmusicaddict
The new plan is to have all control of volume be connected to the notes themselves. So right now, you use velocity, but there are designs being worked on to provide a "volume lane" similar to some DAW's in a future update.
Hi! I downloaded, i love it. But the other day I couldn't open the app. I tried every way...
I've been thrilled with Musescore for quite a while and am anxious to install this new version with all it's capabilities and possibilities. Before I do, I'd appreciate a detailed explanation of what the helper app does. What system resources would I be allowing access to? What sort of tracking is going on, and do I have any control over how data collected from me is used? Thank you so much, and kudos on what appears to be a phenomenal piece of work!
In reply to I've been thrilled with… by rmeike
Hi rmeike. In case you weren't aware: You commented on the announcement of the beta release of MuseScore 4. The final version was released days ago.
The helper app, which is called "MuseHub", has a website: https://www.musehub.com I would suggest having a look at the website. If questions remain you can visit the forums at https://musescore.org/en/forum, search them for related posts and post questions of your own there.