-
Notifications
You must be signed in to change notification settings - Fork 1
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
multimeasure rests #25
Comments
Hey Zvony (@nagymusic), I kinda demoted multimeasure rests in the updated rmakers, largely because my own use of multimeasure rests always seemed to be in the creation of duration-multiplied mm rests. So there's a new The The usage is super simple and looks like this:
|
Thanks, Trevor. This makes sense. I just have a quick follow up question. Is it possible to wrap
|
Hey Zvony I guess it's not possible to selectively replace ("force" in the language of the updated package) in the way you're looking for. That'll be really easy for me to add into the package in a bit. For now you can postprocess the output of your stack: use selectors to select the components you want to replace with multimeasure rests; then use |
Hey Trevor, As you suggested, I'm trying to replace the output of my stack by replacing the middle (third) measure in 4/8 with a new whole-measure rest measure using Thank you!
|
Trevor, I understand if you may not be able to answer this, but is it possible to apply the same (or similar) variables to
Many thanks, |
Hi Zvony,
Your current output looks like this:
[image: zvony.png]
What do you want to output instead? Multimeasure rests (instead of vanilla
rests) in measures 2 and 4?
Trevor.
…On Thu, Apr 30, 2020 at 2:26 PM nagymusic ***@***.***> wrote:
Trevor,
I had a chance to work on the application of selected multi-measure rests
within rmakers. Per your suggestion, I also reviewed the
rmakers.mutliplied_duration() function as it is implemented in the
makers.py module.
I understand if you may not be able to answer this, but is it possible to
apply the *same* (or *similar*) variables to
rmakers.multiplied_duration(abjad.MultimeasureRest) like it's done to
rmakers.force_rest() below? I ask this because in this way one may be
able to apply the same selections of measures tomultiplied_duration as it
is currently used with force_rests.
stack = rmakers.stack(
rmakers.accelerando(
[(1, 8), (1, 20), (1, 16)],
),
rmakers.force_rest(abjad.select().tuplets().get([1], 2)),
#rmakers.multiplied_duration(abjad.MultimeasureRest), => (abjad.select().tuplets().get([1], 2))?
rmakers.rewrite_rest_filled(),
rmakers.feather_beam(beam_rests=True, stemlet_length=0.75,),
rmakers.duration_bracket(),
rmakers.extract_trivial(),
)
divisions = [(4, 8), (3, 8), (4, 8), (3, 8)]
selection = stack(divisions)
lilypond_file = abjad.LilyPondFile.rhythm(selection, divisions)
abjad.show(lilypond_file)
Many thanks,
Zvony
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJFPOZZLL4CWCURADAOZ3RPG7FTANCNFSM4J2A2PRA>
.
--
Trevor Bača
www.trevorbaca.com
soundcloud.com/trevorbaca
|
Thanks, Trevor. That's correct - Multimeasure rests instead of vanilla |
Hi Zvony,
Alas, there's no corresponding method for forcing notes / rest to
multimeasure rests in the rmakers package.
Do it "by hand" after you've made your selection with stack: loop, look for
the rests in question, make a multimeasure rest equal in duration, and
replace.
Trevor.
…On Thu, Apr 30, 2020 at 6:00 PM nagymusic ***@***.***> wrote:
Thanks, Trevor. That's correct - Multimeasure rests instead of vanilla
rests in measures 2 and 4.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#25 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABMJFPKT6END5UKKNSDQ5F3RPHYG3ANCNFSM4J2A2PRA>
.
--
Trevor Bača
www.trevorbaca.com
soundcloud.com/trevorbaca
|
What indicator has replaced
use_multimeasure_rests=True
in the updated version ofrmakers
?Thanks!
-Zvony
The text was updated successfully, but these errors were encountered: