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

Mensural Time Signatures #125

Open
ahankinson opened this issue May 30, 2024 · 4 comments
Open

Mensural Time Signatures #125

ahankinson opened this issue May 30, 2024 · 4 comments
Labels
Type: Spec Clarification Clarifications to existing content in the spec

Comments

@ahankinson
Copy link
Contributor

ahankinson commented May 30, 2024

The only mensural time signatures that are "unique" to mensural notation is the o (including o. and o/, o./). All other time signature values can be shared between them.

The proposal is related to #73 but altered to allow for flexible encoding of things like these images:

music-encoding/music-encoding#504 (comment)

Which is to say that only the o values are not allowed in CMN; every other possible combination of numbers and letters, eg., c/, c3, c3/2 etc. would be allowed.

@ahankinson ahankinson added the Type: Spec Clarification Clarifications to existing content in the spec label May 30, 2024
@BaMikusi
Copy link
Collaborator

BaMikusi commented Jun 3, 2024

@ahankinson Sorry, I read this thrice, but it's still beyond me -- perhaps some typos therein?

@lpugin
Copy link
Contributor

lpugin commented Jun 3, 2024

A quick estimate shows that we have about 500 non mensural incipits using o sign. We can evaluate if it makes sense to change them to mensural, but I am not sure we will be able to do so for all of them - if any.

This means we probably want to allow o in CMN but have the specs saying it SHOULD NOT be used.

@BaMikusi
Copy link
Collaborator

BaMikusi commented Jun 3, 2024

OK, that makes more sense (the present situation and the wished-for future appeared somehow conflated here, to my mind resulting in seeming contradictions).

I shall ask Carlo for a list of the CWMN o cases -- perhaps there is a pattern behind the phenomenon (with respect to libraries, or even catalogers) that could allow for a relatively easy fix.

@ahankinson
Copy link
Contributor Author

Sorry -- I was trying to write the issue and clarify it in person at the same time. I've updated it to what I think I meant?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Spec Clarification Clarifications to existing content in the spec
Projects
None yet
Development

No branches or pull requests

3 participants