Re: using oneVoice vs force-hshift in polyphany and alternatives

[Stephen]

From: "Mats Bengtsson" <address@hidden>
To: "Stephen" <address@hidden>
Cc: <address@hidden>
Sent: Thursday, April 20, 2006 12:24 AM
Subject: Re: using oneVoice vs force-hshift in polyphany and alternatives


> Quoting Stephen <address@hidden>:
>
> > Sure, the notes are in the right place. The interaction between the 
> > various parts is baffling though. Using \oneVoice to set the notes over 
> > one another seems to make the stems go up; \stemDown erases the effect of 
> > \oneVoice and \oneVoice cancels \stemDown. Apparently \override 
> > NoteColumn #'force-hshift = #0.0 accomplishes the what I want without 
> > side effects.
> >
> > What is \oneVoice meant to be used for? Can someone list separately all 
> > the things it does?
>
> See Sect. "Explicitly instantiating voices" for a list of what \voiceOne, 
> ..., \voiceFour do. \oneVoice reverts the settings
> done by any of \voiceOne ... \voiceFour, so among others it does
> a \revert Stem #'direction
> which is what you noted.

Thank you for the reply. Yes, I did note that \oneVoice undoes the effect of 
a previous \stemDown. If I want to use \oneVoice, the stem must already be 
in the direction that I want, hence the line \\ { s4. } when I want the stem 
to switch the other way. But \stemDown also resets the horizontal placement 
of the note if it follows \oneVoice, so they both mutually reverse one 
another.

If I had a list of everything \oneVoice does, I could pick and choose the 
effect that I want. \revert Stem #'direction is a good hint though. Perhaps 
\override NoteColumn #'force-hshift = #0.0 is exactly what \oneVoice does?

Stephen

>   /Mats
>
> > Finally, I don't understand the scoping rules at play here. How come I 
> > can comment out some of the stem overrides while leaving them in effect?
> >
> > Stephen