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.

Sign up for GitHub

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

Jump to bottom

Fix doublestop application over fermata measures #27

Open

trevorbaca opened this issue Nov 12, 2018 · 0 comments

Assignees

Labels

bug

Owner

trevorbaca commented Nov 12, 2018

The command ...

maker(
   (82, 88),
   baca.pitch('<D5 Fqs5>'),
   )

... generates LilyPond output with incorrect timing when 86 is a fermata measure.

Might have something to do with the way that the segment-maker does (or does not) cache fermata measure ghost notes.

The text was updated successfully, but these errors were encountered:

trevorbaca added the bug label

trevorbaca self-assigned this

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