Run Plugin Tin Whistle Tabulatore and MuseScore crashes
Hello,
have problems with the Tin Whistle Tabulatore.
https://musescore.org/en/project/tin-whistle-tablature
-The Plugin is activated in musescore.
-The TTF-Font "Tin Whistle Tab" is installed, i can see it under "windows - system - personalization - fonts". -Under c-windows-fonts-"Tin Wistle TAB" -properties -security: The Font has access for all application packages "read and read and execute" like other TT fonts.
-I have actual Windows 11 Home, language in german.
-MuseScore 4.
-I choose the plugin "for musescore 3.4 and later"
Problem:
I load the Musescore File "Tin Wistle Test" its comming along the plugin in MuseScore.
I take "edit select all" or some notes or select no notes.
And then run the Plugin under "Plugins".
Musescore crashes instant and shows the error message for a very short time:
"No selected staff in the current score uses a tin whistle instrument. Use menu command edit -> instruments to select your instrument"
But this is not true, becouse the Thin-Whistle ist choosen.
the question relates to the functioning of said plugin.
I would also like to point out that when Musescore4 crashes, the error message appears so briefly that it is unreadable, but this should be known.
Thanks
Comments
It crashes because of the use of Qt.quit in the plugin.
The solution is to replace it with quit.
But this is not the only problem with the Tin Wistle plugin.
=> there is also a problem identifying the instrument
instrument = curScore.parts[staff].instrumentId
does not seem to work anymore.
anyone has an idea?
In reply to It crashes because of the… by graffesmusic
"The solution is to replace Qt.quit with quit."
Can u explain what to do?
In reply to "The solution is to replace … by Urban Reed
Use a normal text editor on the qml file and make the above mentioned modification
In reply to Use a normal text editor on… by Jojo-Schmitz
Casper fixed the plugin.
https://github.com/jgadsden/tin-whistle-tablature/pulls
While the author reviews this, here a working plugin for MS4
The main problem is:
"MuseScore 3 returned the MusicXML instrument ID, MuseScore 4 returns its own instrument ID. This change might be reverted in MuseScore 4.0.1, but we will just make sure we recognize MuseScore's own instrument IDs too."