Installing MuseScore 4.4 Makes a Mess of Plugins
Virtually all of the plugins do not show up correctly in 4.4. Instead of showing the names of each plugin, the dropdown list reads "Run plugin ()". Selecting that does nothing. When in the Manage plugins... window, virtually all of the plugin names do not display even after clicking Reload plugins.
| Attachment | Size |
|---|---|
| Screenshot 2024-08-31 at 2.29.00 PM.png | 269.85 KB |
| Screenshot 2024-08-31 at 2.29.52 PM.png | 560.86 KB |
Comments
I have the same problem
In reply to I have the same problem by Dimaxl
so do I
This is due to some technical change in MU4.4(*). Most plugin are not compatible any more. Every plugin developer will need to update their plugin, which could take a some time to be finalized, Or never be done, if the plugin developer doesn't want to spend time on this. Solution: stay to MU3.6.2-3.7 or MU4.3.2.
See this post, for some more detailed explanation.
(*) migration to Qt6.2
In reply to This is due to some… by parkingb
Migration to Qt 6.2
In reply to Migration to Qt 6.2 by Jojo-Schmitz
Corrected!
In reply to Migration to Qt 6.2 by Jojo-Schmitz
Thank you for the response! Is migrating a plugin into Qt 6.2 something I as a user can do or can that only be done by the developer?
In reply to Thank you for the response!… by davidtauler@gm…
Depends...
In reply to Depends... by Jojo-Schmitz
The plugins I depend on daily are: ChordLevelSelector.qml, fix-to-line.qml, movesBreakstoParts.qml (a.k.a. Export layout breaks to parts), ReplaceChordSyms_0.qml.
Do you happen to know if any of these are plugins I can migrate into QT 6.2?
In reply to The plugins I depend on… by davidtauler@gm…
There isn't a real step-by-step migration guide. However some users already collected some information.
I stumbled on this one:
https://musescore.org/en/node/367488
You can try to migrate these plugins by yourself.
If these plugin are managed on github and you are familiar with github, you can fork the repository and work from there.
As there is no Plugin Editor in MU4.x, you'll have to work with some external editor, locate the log files and check any error which is reported there to move forward on the migration.
The question you also would have to answer is what kind of retro-compatibility do you want to maintain: 4.4 solely, 4.0-4.4, 3.6.2/3.7+4.0-4.4. This will impact how you migrate the code.
In reply to There isn't a real step-by… by parkingb
Thank you for this!
In reply to This is due to some… by parkingb
I think this may be why images no longer drag properly since upgrading to the latest version. Can you (or someone else on this thread) please share information on returning to MU4.3.2. Thank you!
In reply to I think this may be why… by Cynthia Cathcart
Uninstall 4.4.0, download and install 4.3.2
In reply to Uninstall 4.4.0, download… by Jojo-Schmitz
Thank you. Do I need to do anything specific to save my template settings, or will those files survive the new install?
Also, please, I looked but all I could find for 4.3.2 was a git-hub error spreadsheet. Is there a link you can share for the install files?
In reply to Thank you. Do I need to do… by Cynthia Cathcart
Are you looking for : https://musescore.org/en/download#older-versions ?
From there you can go to https://github.com/musescore/MuseScore/releases/tag/v4.3.2.
I think you clicked on the link under the release 4.3.2 header, but you have to click on the header itself.
HTH,
Luc.
Workaround: Install MU3.7 Evolution that reads MU3 & MU4 files (and run the plugin in MU3.7)
Instructions here: https://github.com/Jojo-Schmitz/MuseScore/wiki/
In reply to Workaround: Install MU3.7… by elsewhere
MU3.7 reads now MU4 files ??? This is something new ?
In reply to MU3.7 reads now MU4 files ??… by parkingb
No, that is not new at all
In reply to No, that is not new at all by Jojo-Schmitz
Oh I see. When it says "Cannot read the file...", actually it can read it. I never moved beyond that message, and never clicked on "Ignore" :-D
In reply to Oh I see. When it says … by parkingb
;-), yes, I never 'fixed' that dialog
Ditto here but i have some of the plugins that were specifically for Version 4 and these dont work either.
With reference to screenshot 1. I had this initially. To get rid of the run comments on the list I simply closed Musescore and went into the plugins folder and cut out all the plugins i had there. I then opened Musescore and of course nothing was there. I pressed rescan plugins and quit the application.
I then pasted the plugins back into the plugin folder and reopened Musescore and could see the names of the plugins again. However, when I click on the preinstalled plugins I get a black screen if i am lucky! otherwise nothing opens up.
I don't want to regress back to the last version b3ecause there was an error in it that made the application crash if you wanted to drag a slur into the right place. As soon as you did that the application closed down.
The version prior to the mix up worked like it should do no issues with the plugins.
I just wished that the developers behind musescore told every one that all plugins now musr conform to X Y Z version 8.6. They could even update the plugin repository!
Thats my take on this matter. I just hope that who ever wrote the original plugin updates it. There is no compulsion for the original authors of those plugins to update them. Perhaps a kick and a nudge in the right direction might elicit a response from the original author if the developers were to say to all the users that created the plugin to upgrade to whatever version it is and keep on maintaining plugins that ere in the repository. If they dont comply delete the plugin from the repository. Some of those plugins are now defunct as the software now does what the original author intended to do so they are obsolete. In this case the email that goes out the authors should be something like this:
1 The author is dead. The authors estate relinquishes all rights to that plugin and leaves it to someone who is capable of upgrading the plugin to the most recent version.
2 The author hasn't used their software since the date of the great flood and doesn't have an active Pro account. Delete or open the plugin up to someone else to fix it.
4 I have updated my plugin to version XYZ and tested it and it works
5 I have not updated my plugin because it is no longer needed as the software has been updated and the plugin is now obsolete. Please delete from the Plugin Repository.
6 I don't know how to upgrade to version xyz. Help!
7 I have updated my plugin to version XYZ and tested it and it works but now I wish to charge for the use of that plugin up to a max of £2/$2/€2..... I did put the work into it and as Musescore is now more like a DAW i should be recompensed for my time the same way as Steinberg does for it creators of new content using their proprietary software and coding.
Just some ideas here that might help keep the repository cleaned up and any old iron thrown out.
To go back to the question though yes I have the same issue even with the preinstalled plugins that come with Musescore 4.4