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

Handling of Time Signature #11

Open
hbitteur opened this issue Apr 28, 2017 · 3 comments
Open

Handling of Time Signature #11

hbitteur opened this issue Apr 28, 2017 · 3 comments

Comments

@hbitteur
Copy link
Contributor

hbitteur commented Apr 28, 2017

If we except CommonTime and CutTime, a time signature is composed of 2 numbers (numerator and denominator).

Should we consider a time signature (say 8/12, assuming this can exist) as one global time symbol (combo, such as "8/12") or as two time number symbols (numerator, denominator such as "8" and "12") or as two sequences of time digit symbols (such as {"8"} and {"1", "2"})?

We can handle a limited set of predefined combos. Some are already in OmrShape class, perhaps we could a few more,but we can't address all possible combos.
We have to be able to recognize individual time digits.
Even for a combo, could MuseScore generate number symbols (one for num, one for den)? Perhaps also single digit symbols? The more symbols, the better (even if they overlap).

@wschweer
Copy link
Collaborator

Boundig boxes for numerator and denominator strings can be reconstructed by MuseScore. Its more expensive to do this for single glyphs.

@hbitteur
Copy link
Contributor Author

Perhaps we can forget about single digit extraction, provided that we address the most common 2-digit numbers found in time signature (say at least 10, 12, 16)?

@lasconic
Copy link
Collaborator

  • TimeSignature as a whole, should be labeled Time3_4 etc...
  • Numerator/Denominator should be labeled with denominator_timesig_3

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

3 participants