Hi Mark,

I use the second one, with explicit voice-setting, and in that construction I encountered the problems mentioned in the OP. But the solutions offered by David and Matthew, in the previous answers, work in my case.

Thanks for your answer!

regards,
Jogchum
.
Op 25-09-18 om 22:18 schreef Mark Stephen Mrotek:
Jogchum,

I encountered the same when setting multi-voiced fugues and using the
<<{  }\\{   }\\{  }>> construct. Is that what you use?

My solution is to set each voice explicitly, e.g.,

\new Voice = "soprano"
      { \voiceOne \relative c'' {
               f4 f f f }
      }
\new Voice = "alto"
      { \voiceTwo \relative c'' {
aes4 aes aes aes }
      }

More information here
http://lilypond.org/doc/v2.19/Documentation/learning/explicitly-instantiatin
g-voices

Mark


-----Original Message-----
From: lilypond-user
[mailto:lilypond-user-bounces+carsonmark=ca.rr....@gnu.org] On Behalf Of
Jogchum Reitsma
Sent: Tuesday, September 25, 2018 12:13 PM
To: lilypond-user <lilypond-user@gnu.org>
Subject: Octave shifts in polyphonic setting

Hi,

When entering a piece of music with some one-, some two- and some
three-voiced bars, quite often notes in previous bars go up or down an
octave, when entering new bars.
Restoring this from the first bars affected by adding or deleting
apostrophes or comma's, sometimes lead again to side effects. Rather
frustrating...

Is there a way to prevent this?

regards, Jogchum Reitsma



_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user




_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to