bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MIDI dynamics doesn't apply to multi-voice measures


From: Pavel Roskin
Subject: Re: MIDI dynamics doesn't apply to multi-voice measures
Date: Sat, 29 Oct 2011 20:17:00 -0400
User-agent: Internet Messaging Program (IMP) H3 (4.1.4)

Quoting Carl Sorensen <address@hidden>:

On 10/29/11 8:09 AM, "Pavel Roskin" <address@hidden> wrote:

Quoting Keith OHara <address@hidden>:

Pavel Roskin <proski <at> gnu.org> writes:

I'm trying to change relative loudness on the melody and the
accompaniment, by it turn out the MIDI dynamics doesn't apply to the
measures that have multiple voices.

You now need to put some dynamic mark at the start of every voice,
not just the start of every staff.

I tried adding dynamic marks in the first multi-voice measures for the
left and the right hand, but it's not enough.  I'm afraid I'll need
them in every measure.  Also, I'll need to make them transparent, or
the score would be hard to read.  It's easier for me to edit the
resulting MIDI-file.

You're probably using the << \\ >> construct.  This creates temporary
voices.

Yes. It actually created some annoyances. For instance, I could not use legato between single-voice and multi-voice measures.

Please try with explicitly instantiated voices, as shown in section 3.2.2
of the Notation Reference:

http://lilypond.org/doc/v2.15/Documentation/learning/explicitly-instantiati
ng-voices

That's what I tried first, but somehow I didn't notice the documentation about \oneVoice. I didn't like that all the stems in the first voice would go up, so I decided to use temporary voices.

Now that I know about \oneVoice, I'll try to reorganize the score to use explicitly instantiated voices.

There are still some benefits in having all notes on the staff in one place. I hope the bugs with temporary voices would be fixed and they would be treated like the explicitly instantiated ones.

Thank you for your reply, it was really helpful!

--
Regards,
Pavel Roskin



reply via email to

[Prev in Thread] Current Thread [Next in Thread]