Chopin Mazurka: Add @sameas clefs where a clef affects multiple layers#18
Chopin Mazurka: Add @sameas clefs where a clef affects multiple layers#18th-we wants to merge 1 commit into
Conversation
|
I wonder if this is an appropriate use of To illustrate, would you also consider doing: and then just using I don't have the answer, but I think it should be resolved, or at least discussed, before accepting this into the sample encodings. |
|
I definitely agree that this needs discussion. So you are saying that |
|
If we agree that the attributes should be repeated, then this should also be done in Ives' "The Cage", where the double-stemmed notes are encoded like: |
|
For the record, see the discussion here rism-digital/verovio#400 |
|
@th-we if you could resolve the conflicts, I'd be happy to merge this. |

I think in multi-layer situations it should be best practice to encode a
<clef>in all affected layers, using@sameasto refer to a "primary" clef. This avoids having to calculate timestamps for all layers to find out what clef is active.When used consequently, it can also be recognized when a clef is actually meant to apply to a specific single layer only, like in cross staff situations and in the well known oddity from Debussy's "La Danse de Puck":