Craig Stuart Sapp

Ideally there would be some way of overriding the default behavior with some sort of overlay attribute that would force the same pitch in different layers to share a notehead...

> Well, that is a completely different case, that should be encoded with sameas I guess. No, it is the same case, except that chords are being used. In this...

That sounds good. It would be useful to avoid backwards compatible problems by using different values in `@sig.showchange`. But it would be very verbose to include both `@sig.showchange` and `@sig.changestyle`...

Another though: `@sig.showchange` is a bit confusing: the key *change* is always shown, rather it is the cancellation naturals placement that is being controlled. Better would be `@sig.showcancellation`, or since...

> Should we have another option to place the cancellation before the bar line? Related to this, it would be useful to have something like `keySig@cautionary` or `keySig@caution` to control...

I don't know if it would be useful to include `@dur.recip` all of the time, but adding an option, either in verovio or embedded in the Humdrum data, would be...

Also, if I add `@dur.recip` parameters, the definition of it should be updated in the MEI schema: ``` [0-9]+(%[0-9]+)?\.*q? ``` The `(%[0-9]+)?` is a `**recip` extension that I added 10...

> I think it would be good to have them always present when converting. As `multiRest` needs no `@dur` it would not make too much sense to generate a `@dur.recip`,...

Another considertation for the definition of `dur.recip` would be to include the tie information: ``` [[]?[0-9]+(%[0-9]+)?\.*q{0,2}[]_]? ``` This encodes the tie states of notes: | symbol | meaning | |---|...

OK. That sounds good.