Problem with ChordIdentifier in Musescore 3.05
Reported version
3.0
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
by design
Regression
No
Workaround
No
I have tried but seems to not work in Musescore 3.05 . I put in the Plugin folder but when clic on the
Plugin Tab nothing happens (the Chordidentifier is in the Plugin Manager but does not appear in the window
Comments
Did you enable that plugin in Plugin Manager?
In reply to Did you enable that plugin… by Jojo-Schmitz
Yes I tried putting chordIdentifier.qml in C/ProgrFiles/Musescore3/Plugins and also tried putting it in
C/Documents/Musescore3/Plugins.Then I open Musescore 3.05 >Plugins>Plugin Manager and I see the "Chordidentifier" and check the small square box before the name then clic OK. but when I reopen "Plugins"
I see nothing .....(see attached screenshot with step 1 and step 2)
PS I'm working on win 7 and the installed version of Musescore 3.05 is 32 bit
Tried that 2nd entry in the plugin manager?
That one probably is https://musescore.org/en/project/chord-identifier-special-v3
Also try to open and run it in the plugin editor, this may show an error message telling us what went wrong.
In reply to Tried that 2nd entry in.tge… by Jojo-Schmitz
Dear Jojo-Schmitz,
The 2nd entry you see on the screenshot is "chord-identifier-sp3" which I have downloaded and added after the "ChordIdentifier" ... and that seems to work (even if I took half an hour to find that it was "hidden" in
the lower left corner of musescore). Regarding the "ChordIdentifier" I attach another image after loading it
in the Plugin Creator and Running . The 1st error is : Line 21>Musescore version 1.0 not installed !!!
i thought these plugins were cheched before uploading: how can it work if it is asking for MS 1.0 ?
...and I'm afraid it is not the only bug...
Anyway I will use "chord-identifier-sp3" for now since it is the only available for Musescore 3
Thanks
Then is is not the version for MuseScore 3, but the one for MuseScore 2.
In reply to Dear Jojo-Schmitz, The 2nd… by Luciano Rizzi
Did you read the bold text on the page of SP3? :
"Close the left side palette (F9 to toggle) before running the plug-in
Otherwise, the plug-in dialog will remain on the bottom and you may not see it."
In reply to Then is is not the version… by Jojo-Schmitz
Dear Jojo-Schmitz
indeed , I have moved it on the Plugins Folder for Musescore 2.1 and seems to work !!
Therefore I will use it with this version , but please it shall be removed from the list of Plugins for Version 3
Thanks
In reply to Then is is not the version… by Jojo-Schmitz
Dear Demircan ,
Sorry I did not read that note !! (... and it was well bolded !) : it shall be putted also on the "Readme.txt"
and in any case I think it shall be a separate tab because to read all we have to close the palette and then
slide to the right all the score....
Now everything is clear regarding the "chordIdentifier-sp3" and how to use it .
Incidentally I have tested on some scores and find that many times on the same staff it gives me 2 chord names
(one below the other) and one of which is correct while the other is wrong....
Can you please check
Thanks a lot
That Line 21>Musescore version 1.0 not installed error cannot stem from this version of the plugin, as taken from https://musescore.org/en/project/chord-identifier-musescore-3-port, as that very clearly has the statement
import MuseScore 3.0in line 21, so you got to have loaded the 2.x version from https://musescore.org/en/project/chord-identifier-musescore-23 insteadTha fact that it works in 2.1 proves the point... (BTW: you really should be upgrading to 2.3.1)
In reply to (No subject) by Jojo-Schmitz
Jojo-Schmitz ,
You are right , it was a right mess ! I started reading from Musescore 3 plugins page but then switched
to the documentation page and went on Github and downloaded from there the wrong version , instead to download the "Attachment" on the 1st Page.....
Thanks for help , I will now put order on these files
Best Regards
In reply to Jojo-Schmitz , You are right… by Luciano Rizzi
@Luciano Rizzi;
Please re-download the SP3 (now:SP3_2) version and please test it.
Plug-in was revised and many corrections were made.