Cannot read property 'STAFF_TEXT' of undefined error when using TempoChanges
The TempoChanges plugin doesn't seem to work anymore for me. I am using Musescore 3.0.5
Here is the log from the Plugin Creator:
En cours…
Détails du Plugin :
Chemin du menu : Plugins.TempoChanges
Version : 3.0.1
Description: Creates linear hidden tempo markers.
See also: https://musescore.org/en/handbook/3/tempo#ritardando-accelerando
Nécessite une partition
Debug: Applying to selection [18240, 19200] = 960
Debug: 1.7333333333333334 (104) -> 0.9333333333333333 (56) = -0.8
Warning: QMetaProperty::read: Unable to handle unregistered datatype 'Ms::PluginAPI::Enum*' for property 'Ms::PluginAPI::PluginAPI_QML_167::Element'
57:-1: TypeError: Cannot read property 'STAFF_TEXT' of undefined
57:-1: TypeError: Cannot read property 'STAFF_TEXT' of undefined
Warning: :57: TypeError: Cannot read property 'STAFF_TEXT' of undefined
Comments
Thanks for reporting, I'll have a closer look during the coming week
Can you please add some more detailed information about your MuseScore version?
I'm on "Windows 10 (10.0), Arch.: x86_64, MuseScore version (64-bit): 3.0.5.5992, revision: 58dd23d" (use the copy button from Help → About)
and there the error doesn't occur.
It is triggered by the code
var startText = newElement(Element.STAFF_TEXT);as if the Element isn't exposed as expected by MuseScore, which makes me believe you have a differently built/packaged version of MuseScore.As per https://musescore.org/en/node/284012#comment-895137 an AppImage on Manjaro Linux
In AppImage for 3.0.5 version this plugin works correctly for me.
OS: Debian GNU/Linux 9 (stretch), Arch.: x86_64, MuseScore version (64-bit): 3.0.5., revision: 58dd23d
More info on the used MuseScore version would be useful indeed. Does this bug appear in AppImage or in some version packaged in other way?
In reply to In AppImage for 3.0.5… by dmitrio95
Hi, I'm still using Musescore on Manjaro Linux but this time it's version 3.0.5 from the repositories. Specifically it's Revision 3543170 from the community repository : https://www.archlinux.org/packages/community/x86_64/musescore/
Also, here is the output from when I run Musescore from the command line:
[brett@brett-HP ~]$ musescore
[1464:1478:0506/193955.515569:ERROR:adm_helpers.cc(73)] Failed to query stereo recording.
libpng error: Read Error
qml: Applying to selection [18240, 19200] = 960
qml: 2 (120) -> 1 (60) = -1
QMetaProperty::read: Unable to handle unregistered datatype 'Ms::PluginAPI::Enum*' for property 'TempoChanges_QMLTYPE_74::Element'
file:///home/brett/Documents/MuseScore3/Plugins/MuseScore_TempoChanges-3.0.1/TempoChanges.qml:57: TypeError: Cannot read property 'STAFF_TEXT' of undefined
QMutex: destroying locked mutex
QObject::disconnect: No such slot Ms::MyWebView::stopBusy(bool)
I'm afraid something went not exactly right when that package was built by the maintainer.
That revision number specifically comes straight from the 2013 version of https://github.com/musescore/MuseScore/blob/master/mscore/revision.h indicating that at least the "make revision" build step was not executed by the package maintainer.
Try to get in touch with him, point them here and let's see if an update to the package (or packaging process) is required.
That revision number issue is a very common mistake, in many Linux versions. But here it seems not to be the only mistake?
Aha, that makes sense. I'll try sending an email to the maintaner. In the meantime I'll use the Appimage. Thanks everyone for your help!