I wish I could...Can I?
Dear Musescore users.
(Sorry if this is an old topic or: it's already possible).
When entering a score with piano and song (voice), I normally start with the "piano-part".
When finished I do the voice.
I then find that it would be nice to copy the "right hand" piano-part directly to the voice-part,
but only the single, highest note, of the (often) chords in the piano part.
(The red notes in the attached file) .
This is, I find, in many cases very "close" to the "voice part".
Is this possible today with a plugin or some "feature" I did not find:
To remove all but upper note of a chord?
Thanks in advance for an answer!
Erling
(And...Allow me a separate question:
Is there a "system" in the Musescore developer-group
where plugins are considered to be so "valuable"
that they might be "added" as a new feature in the software?)
| Attachment | Size |
|---|---|
| Example.jpg | 22.12 KB |
Comments
Maybe you could exploit explode https://musescore.org/en/handbook/tools#explode
First Press I, select the first Staff and add another one (or two others).
In reply to Maybe you could exploit… by Shoichi
Hi and thanks for quick answer. Works, but...affects the chords also in the piano part (The whole measure), not only the single staff. What am I missing? It should only affect the staff "in question", not "spread any notes to other staffs.
In reply to Hi and thanks for quick… by ErlingI
You're gonna have to take several steps...
For example, add another indstrument (e.g. Voice) and two staves (as mentioned above);
Copy and paste the Piano into the Voice;
Explode Voice;
Press I again to delete unnecessary staves (from the I dialog box you can move them up/down).
In reply to You're gonna have to take… by Shoichi
Again, thank you for very detailed (and quick and good!) answer. Highly appreciated.
Still, your explanation makes my question still valid, I think:
Why not simply have a function "similar" to explode: Simply remove all, but the highest note, in a selected range of notes/chords.
In reply to Again, thank you for very… by ErlingI
I think it's a question already asked, but I couldn't find it (yet).
eg.: https://musescore.org/en/node/302802
In reply to I think it's a question… by Shoichi
Again, thanks for the answer. It is very nice to receive this kind of quick and friendly feedback!
Makes me glad in these troublesome times!
Thanks again! (And perhaps you find the question already asked?!)
In reply to Again, thanks for the answer… by ErlingI
Just the one linked above.
But if you want you could use https://musescore.org/en/project/issues/musescore to make the request official. Perhaps it's better to wait a little while to receive some more authoritative comments here.
In reply to Just the one linked above… by Shoichi
OK, I will wait!
Hi, see https://musescore.org/en/handbook/tools#explode
In reply to Hi, see https://musescore… by Raymond Wicquart
Hi and thanks! See my thread with @shoichi. I can simply copy what I say there to your kind and quick answer!
I seem to remember that this plugin should be able to do what you want (haven't tested it myself though): https://musescore.org/en/project/prunestack
In reply to I seem to remember that this… by jeetee
Thanks jeetee for the report. Now question 2 would remain ;-)
Is there a "system" in the Musescore developer-group where plugins are considered to be so "valuable"
In reply to Thanks jeetee for the report… by Shoichi
Not really. It's more of a general function improvement vs use case effort and maintainability.
Take for example my own TempoChanges plugin; which provides automation for and existing workaround of a missing feature. I'd expect at some point in the future this functionality (being "valuable" enough) will make it into the main program; at which point I'll discontinue the plugin.
Plugins distributed with the software itself are more (outdated) tech demo documentations of the plugin framework possibilities for plugin developers.