Thanks Thomas. Your note fixed all.
I found the per-voice association casually, then I even googled "lilypond
dynamics per-voice" but could not find anything specific for 2.19: then,
without your suggestion, given that this default behaviour is not documented
and the official snippets use another default behaviour, it seemed a bug.
Il lunedì 18 novembre 2019, 22:09:49 CET, Thomas Morley
<[email protected]> ha scritto:
Am Mo., 18. Nov. 2019 um 17:00 Uhr schrieb Paolo Prete <[email protected]>:
>
> Hello,
>
> Regarding my previous question,
Please link to it.
> I just checked that there's a bug on the dynamics of the produced midi output
> for a piano staff.
> The bug can be reproduced on the 2.19 version. Please, check this snippet (
> from http://lsr.di.unimi.it/LSR/Item?id=357 ), with Lilybin
>
> http://lilybin.com/eg700v/1
>
>
> The same error doesn't occur if you compile the snippet with 2.18 version.
>
> 1) Is there a workaround for that?
> 2) Is there a particular version of the 2.19 branch that doesn't cause the
> bug?
>
> Thanks
> Paolo
I don't see any bug- nor error-description...
Dynamics are associated per Voice since 2.19.x.
In a Dynamics-context usually spacers are used, so it's pure graphic.
The voice-association seems to be a reasonable default.
If you want it different, add the "Dynamic_performer" to the context
of your choice in \midi {}
Probably a documentation-issue.
Cheers,
Harm
