Re: Midi dynamics behaviour changed in latest git HEAD

[H. S. Teoh]

On Sat, Aug 20, 2016 at 03:25:10PM +0300, Heikki Tauriainen wrote:
> Hi,
> 
> On Fri, 2016-08-19 at 10:16 -0700, H. S. Teoh wrote:
> > I've been using lilypond from git HEAD (mainly because lilypond in
> > my distro is too old, still stuck at 2.18, and I need features and
> > fixes in 2.19), and recently I noticed that midi dynamics in my
> > piano scores aren't being rendered correctly anymore.  Looking into
> > the commit log, I saw this:
> > 
> >     Issue 4947: Link notes to dynamics in Dynamic_performer rather
> > than Staff_performer.  Dynamics in different voices are now
> > independent.
[...]
> Would instantiating the Voice contexts explicitly in the MIDI \score,
> 
> <<
>     \new Staff \new Voice << \rightHandPart \dynamicsPart >>
>     \new Staff \new Voice << \leftHandPart \dynamicsPart >>
> >>
> 
> help?  This is what I'd try first to ensure that \rightHandPart and
> \dynamicsPart will end up in the same Voice (and not in any separate
> implicit Voices which could get instantiated implicitly otherwise).
[...]

That did the trick.  Thanks a lot!!!


T

-- 
Famous last words: I wonder what will happen if I do *this*...