Same thing happens to me. If qml file is in plugin directory then Musescore will close the instant I click on "Plugin Manager". I'm using Musescore 2.0.2 on linux (Lubuntu).
This would be an amazing plugin if only I could get it to work!
version: "1.2";
description: "- Identify chords and put chord symbol on top.\n" +
"- Works with single or multiple voices, accross one or more staves.\n" +
"- Inversions are mentionned.\n" +
"- Notes are colored according to their function in the chord (NCTs stay in black)\n" +
"- Shows only chords used in classical music: triads (major, minor, diminished) and seventh chords (MM7, m7, Mm7, dim7)\n\n" +
"Comments, feedbacks, report bugs, ask for new features, contribute:\n" +
"https://musescore.org/en/project/chordidentifier";
menuPath: "Plugins.Chords." + qsTr("Chord Identifier")
Hi Griddy,
Thank you for your analysis! I don't really understand what caused the problem... maybe the "qsTr()" function?
Anyway, I modified the plugin accordingly, you can download the modified version here: https://github.com/rousselmanu/msc_plugins/archive/v1.2.1.zip
Hi rousselmanu,
I am also getting the crash on opening the plugin manager with both version 1.2 and 1.21. I am running Musescore 2.0.3 on Windows 10.
As I am new to this, I am not sure if there are any logs, or any way to debug the plugin. Let me know if there is any other information that I can provide.
Maybe, if I'll have some spare time, I could push the fix myself to the repo.
By the way, it doesn't recognise anything if there is no third in a triad. Is it supposed to do so (it doesn't recognise "power chords" like D5 or Dsus2/sus4)?
Maybe, if I'll have some spare time, I could push the fix myself to the repo.
By the way, it doesn't recognise anything if there is no third in a triad. Is it supposed to do so (it doesn't recognise "power chords" like D5 or Dsus2/sus4)?
Hi, sorry for the late answer, I'm not the developer.
Anyway you just need to:
1. Open the addChord.qml file with a text editor (Notepad, Notepad++, ...)
2. Add the string "import QtQuick 2.0" right after "import MuseScore 1.0" (EDIT: in a new line, of course)
3. Save and open Musescore.
When using MuseScore 2.1.0 on OS/X, I also encountered this crash (using the 1.2.1 zip above), and found that adding the "import QtQuick 2.0" statement to the file fixed the problem.
Could the original author therefore please apply this update in the repository, and make sure that the MuseScore.com plugins page (https://musescore.org/plugins) page actually refers to it?
Now that I've got it working, it works great!
(Incidentally, the crash occurred, on startup, when I had enabled the "chordidentifier" plugin, although the patch had to be applied to "addChord" as noted. Don't ask me why.
Hi,
Thank you all for your diagnosis of the bug and for the fix!
I just made the change in the repository and the plugin page. Sorry for the time I took... :-p
I hope it is working fine for you now.
The latest Zip does not appear to contain the "import QtQuick 2.0" statement, and therefore, on OS/X, caused an immediate crash upon selection of "Plugin Manager." Therefore, for me at least, it did not fix the problem.
When I manually inserted the "import" statement, it appeared to work.
Also, when I selected only the bottom note of a chord but not the entire thing, the plug-in not only labeled the chord (Cm), but also labeled an adjacent rest as "B-flat minor / C-sharp." When I selected all the notes of the chord, it labeled the one chord correctly and added no detritus after it.
H-O-W-E-V-E-R: when I exited MuseScore and tried to restart it, it failed on startup with this message:
---
2017-06-26 12:47:06.466 mscore[2710:123582] 12:47:06.466 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
Init midi driver failed
QQmlPropertyCache: QQuickItem has FastProperty class info, but has not installed property accessors
Abort trap: 6
---
Focusing, then, on the last bit, I'm not sure that the "add an import statement" advice really is a correct and complete solution to the problem in the first place.
---
I notice that your "GitHub" repository contains the source-line modification aforementioned but the zip does not. Nevertheless, it appears that this is not actually quite enough, as aforementioned.
Thank you @Jojo-Schmitz.
In fact I think that the import statement should be "import QtQuick 2.3", which I was doing in the 1st version of the plugin
, but caused problems for some users.
I removed it, because on my computer it is working even without the statement, but this caused problems mentionned in this thread.
The suggestion to import QtQuick 2.0 seems to work for most of you, but it appears really difficult to build a plugin working on all possible versions and platforms... Maybe a developper of Musescore could tell us the good way to go ? Because there is no real doc for plugin development as far as I know.
So I suggest to first make sure you have the latest version of musescore and the latest version of the plugin
. If still not working, try "import QtQuick 2.3". You can also delete the addChord.qml which is not used by the main plugin, only a demo for automatically adding chords. More than that I don't know...
Disappointingly, the latest version (1.2.2) doesn't appear to do anything at all. Musescore 2.1.0 on OS/X just as before, but when I select notes and press the chosen key-sequence, nothing happens. Even on a dummy score where I've written C-major. It doesn't crash on startup, but it doesn't work either.
(This is the exact same unchanged environment that I've used in all posts to this issue.)
Comments
Unless you plan to provide a fix, you'd better unassign yourself
Hi Evan,
Could you try the last version available here:
https://github.com/rousselmanu/msc_plugins/archive/v1.2.zip
I also added download links on the project webpage because some people got confused and downloaded the html webpage instead of the plugin.
If it still doesn't work, please provide more info on your config.
Same thing happens to me. If qml file is in plugin directory then Musescore will close the instant I click on "Plugin Manager". I'm using Musescore 2.0.2 on linux (Lubuntu).
This would be an amazing plugin if only I could get it to work!
I edited the qml file a little and it works now.
The problem is the first lines of the menu:
version: "1.2";
description: "- Identify chords and put chord symbol on top.\n" +
"- Works with single or multiple voices, accross one or more staves.\n" +
"- Inversions are mentionned.\n" +
"- Notes are colored according to their function in the chord (NCTs stay in black)\n" +
"- Shows only chords used in classical music: triads (major, minor, diminished) and seventh chords (MM7, m7, Mm7, dim7)\n\n" +
"Comments, feedbacks, report bugs, ask for new features, contribute:\n" +
"https://musescore.org/en/project/chordidentifier";
menuPath: "Plugins.Chords." + qsTr("Chord Identifier")
I just simplified it to:
MuseScore {
menuPath: "Plugins.Chords."
description: "- Identify chords and put chord symbol on top."
version: "1.2"
And now it seems to work
Hi Griddy,
Thank you for your analysis! I don't really understand what caused the problem... maybe the "qsTr()" function?
Anyway, I modified the plugin accordingly, you can download the modified version here: https://github.com/rousselmanu/msc_plugins/archive/v1.2.1.zip
Hi rousselmanu,
Sorry for the late reply.
The modified version still isn't working for me :/
I'm running Musescore 2.0.3 on OS 10.12.2 Sierra.
2.5GHz Intel Core i7
Let me know if there's any more info I can give to help, I'll get back quicker this time, lol.
I appreciate everyone trying to make this work!
Thanks!
Evan
Automatically closed -- issue fixed for 2 weeks with no activity.
Hi rousselmanu,
I am also getting the crash on opening the plugin manager with both version 1.2 and 1.21. I am running Musescore 2.0.3 on Windows 10.
As I am new to this, I am not sure if there are any logs, or any way to debug the plugin. Let me know if there is any other information that I can provide.
Hi, I got the same crash too, Windows 10, but I found a fix.
I started some debugging and I found this error: QQuickItem has FastProperty class info, but has not installed property accessors
A quick search on StackOverflow brought me here: http://stackoverflow.com/questions/30824350/qqmlpropertycache-qquickite… . I added the "import QtQuick 2.0" to the lib and now the demo works.
Maybe, if I'll have some spare time, I could push the fix myself to the repo.
By the way, it doesn't recognise anything if there is no third in a triad. Is it supposed to do so (it doesn't recognise "power chords" like D5 or Dsus2/sus4)?
Hi, I got the same crash too, Windows 10, but I found a fix.
I started some debugging and I found this error: QQuickItem has FastProperty class info, but has not installed property accessors
A quick search on StackOverflow brought me here: http://stackoverflow.com/questions/30824350/qqmlpropertycache-qquickite… . I added the "import QtQuick 2.0" to the lib and now the demo works.
Maybe, if I'll have some spare time, I could push the fix myself to the repo.
By the way, it doesn't recognise anything if there is no third in a triad. Is it supposed to do so (it doesn't recognise "power chords" like D5 or Dsus2/sus4)?
(are comments moderated?)
Yep, that got it. Thanks for sharing your fix.
Crashing with version 1.2.1 and MuseScore 2.0.3.1. on a Mac. Crashes as soon as I click Plugin Manager.
Crashing on Musecore 2.0.3 on Windows 7. the.real.berga95 said they found a fix, but I didn't understand what the fix was.
Hi, sorry for the late answer, I'm not the developer.
Anyway you just need to:
1. Open the addChord.qml file with a text editor (Notepad, Notepad++, ...)
2. Add the string "import QtQuick 2.0" right after "import MuseScore 1.0" (EDIT: in a new line, of course)
3. Save and open Musescore.
Let me know if this worked for you, too! Bye!
When using MuseScore 2.1.0 on OS/X, I also encountered this crash (using the 1.2.1 zip above), and found that adding the "import QtQuick 2.0" statement to the file fixed the problem.
Could the original author therefore please apply this update in the repository, and make sure that the MuseScore.com plugins page (https://musescore.org/plugins) page actually refers to it?
Now that I've got it working, it works great!
(Incidentally, the crash occurred, on startup, when I had enabled the "chordidentifier" plugin, although the patch had to be applied to "addChord" as noted. Don't ask me why.
Hi,
Thank you all for your diagnosis of the bug and for the fix!
I just made the change in the repository and the plugin page. Sorry for the time I took... :-p
I hope it is working fine for you now.
It works for me now. Many thanks to everyone.
You're welcome. Thanks to the dev for pushing the fix! :)
The latest Zip does not appear to contain the "import QtQuick 2.0" statement, and therefore, on OS/X, caused an immediate crash upon selection of "Plugin Manager." Therefore, for me at least, it did not fix the problem.
When I manually inserted the "import" statement, it appeared to work.
Also, when I selected only the bottom note of a chord but not the entire thing, the plug-in not only labeled the chord (Cm), but also labeled an adjacent rest as "B-flat minor / C-sharp." When I selected all the notes of the chord, it labeled the one chord correctly and added no detritus after it.
H-O-W-E-V-E-R: when I exited MuseScore and tried to restart it, it failed on startup with this message:
---
2017-06-26 12:47:06.466 mscore[2710:123582] 12:47:06.466 WARNING: 140: This application, or a library it uses, is using the deprecated Carbon Component Manager for hosting Audio Units. Support for this will be removed in a future release. Also, this makes the host incompatible with version 3 audio units. Please transition to the API's in AudioComponent.h.
Init midi driver failed
QQmlPropertyCache: QQuickItem has FastProperty class info, but has not installed property accessors
Abort trap: 6
---
Focusing, then, on the last bit, I'm not sure that the "add an import statement" advice really is a correct and complete solution to the problem in the first place.
---
I notice that your "GitHub" repository contains the source-line modification aforementioned but the zip does not. Nevertheless, it appears that this is not actually quite enough, as aforementioned.
Not sure what you are looking at, but the zip file linked to at https://musescore.org/en/project/chordidentifier does contain that statement
Thank you @Jojo-Schmitz.
In fact I think that the import statement should be "import QtQuick 2.3", which I was doing in the 1st version of the plugin , but caused problems for some users.
I removed it, because on my computer it is working even without the statement, but this caused problems mentionned in this thread.
The suggestion to import QtQuick 2.0 seems to work for most of you, but it appears really difficult to build a plugin working on all possible versions and platforms... Maybe a developper of Musescore could tell us the good way to go ? Because there is no real doc for plugin development as far as I know.
So I suggest to first make sure you have the latest version of musescore and the latest version of the plugin . If still not working, try "import QtQuick 2.3". You can also delete the addChord.qml which is not used by the main plugin, only a demo for automatically adding chords. More than that I don't know...
Automatically closed -- issue fixed for 2 weeks with no activity.
Disappointingly, the latest version (1.2.2) doesn't appear to do anything at all. Musescore 2.1.0 on OS/X just as before, but when I select notes and press the chosen key-sequence, nothing happens. Even on a dummy score where I've written C-major. It doesn't crash on startup, but it doesn't work either.
(This is the exact same unchanged environment that I've used in all posts to this issue.)