Navigation Menu

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

Define how to encode instrument transposition #111

Closed
joeberkovitz opened this issue May 11, 2018 · 4 comments
Closed

Define how to encode instrument transposition #111

joeberkovitz opened this issue May 11, 2018 · 4 comments

Comments

@joeberkovitz
Copy link
Contributor

This issue notes the need to represent the transposition of instruments including both key changes and octave shifts.

This is related to the more specialized concerns in #4 and #34 but concerns the general nature of the transposition.

@clnoel
Copy link

clnoel commented Apr 15, 2019

I am commenting here to draw attention to the fact that there is an issue already to deal with these specifics, since part of the proposals in the general issue #138 include the addition of a <transposition> open-ended direction, which can handle several of the cases here. We should probably discuss here how to use that in conjunction with visible octava, key-changes, or clef-changes.

@adrianholovaty
Copy link
Contributor

See pull request #158 for some work on octave shifts.

@adrianholovaty adrianholovaty changed the title Support transposition and octave shifts Define how to encode instrument transposition Jun 23, 2020
@adrianholovaty
Copy link
Contributor

(Just renamed this issue to make the intent clearer.)

@adrianholovaty
Copy link
Contributor

Marking this closed in favor of #287.

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

No branches or pull requests

5 participants