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

braille: multiple consecutive whole measure rests #19

Closed
mscuthbert opened this issue Nov 11, 2013 · 2 comments
Closed

braille: multiple consecutive whole measure rests #19

mscuthbert opened this issue Nov 11, 2013 · 2 comments

Comments

@mscuthbert
Copy link
Member

What steps will reproduce the problem?

from music21 import *
p = stream.Part()
for _ in range(8):
r1 = note.Rest()
r1.duration.type='whole'
p.append(r1)
p.show('braille')

What is the expected output?

⠀⠀⠼⠙⠲⠀⠀⠀
⠼⠁⠀⠼⠓⠍⠣⠅

What do you see instead?

⠀⠀⠀⠀⠀⠀⠀⠀⠼⠙⠲⠀⠀⠀⠀⠀⠀⠀⠀⠀

⠼⠁⠀⠍⠀⠶⠀⠶⠀⠶⠀⠶⠀⠶⠀⠶⠀⠍⠣⠅

What version of the product are you using?

svn trunk

On what operating system?

Debian GNU/Linux

Please provide any additional information below.

Multiple consecutive whole measure rests can and should be transcribed
in a more concise way. Except for when we are doing bar-over-bar,
two consecutive whole measure rests should simply be written as ⠍⠍, and
more then two consecutive whole measure rests are written with a number
sign (⠼) followed by the number of rests (in our case ⠓ which means 8)
followed by the whole-rest sign (⠍).

This device is especially useful in music with several parts, or if a particular
instrument has a few measures rest. It is not possible to use in
bar-over-bar format of course, but that should not be used for a single
part like in our example above anyway.

@mscuthbert
Copy link
Member Author

Will need more unit tests / doctests in segment.py before attempting. But shouldn't be too hard once the code is better known.

@mscuthbert
Copy link
Member Author

I'm following the Enhancement model suggested at http://brianegranger.com/?p=249 -- closing the issue here; if others believe it is important, they can reopen the issue.

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