Re: Dynamics [pl|sp]acing weirdness

2023-12-15 Thread Kieren MacMillan
Hi MIchael, > While that works, wrapping that combo isn't required all the time. E.g. when > you have > dynamicsA = { > s2. s4\mf\< | s2 s2\f | > } That’s because this version does not use \after, which is a music function that expects a single musical expression as its first parameter. >

Re: Dynamics [pl|sp]acing weirdness

2023-12-15 Thread Michael Gerdau
Hi Kieren, thanks for answering :) I've come across some placing or spacing weirdness with dynamics. In the attached example \dynamicsA is what I tried to code, aka the \< starts directly after the \mf. What I expected is what you see in \dynamicsB. However it seems as if the combo \mf\<

Re: Dynamics [pl|sp]acing weirdness

2023-12-15 Thread Kieren MacMillan
Hi Michael, > I've come across some placing or spacing weirdness with dynamics. > In the attached example \dynamicsA is what I tried to code, aka the \< starts > directly after the \mf. What I expected is what you see in \dynamicsB. > However it seems as if the combo \mf\< does use some musical

Dynamics [pl|sp]acing weirdness

2023-12-15 Thread Michael Gerdau
Hi list! I've come across some placing or spacing weirdness with dynamics. In the attached example \dynamicsA is what I tried to code, aka the \< starts directly after the \mf. What I expected is what you see in \dynamicsB. However it seems as if the combo \mf\< does use some musical time