-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Porting to Mu4 #11
Comments
This is great. When I test it in MS3, I will post it. Will see about the others...Thank you! |
in Mu4 IIRC dockable plugins are not (yet) possible in Mu4 |
I remember hearing from Marc Sabatella that even with the 'typical' Mu4 edits the plugins no longer function, or at least, they don't affect how playback sounds |
I have downloaded and installed MS4.1, ran it, and placed your articulate.qml in its Plugins directory, but I can't find the way to make it aware of the plugin. ReloadPlugins doesn't do it. What do I have to do?
Thanks....
…________________________________
From: Joachim Schmitz ***@***.***>
Sent: Monday, June 26, 2023 11:33 AM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
in Mu4 Qt.quit(); crashes Mu on load of the plugin. In Mu3 it is harmfool to, it stops thwe QML engoine and with that all running plugins. iIn Mu4 a plain quit();does the trick, in M3 that doesn't exists, so gives a warning in the plugin editor, but that should be harmless
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZNGDPFD3XWRGKZMDQ3XNGTUNANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
'Reload plugins' doesn't do anything at the moment, have you tried restarting the program? |
Just tried that. Certainly works (plugin appears where it should), but clicking on it in the plugins menu (after selecting a measure or note) crashes the app immediately.
Guess it's not ready yet.
…________________________________
From: XiaoMigros ***@***.***>
Sent: Friday, July 14, 2023 2:38 PM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
'Reload plugins' doesn't do anything at the moment, have you tried restarting the program?
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZP6OV4OJRDDD3PG533XQGGZXANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I can't immediately see a reason why, but I think it's worth noting that this plugin would not be functional (the play events system isnt present in MuseScore 4 yet) |
Uh, this is the version Jojo posted to this thread because he said that it IS functional! Do read it! Can you and he come up with one story?
Do you duplicate my result, or his? The only reason I downloaded MS4 was to check this claim.
If the Play Event system really isn't present in MS4, I don't see how the claim that this worked could possibly be true.
…________________________________
From: XiaoMigros ***@***.***>
Sent: Friday, July 14, 2023 3:33 PM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
I can't immediately see a reason why, but I think it's worth noting that this plugin would not be functional (the play events system isnt present in MuseScore 4 yet)
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZNYUHKB2ENTRJKAEXLXQGNHBANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I'm currently and for the next 2 weeks away for my computer... |
For me, it's not even showing up at all in the plugin manager tab |
Great. I'll uninstall MS4. Not ready yet. Don't know what Jojo was thinking.,
…________________________________
From: XiaoMigros ***@***.***>
Sent: Friday, July 14, 2023 4:00 PM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
[image]<https://user-images.githubusercontent.com/116587995/253670074-6ec83b1e-98f8-4308-9c10-32ea99659528.png>
Here are marc's notes on the play events system, for what it's worth (I haven't tested anything myself)
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZNOKTHYECSJAUEDE3DXQGQMJANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Interesting it shows up for you, it still doesn't for me.. Regardless, as Marc said,even though the properties exist and there are no errors encountered when writing them, no changes are made to playback |
It showed up for me after I restarted the app. But, as I said (this is in 4.1), as soon as I tried to apply it to notes, the app crashed, i.e.. it did not show the dialog.
Does it indeed actually work (change in notes and sound), or not (for you)? Have you changed it since the earlier version you posted?
…________________________________
From: Joachim Schmitz ***@***.***>
Sent: Monday, July 31, 2023 5:22 AM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
For me, it's not even showing up at all in the plugin manager tab
It does for me:
[image]<https://user-images.githubusercontent.com/1786669/257175724-fcc31658-b426-4ffc-b221-4f4437bcbf66.png>
[image]<https://user-images.githubusercontent.com/1786669/257176010-3cc18fed-6533-41d4-897c-6e92b9612976.png>
[image]<https://user-images.githubusercontent.com/1786669/257176116-f9e112cc-611e-4ced-8203-4cc2a50d26e2.png>
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZN75T2YF44OVERW3OLXS52LRANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I don't think it actually changed the sound, but it works and apparently changes the score in some form or shape. Haven't investigated in to what the changes are exactly. And no, I've not modified the plugin further, it is the one from the initial post. |
Then I cannot understand why it sort-of-works for you and crashes for me. The 4.1 I installed was out of the box and not customized in any way. I do not have MuseSounds. Obviously, I can't post it if it doesn't work for me.
…________________________________
From: Joachim Schmitz ***@***.***>
Sent: Monday, July 31, 2023 8:06 AM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
I don't think it actually changed the sound, but it works and apparently changes the score in some form or shape. Haven't investigated in to what the changes are exactly. And no, I've not modified the plugin further, it is the one from the initial post.
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZPALKZDKVGPPTQ3IKTXS6NT5ANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Anything helpful in the logs? |
Where do I find them? (I am running the Mac build, which may have something to do with the failures, too. What OS are you using?)
…________________________________
From: Joachim Schmitz ***@***.***>
Sent: Monday, July 31, 2023 8:46 AM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
Anything helpful in the logs?
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZN3GD2HR4VJ7TCAGA3XS6SK7ANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
I'm on Windows. The logs should be in |
Thanks, will try.
…________________________________
From: Joachim Schmitz ***@***.***>
Sent: Monday, July 31, 2023 9:25 AM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
I'm on Windows. The logs should be in ~/Library/Application\ Support/MuseScore/MuseScore4/logs on a Mac
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZIWLCR74EWXBUF72TTXS6W5JANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Using 4.1.1, just installed, I selected a note, tried to invoke the plugin from the men and the app crashed immediately. The log is enclosed and tells me nothing, given tht it worked for you.
I feel no urge to debug this given that the app is buggy and I don't need MS4.
…________________________________
From: Joachim Schmitz ***@***.***>
Sent: Monday, July 31, 2023 9:25 AM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
I'm on Windows. The logs should be in ~/Library/Application\ Support/MuseScore/MuseScore4/logs on a Mac
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZIWLCR74EWXBUF72TTXS6W5JANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
There no log... BTW: the plugin itself really works, it adds (something like) this to the score (to a
It is just nothing there in Mu4 to interprete that, I guess |
How can I get the log to you? Here are its last lines...
2023-07-31T16:38:02.929 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: play
2023-07-31T16:38:15.213 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: play
2023-07-31T16:38:23.601 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: articulate
2023-07-31T16:38:23.602 | WARN | main_thread | QmlPlugin | setMenuPath: Not supported!! Use:title
Somebody developing the app on the Mac has to find out what's happening. I don't want to be he,
…________________________________
From: Joachim Schmitz ***@***.***>
Sent: Tuesday, August 1, 2023 8:41 AM
To: BernardGreenberg/MuseScorePlugins ***@***.***>
Cc: Bernard Greenberg ***@***.***>; Comment ***@***.***>
Subject: Re: [BernardGreenberg/MuseScorePlugins] Porting to Mu4 (Issue #11)
There no log...
BTW: the plugin uitseld really works, it adds (something like) this to the score (to a note actually:
<Events>
<Event>
<len>111</len>
</Event>
</Events>
It is just nothing there in Mu4 to interprete that, I guess
—
Reply to this email directly, view it on GitHub<#11 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AMYBOZKUKZEDENCDLQZZWPTXTD2N5ANCNFSM6AAAAAAZUICUG4>.
You are receiving this because you commented.Message ID: ***@***.***>
|
Probably indeed someone needs to look at it in a Debugger |
Here's a port of one of these plugin to Mu4: articulate.zip
Verified to work, see https://musescore.org/en/node/351541#comment-1195813 ff.
It should work for Mu3 too, and the diff might serve as a template to port the others
The text was updated successfully, but these errors were encountered: