|
From: | Urs Liska |
Subject: | Re: How to work with large orchestral1 projects |
Date: | Mon, 22 Feb 2016 09:02:29 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 |
Am 22.02.2016 um 08:51 schrieb
Carl-Henrik Buschmann:
Hi again, which is very well thought and nearly there.
There are two issues with your code here: a) Stem direction If you use the temporary polyphony construct like you do LilyPond will implicitly create new voices with \voiceOne and \voiceTwo set. So the a is considered the upper voice of a two-part setting. Of course this is usually correct but not in your case. The most immediate solution is to add \oneVoice before the a.. Alternatively you can choose the alternative syntax for temporary polyphony: << { a2 } \new Voice { s4 \sfz \> s4 \pp \< } >> This syntax will let the *first* voice (with the a) *continue* the voice before and after the polyphonic section. So when you have \oneVoice before the a will stick to that. This is sometimes even *necessary*, namely when you have to start/stop a spanner like a dynamic or a slur inside that section. b) not printing at all You will have got a " warning: unterminated crescendo" in your console output, isn't it? The crescendo goes nowhere. Probably you *did* write the \ff, but not inside the voice where you started the crescendo. Therefore LilyPond considers it unterminated and can't print it. I'm not sure why this is propagated to the preceding dynamics, but it's clear that this is the reason. So you have to extend your polyphonic section to include the \ff, then the dynamics will be printed. HTH Urs
|
[Prev in Thread] | Current Thread | [Next in Thread] |