Can not be used in MuseScore 3, while it works in MuseScore 2

• Jan 8, 2019 - 12:58
Reported version
3.0
Type
Functional
Frequency
Many
Severity
S2 - Critical
Reproducibility
Always
Status
closed
Regression
No
Workaround
No
Project
Tags

After activating TempoChanges in the MuseScore 3 Plugin Manager, TempoChanges still doesn't show up under "Plugins", while other plugins do.
In MuseScore 2 everything works fine.


Comments

I went into the plugin creator and the error is it cant find version 1.0 on my system. I altered this to 2.0 and to last know version and then 3.0 and I got the app to work and show in my list of plugins but it does work. Error report is as follows:

Running…
Plugin Details:
Menu Path: Plugins.TempoChanges
Version: 2.3.1
Description: Creates linear hidden tempo markers.
See also: https://musescore.org/en/handbook/tempo-0#ritardando-accelerando
Requires Score
Debug: Applying to selection [41040, 44160] = 3120
Debug: 2.2 (132) -> 1.5 (90) = -0.7000000000000002
54:-1: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function
54:-1: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function
54:-1: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function
54:-1: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function
54:-1: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function
54:-1: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function
54:-1: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function
Warning: :54: TypeError: Property 'startCmd' of object Ms::MasterScore(0x269c72a7010) is not a function

The best you can expect from running any plugin in version 3 at the moment is error messages. Keep an eye open for plugins to be fixed in the not to distant future.