Automatic Boomwhacker color - 2nd volta
Just watching the last "Mastering MS" Youtube video...Seems like we have been telepathically communicating, @Marc Sabatella, have been implementing the exact same things as you these past days.
I think there is one remarkable omission: automatic boomwhacker colored noteheads. And NOT as a plugin which I have to invoke every time I add notes, but just as solfege notes automatically change when I move a note. I mean, in my side of the pond, Boomwhacker coloring is quite more used that 7-shape Aikin... ;)
Shouldn't be too hard to implement, should it?
Comments
So a duplicate of https://musescore.org/en/node/303999
As said there it should be possible to modify that plugin to automatically update the colors.
I'm just not sure how that works, I guess @dmitrio95 would know though
In reply to So a duplicate of https:/… by Jojo-Schmitz
Basically. I feel I didn't get a satisfactory response as to why this feature which is so incredibly useful for pedagogy with small children isn't implemented. Neither whether there were any plans to implement it. It seems it should be no biggie, as other types of noteheads adapt immediately to note changes.
In reply to Basically. I feel I didn't… by urisala
In the past 10+ years that need never came up, as far as I remember, beyond what the color notes plugin provides already.
And as mention, with some modification of that plugin it won't even require any additional code inside MuseScore itself anymore
In reply to In the past 10+ years that… by Jojo-Schmitz
How often the need has come up shouldn't be the only criteria. So you really don't think that would be incredibly useful? Then I am going to go out on a limb and assume you don't teach at primary school.
Maybe some people haven't even heard of boomwhackers, or the possibility of changing noteheads. But once this is implemented, they will understand what they have been missing.
Using the plugin is a major pain, especially when you are using chord, adding notes to make chord out of several notes, etc. One ends up with some notes with color, some without, some with wrong color.
Really...
In reply to How often the need has come… by urisala
Indeed, I'm not a music teacher at a primary school, the the time my kids were at primary school is long ago (mine even more so ;-)), although I'm pretty sure they haven't used boomwhackers color coding there.
No pain, if that plugin does the updates for you, which it should be able to do nowadays
Won't do anything to the pinao keyboard though, something you brought up in that other thread
In reply to Indeed, I'm not a music… by Jojo-Schmitz
"Indeed, I'm not a music teacher at a primary school, the the time my kids were at primary school is long ago (mine even more so ;-)), although I'm pretty sure they haven't used boomwhackers color coding there."
There were no boomwhackers or color coding either when I was a kid. Neither were music teachers going around with laptops loaded with notation software, DAWs, etc. But luckily things are improving. Let's keep at it. Using boomwhacker notation + Song Maker is making composers out of little children!
And REALLY hoping for a color coded piano too, down the line! ;)
In reply to How often the need has come… by urisala
Try and read the response again.
The plugin can be adjusted to work "live" instead of when you manually call it. That adjustment is expected to be a smaller effort than extending native musescore support. On top of it, once the plugin is adjusted, you can use it right away; if it becomes a native feature, you'd have to wait for a future release (as it won't make the 3.5 inclusion list anymore at this point in time).
In reply to Try and read the response… by jeetee
How? Note names and color notes would be good candidates for taking advantag of this and even for inclusion in 3.5
In reply to How? by Jojo-Schmitz
Yes, how? Any chance of a screencasting of you doing that?
In reply to Try and read the response… by jeetee
Ah, (as per @dmitrio95) the
onScoreStateChangedhandler and the not yet merged PR https://github.com/musescore/MuseScore/pull/5657In reply to Ah, (as per @dmitrio95) the… by Jojo-Schmitz
And THERE is where the conversation turns to Chinese for me ;)
In reply to And THERE is where the… by urisala
Would it help if we'd add some colors?
SCNR...
Basically we're not quite there yet, some building blocks are still missing
In reply to Would it help if we'd add… by Jojo-Schmitz
Hahaaa ;)
In reply to Would it help if we'd add… by Jojo-Schmitz
If you could add some glitter animation too, and a Mr. Dinkles mew sound effect every time a notes changes, that would be awesome, my kids would love it.
Seriously though, do I take it that maybe the feature might come in the not too distant future?
In reply to If you could add some… by urisala
That's the hope, yes
In reply to That's the hope, yes by Jojo-Schmitz
Great!
In reply to How often the need has come… by urisala
Glad you're finding some of my resources useful!
FWIW, while the question of how often the need comes up isn't the only criterion for choosing which features to implement, it certainly is a hugely important one. Every week spent implementing a new feature is a week that could have been spent implementing a different feature, or fixing bugs, etc. Also, it is important to consider how much time a given feature actually saves. A feature requested by, say, 1000 users sounds like a higher priority than one requested by only 200, sure. But if the feature requested by the 1000 saves each of them 5-10 seconds of time per day, but the feature requested by the 200 saves each of them 5-10 minutes per day, suddenly the latter starts to sound higher priority.
So yes, prioritization is a complex and subjective thing. FWIW, my sense is that saving the need to re-run the plugin manually is on that order of saving 5-10 seconds per day, but maybe I'm misunderstanding something? To me, it seems that simply getting that plugin to update automatically - which appears like it might be possible soon - largely solves the problem?
In reply to Glad you're finding some of… by Marc Sabatella
The infrastructure is in place, the note names plugin now exists in an interactive version, so now it is 'just' needed to create an interactive version of the color notes plugin.
In reply to The infrastructure is in… by Jojo-Schmitz
I see maybe some issues with a plugin based solution. AFAIK the plugin acts on the selected notes. If the plugin is made to act automatically on each note change, how will it know which staff I want colored and which not..
In reply to I see maybe some issues with… by urisala
The dynamic noenames plugin allows to select which staves to act upon
In reply to Glad you're finding some of… by Marc Sabatella
I would add another category: features not a lot of people conceptualized as possible, and therefore didn't ask for, but when added proved to open a whole new realm of possibilities.
I think there is a lot of potential for MS in school education, but the workflow has to be agilized, otherwise I lose my audience. Losing 10 seconds to color notes is exactly that. And sometimes it is many more seconds.
I am using more and more MS as a sort of musical powerpoint, and many of the feature I request are things that, I know, are not things that most composers need in their daily work. But maybe that is the thing, if features were added which allowed a sorts of "presenter mode", a lot more teachers would be using MS. I am in a lot of Facebook music e-teaching groups, people are constantly asking each other for software recommendation. Man, if I could edit my score, and just hit Presentation mode—change the workspace and suddenly the staff is size 9, everything I want hidden is hidden, staffs I want are colorized— I think teachers would flock to MS.
In reply to I would add another category… by urisala
As long as MS means MuseScore and not Multiple Sklerosis...
Not meant to be funny, MS is a well known acronym for a serious health issue and as such better not used for MuseScore
In reply to I would add another category… by urisala
You may be right that a presentation mode would make it even more attractive. But teachers already do flock to MuseScore. For all the obvious reasons - there's nothing even remotely comparable out there that is available for free. I mean, there is Noteflight and flat.io and they are popular as well, but kind of different in purpose and use. But definitely, continue to make suggestions for further improvement!
Elsewhere I mentioned that I'm not so sure it makes sense for the various "show invisible" commands to be score settings. I am not sure how viable it is to change that at this point, but they could at least be made part of what gets saved/loaded with the style, and in a template. That could in some ways be better than requiring a separate "presentation mode", because now those settings would just be there in the score and in all future scores created from the template.
But I could totally see "presentation mode" being a thing, not just as a workspace, but a "view" like we have page, continuous, and single page views. Or sit alongside the existing "full screen" facility. When in this view, we could automatically close the palettes, inspector, toolbars, and even the menu, and automatically suppress show invisible etc.
In reply to In the past 10+ years that… by Jojo-Schmitz
"And as mention, with some modification of that plugin it won't even requite any additional code inside MuseScore itself anymore"
Hopefully whoever wrote the plugin will do that, if it is so easy. I can't even begin to wrap my head around tinkering with plugins.