Plugins are no longer working in MU4.4 ?

• Sep 1, 2024 - 10:38

Hi, What's going on with the new MU4.4 with the plugins ?
The menu doesn't show the plugin names:
Mu44_plugin.png
Many plugin's don't run any more:
MU44_Plugin KO.png
And in the Plugin management, the thumbnails are not shown any longer:
MU44_Plugin Mgmt.png

Comments

• Sep 1, 2024 - 10:40

It's explained here (https://musescore.org/en/node/365783), I quote:

Qt 6

MuseScore Studio 4.4. will be the first release using Qt 6, the latest version of the cross-platform framework that powers MuseScore's UI on Windows, macOS and Linux. Qt 6 brings a host of improvements, including better support for scrolling and touch gestures. It also unlocks the potential for native Apple Silicon builds, and we're hoping to have these builds ready in time for the 4.4 release.

The current plan is to release with Qt 6.2.4, which maintains compatibility with Ubuntu 20.04 (Focal Fossa), macOS 10.14 (Mojave), as well as Windows 10. Fonts are handled slightly differently in this version and we're currently working to ensure that score and UI text looks as close as possible to how it did in MuseScore Studio 4.3, which uses Qt 5.15. If you encounter other differences while testing, please let us know.

Important: Plugins must be updated to work with Qt 6 otherwise they won't appear in the Home screen or Plugins menu in MuseScore Studio 4.4. Plugin developers, please see issue https://github.com/musescore/MuseScore/issues/21659 for details, and these commits (https://github.com/musescore/MuseScore/commits/7fe32bacbc9287b716d40462…) for the required changes.

Reply

• Sep 13, 2024 - 20:40

Who in the world thought releasing MuseScore Studio 4.4 with a crippled major plug-in system was a good idea? The release notes said that plugins might need updating. The note did not suggest that "Plugins must be updated to work with Qt 6 otherwise they won't appear in the Home screen or Plugins menu in MuseScore Studio 4.4". That information would have saved me hours trying to figure out what went wrong.
I understand you have to wrestle with a complex mix of operating systems, UI's, and volunteer work on the plugins. And I know from personal experience that new releases can be nerve racking and that the pressure to release can be intense.
I don't know your organization climate. I hope it's not a place where people are afraid to stand up and say "don't release a crippled package". Someone should have.

Reply

• Sep 13, 2024 - 20:59

Plugin are built by volunteers (mostly) not affiliated with the Musescore dev team.

Most of the developers just discover the impact of a new release on their plugin when the release is out. They are not involved in early tests, e.g.. There is no documentation provided to tell them, these are the impact of the upcoming release, please check and update your plugins. Nope.

Since the takeover by the Muse company (which is an editor of scores) the focus of the development goes mostly/only on engraving and audio rendering. who are two outputs provided by the Musescore.com website. The plugin, while fundamental for most users, don't come in their line.
The composers (opposed to copy-writer) and the workflows to get nice score are completely left over.

Unfortunately, you can't shout too loud without risking to be banned from the tribune.

Alternatively, as a end-user, you choose to remain on older versions. MU3.6.2 or MU3.7. And having the plugin keep on running.

Reply

• Oct 8, 2024 - 22:26

Especially at a time when a bunch of people are needing to jump ship and want to hop over here: not taking plugins into consideration at the development communication level, and simply not having working plugins available does not improve the chances that people will take the platform seriously.

Reply

Do you still have an unanswered question? Please log in first to post your question.