![]() ![]() ![]() If it does lots of things then you're going to run into a problem when some of those things change a lot while others don't change very much. Strict semantic versioning only makes sense if your app/library does one thing. If you write scores for guitar and parts then you would consider 4.2 a "major" upgrade, but if you don't write scores for those things then you would see the changes in 4.2 as incremental, so it wouldn't make sense for us to bump the major version. It might help with expectation, but we have to balance the expectation for compatibility with the expectation for new features. Thanks!Ī) Bumping the major version wouldn't help with compatibility (you would still be unable to open scores in the older version). Reminder for plugin authors: if your plugin uses the TextField component from QtQuick.Controls 1.0, please replace it with the TextEdit component from QtQuick.Controls 2.15 (or from QtQuick.Controls 2.2 if you require compatibility with MuseScore 3). Finessing this feature is likely to be an ongoing process over the next couple of releases, but we’d appreciate your feedback and input!.Playback support for microtonal accidentals has now made it into MuseScore 4.2!.Option to publish to and at the same time.Various MusicXML fixes and improvements.Support for Music Encoding Initiative (MEI) format.Ability to choose specific sounds within a SoundFont.6-key Braille input via the Braille panel.Options to place ties ‘inside’ or ‘outside’ of notes and chords.Support for glissando playback with correct enharmonics. ![]() Ability to exclude certain elements from the score or the parts.Better synchronisation between the score and the parts.Bend playback currently requires SoundFont or VST.All-new system for inputting bends and customising their playback.Here’s a reminder of the new features in 4.2: Guitar As always, please check first that the issue hasn’t already been raised, and ideally try to reproduce it in the latest nightly build before reporting. If you find any issues, please report them on GitHub. Also, if you save any score files with 4.2 then you will not be able to open them with previous versions of MuseScore 4. You can install it alongside your current version of MuseScore 4, but please be aware that the two versions will share preferences and workspaces. Once the beta is installed, it will show up on your machine as “MuseScore 4 Testing”. As promised, we have a beta build ready for MuseScore 4.2, which you can download from our release page over on GitHub: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |