Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifying the use of staffDef vs clef #11

Open
lpugin opened this issue Jun 6, 2016 · 0 comments
Open

Clarifying the use of staffDef vs clef #11

lpugin opened this issue Jun 6, 2016 · 0 comments

Comments

@lpugin
Copy link
Member

lpugin commented Jun 6, 2016

Currently the musicxml2mei stylesheet generates clef elements for clef changes occurring within a measure and staffDef for the ones occurring at the end of a measure. I would suggest to make it consistent, and this should also be a recommendation for the guidelines. My proposal would be to use clef for all clef changes that occur within the flow of the music, be in within or at the end of a measure (when a clef change at the end of a measure appears before the end of a measure it does not make sense to make it a staffDef after the measure).

staffDef / scoreDef should be used in other cases (including changes with keySig or meterSig). A staffDef / scoreDef with a clef change is still possible and will still make sense but in such a case the clef will be expected to be displayed at the beginning of the next measure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant