custom definitions for ornaments and articulations (et al)

• Apr 19, 2015 - 09:58

Is there any sort of feature already in musescore which could allow the user to enter reference data, or templates. For example, the user should be able to use the GUI to create measures with names which are not part of the score if played from the beginning, but which the programmer can access at the C++ level.

I'm wondering for the purpose of ornaments and articulations. If I want to somehow allow the user to define what a certain ornament means, he needs to be able to enter the data somewhere. Or would I have to create a completely new interface for this?

What I had in mind was, that if such reference measures could be created, the user could then use the inspector to put an indication on a note, play-as="MyMeasure123".

Another idea might be to have a staff as part of the system which is marked in the mixer as don't play, and usually marked as dont-display. The first time a note with a particular ornament appears, a play-as property could be on the note indicating play as staff X. The next time the same note with the same articulation appears, it would play as it did previously unless there is a new play-as property.

This is sort of already possible using multiple voices and changing visibility. But it is extremely awkward, and forces the user to define the same articulation every time it appears in the score.

I don't want to try to invent something very elaborate if there is already something in existence which can already be used.


Comments

In reply to by jim.newton.562

Jim, there's no single discussion I could cite - but you could enter
layers tags
into the Search for help box.

https://musescore.org/en/search/site/layers%20tags

Click on 'Filter'; under 'Filter by content type', you should find categorized links to places where what was proposed was mentioned (and, briefly, implemented in the Nightlies). These are the ones I would check out:

Forum topic (11)
Issue (5)
Book 2 (2)
Book page (1)

Of course, I'm just a curious and enthusiastic end user. Only developers could explain why the idea was set aside (at least until a later release) and if it actually has any relevance to the original point of this thread other than in my own imagination!

Do you still have an unanswered question? Please log in first to post your question.