Re: Problem with merging notes and accidental placement in two voices

2015-07-21 Thread Ralph Palmer 
On Tue, Jul 21, 2015 at 3:29 PM, Simon Albrecht 
wrote:

>  Hi Ralph,
>
> this is issue 1134
> 
> . There are
> workarounds tracked there.
>
> HTH, Simon
>

Thanks, Simon, for the quick and helpful response! It looks like the
"human" workaround will do the trick.

Ralph

-- 
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Problem with merging notes and accidental placement in two voices

2015-07-21 Thread Simon Albrecht 

Hi Ralph,

this is issue 1134 
. There are 
workarounds tracked there.


HTH, Simon

Am 21.07.2015 um 21:13 schrieb Ralph Palmer:

Greetings -

(This is the second time - my original .png was too large.)

I'm running LilyPond 18.2 under Win7.

I'm attaching 3 files:
1) NoteMergeAndAccidentals.ly   :   LilyPond source file with no tweaks
2) NoteMergeAndAccidentals.pdf   :  a PDF of NoteMergeAndAccidentals.ly
3)NoteMergeAndAccidentalsOriginal.png   :   what I'm trying to replicate.

I'm having problems with some music in two vioces. I can "un-merge" 
the first two notes in the accompanying .ly file, but I can't seem to 
un-merge the accidentals. I'm also unable to get separate the a-flat 
and a-natural and get their accidentals next to the notes.


I would appreciate any help with these issues.

Thanks for your time and attention,

Ralph

--
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com 


___
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

Problem with merging notes and accidental placement in two voices

2015-07-21 Thread Ralph Palmer 
Greetings -

(This is the second time - my original .png was too large.)

I'm running LilyPond 18.2 under Win7.

I'm attaching 3 files:
1) NoteMergeAndAccidentals.ly   :   LilyPond source file with no tweaks
2) NoteMergeAndAccidentals.pdf   :  a PDF of NoteMergeAndAccidentals.ly
3)NoteMergeAndAccidentalsOriginal.png   :   what I'm trying to replicate.

I'm having problems with some music in two vioces. I can "un-merge" the
first two notes in the accompanying .ly file, but I can't seem to un-merge
the accidentals. I'm also unable to get separate the a-flat and a-natural
and get their accidentals next to the notes.

I would appreciate any help with these issues.

Thanks for your time and attention,

Ralph

-- 
Ralph Palmer
Brattleboro, VT
USA
palmer.r.vio...@gmail.com
\version "2.18.2"

%%% Problem both with merging noteheads AND with accidentals 

\language "english" 

\relative c' { 
\clef treble
\key bf \major
\time 2/4
<< 
  \voiceOne
  { 
  e'8. r16 a,!8. r16 |
  } 
   \\
   \new Voice
   \voiceTwo
{ 
  ef'!8. r16 af,8 gf16 r |
} 
>>
}

NoteMergeAndAccidentals.pdf
Description: Adobe PDF document
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: merging notes

2013-09-06 Thread Nick Payne 
In the second bar, the filling in of the merged notehead on the half 
note is avoided if you rearrange the music to put the merged notes in 
the voices that are implicitly voiceOne and VoiceTwo:


\relative c''{ <<

\mergeDifferentlyHeadedOn

\mergeDifferentlyDottedOn

{

c8 d e d c d c4

e,8 a b c fis2

} \\ {

c2 c8. b16 c4

e,2 r

} \\ {

s1

g'2 d

}

>>
}

<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: merging notes

2013-09-06 Thread David Kastrup 
Peter Bjuhr  writes:

> On 09/06/2013 06:24 PM, Peter Bjuhr wrote:
>> But obviously the result you are after can be achieved in same
>> way. I will look into it further in a moment... 
>
> Maybe this is in the right direction...
>
> \version "2.17.10"
>
> lcl = { \revert MultiMeasureRest #'staff-position }
^

This one looks like a bug of the part combiner.  I'll try a fix.

> ma = \relative c' { \lcl
> \partcombineAutomatic
> d1 |
> \partcombineApart
> g2 g |
> \partcombineAutomatic
> R1
> \fermataMarkup }
> mb = \relative c' { \lcl
> d1 | d2 d | R1
> \fermataMarkup }
>
>
>   \new Staff <<
>   \set Staff.aDueText = #"ma + mb"
>   { \partcombine \ma \mb }
>   >>
>
> Best
> Peter

-- 
David Kastrup


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

Re: merging notes

2013-09-06 Thread Peter Bjuhr 


On 09/06/2013 06:24 PM, Peter Bjuhr wrote:
But obviously the result you are after can be achieved in same way. I 
will look into it further in a moment... 


Maybe this is in the right direction...

\version "2.17.10"

lcl = { \revert MultiMeasureRest #'staff-position }
ma = \relative c' { \lcl
\partcombineAutomatic
d1 |
\partcombineApart
g2 g |
\partcombineAutomatic
R1
\fermataMarkup }
mb = \relative c' { \lcl
d1 | d2 d | R1
\fermataMarkup }


  \new Staff <<
  \set Staff.aDueText = #"ma + mb"
  { \partcombine \ma \mb }
  >>

Best
Peter

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

Re: merging notes

2013-09-06 Thread Karl Hammar 
Peter Bjuhr:
> On 09/06/2013 11:32 AM, Karl Hammar wrote:
> > The same thing with rests, if only on rest, it applies both voices
> > if one rest and one note, seperate voices.
> > If only one whole note, both voices.
> >
> > Two whole notes at same pitch just looks strange.
> > Have a look at:
> >
> >   http://turkos.aspodata.se/motett/c_saint_saens/4_air.pdf
> >
> I refer again to Behind Bars by Elaine Gould. Here is a scan from p 52:
> https://docs.google.com/file/d/0B627QNBiKcXpdXFJWVpkR2o0MFE/edit?usp=sharing

Doesn't work for me, google complains I have a unsupported browser...
Or it might be that my connection is too slow.

It might wery well be so that Ms. Gould likes the double whole notes
and have some good rationale for it, but I only think it looks
strange, and if I thinks so, the choir will certantly also think so.

To lessen confusion, I'd like to merge them.

> Isn't this comparable to your example?
> >>
> >> >For the fermata you could perhaps find a solution here:
> >> >http://lsr.dsi.unimi.it/LSR/Item?id=372
> > Thanks, that worked.
> Great, thanks!

:)

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



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

Re: merging notes

2013-09-06 Thread David Kastrup 
David Kastrup  writes:

> Peter Bjuhr  writes:
>
>> On 09/06/2013 06:24 PM, Peter Bjuhr wrote:
>>> But obviously the result you are after can be achieved in same
>>> way. I will look into it further in a moment... 
>>
>> Maybe this is in the right direction...
>>
>> \version "2.17.10"
>>
>> lcl = { \revert MultiMeasureRest #'staff-position }
> ^
>
> This one looks like a bug of the part combiner.  I'll try a fix.

Tracker issue: 3534 (http://code.google.com/p/lilypond/issues/detail?id=3534)
Rietveld issue: 13302048 (http://codereview.appspot.com/13302048)
Issue description:
  Handle MultiMeasureRest direction in the part combiner like other
  elements  Since issue 3307, they did not require special
  positioning.

-- 
David Kastrup


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

Re: merging notes

2013-09-06 Thread Karl Hammar 
Peter Bjuhr:
> On 09/06/2013 11:06 AM, Karl Hammar wrote:
...
> I revised my answer now in the morning, hope you have seen it. An e2 
> shouldn't look like an e4, I agree!
> 
> But I still don't think it is a bug.
> If you use /oneVoice in this way 
> you have accept some additional fixing, which is also documented below.

Anyhow, you helped med solve one part!

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



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

Re: merging notes

2013-09-06 Thread Peter Bjuhr 


On 09/06/2013 06:02 PM, Karl Hammar wrote:

Doesn't work for me, google complains I have a unsupported browser...
Or it might be that my connection is too slow.
I have sent you the image if you like to see it. But perhaps it is 
unhelpful for your problem...


It might wery well be so that Ms. Gould likes the double whole notes
and have some good rationale for it, but I only think it looks
strange, and if I thinks so, the choir will certantly also think so.

To lessen confusion, I'd like to merge them.
It seems like this is not possible with the ordinary merging technique 
and the reason is probably the same as Gould's rationale, which I 
suggested in a previous mail - it will obscure the part writing. But 
obviously the result you are after can be achieved in same way. I will 
look into it further in a moment...


Best
Peter

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

Re: merging notes

2013-09-06 Thread Peter Bjuhr 


On 09/06/2013 11:32 AM, Karl Hammar wrote:

The same thing with rests, if only on rest, it applies both voices
if one rest and one note, seperate voices.
If only one whole note, both voices.

Two whole notes at same pitch just looks strange.
Have a look at:

  http://turkos.aspodata.se/motett/c_saint_saens/4_air.pdf


I refer again to Behind Bars by Elaine Gould. Here is a scan from p 52:
https://docs.google.com/file/d/0B627QNBiKcXpdXFJWVpkR2o0MFE/edit?usp=sharing

Isn't this comparable to your example?


>For the fermata you could perhaps find a solution here:
>http://lsr.dsi.unimi.it/LSR/Item?id=372

Thanks, that worked.

Great, thanks!

Best
Peter

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

Re: merging notes

2013-09-06 Thread Phil Holmes 
- Original Message - 
From: "Karl Hammar" 

To: 
Sent: Friday, September 06, 2013 10:06 AM
Subject: Re: merging notes



Peter Bjuhr:

On 09/05/2013 10:44 PM, Karl Hammar wrote:
> 
http://www.lilypond.org/doc/v2.16/Documentation/notation/multiple-voices#collision-resolution
>
> <<
>{
>  c8 d e d c d c4
>  g'2 fis
>} \\ {
>  c2 c8. b16 c4
>  e,2 r
>} \\ {
>  \oneVoice
>  s1
>  e8 a b c d2
>}



> 1, why is the snippet shown without the surronding \relative c'',
> it makes it confusing -- it starts in the wrong octave, doesn't it



If you click on the image you see the ly-file, and that in fact uses
surrounding \relative c''.


Yes, I know.


But it's assumed in the text.


Hmm, where is that assumption stated?




Section 1.4.1 of the Learning Manual.  The documentation assumes users have 
read the LM.


--
Phil Holmes 



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

Re: merging notes

2013-09-06 Thread Peter Bjuhr 


On 09/06/2013 11:06 AM, Karl Hammar wrote:

Yes, I know.

But it's assumed in the text.

Hmm, where is that assumption stated?

This is simply non-obvious and confusing that in some examples one
cannot copy the visibly code and get the shown result.

Sorry if I stated the obvious! I interpreted your question wrongly. I 
don't know enough of the documentation system to defend it. Maybe 
someone else can answer this!?


In what way isn't it a bug when an e2 looks like an e4.

If I really wanted a half note to look like a quater note I'd use e4*2,
then it is obvious in the code that I do something "unusual".

Yes, and

   The half note and eighth note at the start of the second measure
   are incorrectly merged because the automatic merge cannot
   successfully complete the merge when three or more notes line up
   in the same note column, and in this case the merged note head is
   incorrect.

after the third example confirms that "failing".

When writing ly-files, such "failings" would be very hard to spot.

I revised my answer now in the morning, hope you have seen it. An e2 
shouldn't look like an e4, I agree!


But I still don't think it is a bug. If you use /oneVoice in this way 
you have accept some additional fixing, which is also documented below.


Best
Peter

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

Re: merging notes

2013-09-06 Thread Eluze 
Peter Bjuhr wrote
> No, the merging in beat 1 bar 2 fails because the note should be white 
> and not black. My mistake! The corrected version is shown further below 
> with \shiftOn.

and if you're not happy with the shift you can correct it like

\shiftOn
\tweak NoteColumn.force-hshift #-.0001
g'2 fis

Eluze



--
View this message in context: 
http://lilypond.1069038.n5.nabble.com/merging-notes-tp150280p150322.html
Sent from the User mailing list archive at Nabble.com.

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

Re: merging notes

2013-09-06 Thread Karl Hammar 
Peter Bjuhr:
> I will try to find a solution to your actual problem now.

That's very kind of you, thanks.

> > Now, I want to merge two same looking notes. It works well for the
> > c4 in the third beat, 1st measure, above.
> >
> > \version "2.17.10"
> >
> > lcl = { \revert MultiMeasureRest #'staff-position }
> > ma = \relative c' { \lcl d1 | g2 g | R1\fermataMarkup }
> > mb = \relative c' { \lcl d1 | d2 d | R1\fermataMarkup }
> >
> > \new Staff <<
> >\new Voice = "Va" { \voiceOne \ma }
> >\new Voice = "Vb" { \voiceTwo \mb }
> > I need to name the voices for a later \lyricsto,
> > I want the \voiceOne/Two so the stems comes out right.
> How do you want the stems?

Top voice with stems up, bottom voice with stems down as shown in
my example.

> > How do I make the first d1's merge ?
> The problem here is that these are whole note's/semibreve's without 
> stems, and if they are merged how would you know that there are two voices!?

The same thing with rests, if only on rest, it applies both voices
if one rest and one note, seperate voices.
If only one whole note, both voices.

Two whole notes at same pitch just looks strange.
Have a look at:

 http://turkos.aspodata.se/motett/c_saint_saens/4_air.pdf

> There are perhaps a technical solution to this but I leave that to the 
> experts. But this and your previous question hints at you wanting to use 
> some kind of part combining!?

No, part combining makes voices to be combined into chords.
I could use it for the above, but if one of the voices are split,
then you don't know wich voice is split after part combiner.

> > How do I make the \fermataMarkup merge ?
> For the fermata you could perhaps find a solution here: 
> http://lsr.dsi.unimi.it/LSR/Item?id=372

Thanks, that worked.

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



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

Re: merging notes

2013-09-06 Thread Karl Hammar 
Peter Bjuhr:
> On 09/05/2013 10:44 PM, Karl Hammar wrote:
> > http://www.lilypond.org/doc/v2.16/Documentation/notation/multiple-voices#collision-resolution
> >
> > <<
> >{
> >  c8 d e d c d c4
> >  g'2 fis
> >} \\ {
> >  c2 c8. b16 c4
> >  e,2 r
> >} \\ {
> >  \oneVoice
> >  s1
> >  e8 a b c d2
> >}

> > 1, why is the snippet shown without the surronding \relative c'',
> > it makes it confusing -- it starts in the wrong octave, doesn't it

> If you click on the image you see the ly-file, and that in fact uses 
> surrounding \relative c''.

Yes, I know.

> But it's assumed in the text.

Hmm, where is that assumption stated?

I can find below "1.1.3 Displaying pitches", "Clef", 2nd sentence
(page 16 in my pdf):

 Middle C is shown in every example. 

Then on p.18, Selected Snippets, absolute entry is used
p.20 Key signature, the fis happens to be fis'' without any explanations
and the example just below works by simple copy-and-paste

This is simply non-obvious and confusing that in some examples one
cannot copy the visibly code and get the shown result.

> > 2, the e,2 in the second voice is hidden by the d8 in the third voice
> > isn't that a bug ?
> (I think you mean the e8 in the third voice.)

Yes, typo by me.

> I don't think it is a bug, 

In what way isn't it a bug when an e2 looks like an e4.

If I really wanted a half note to look like a quater note I'd use e4*2,
then it is obvious in the code that I do something "unusual".

> but it's contradictory to the text; as it says: "[...] beat 1 in bar 2, 
> where the automatic merging fails.". The merging appears fine!

Yes, and 

  The half note and eighth note at the start of the second measure
  are incorrectly merged because the automatic merge cannot
  successfully complete the merge when three or more notes line up
  in the same note column, and in this case the merged note head is
  incorrect.

after the third example confirms that "failing".

When writing ly-files, such "failings" would be very hard to spot.

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



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

Re: merging notes

2013-09-06 Thread Peter Bjuhr 




I will try to find a solution to your actual problem now.


Now, I want to merge two same looking notes. It works well for the
c4 in the third beat, 1st measure, above.

\version "2.17.10"

lcl = { \revert MultiMeasureRest #'staff-position }
ma = \relative c' { \lcl d1 | g2 g | R1\fermataMarkup }
mb = \relative c' { \lcl d1 | d2 d | R1\fermataMarkup }

\new Staff <<
   \new Voice = "Va" { \voiceOne \ma }
   \new Voice = "Vb" { \voiceTwo \mb }
I need to name the voices for a later \lyricsto,
I want the \voiceOne/Two so the stems comes out right.

How do you want the stems?

How do I make the first d1's merge ?
The problem here is that these are whole note's/semibreve's without 
stems, and if they are merged how would you know that there are two voices!?


There are perhaps a technical solution to this but I leave that to the 
experts. But this and your previous question hints at you wanting to use 
some kind of part combining!?

How do I make the \fermataMarkup merge ?
For the fermata you could perhaps find a solution here: 
http://lsr.dsi.unimi.it/LSR/Item?id=372


Best
Peter
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: merging notes

2013-09-06 Thread Peter Bjuhr 

I revise my answer from yesterday:

On 09/05/2013 11:48 PM, Peter Bjuhr wrote:




2, the e,2 in the second voice is hidden by the d8 in the third voice
isn't that a bug ?
(I think you mean the e8 in the third voice.) I don't think it is a 
bug, but it's contradictory to the text; as it says: "[...] beat 1 in 
bar 2, where the automatic merging fails.". The merging appears fine!
No, the merging in beat 1 bar 2 fails because the note should be white 
and not black. My mistake! The corrected version is shown further below 
with \shiftOn.


I will try to find a solution to your actual problem now.

Best
Peter


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

Re: merging notes

2013-09-05 Thread Peter Bjuhr 


On 09/05/2013 10:44 PM, Karl Hammar wrote:

http://www.lilypond.org/doc/v2.16/Documentation/notation/multiple-voices#collision-resolution

<<
   {
 c8 d e d c d c4
 g'2 fis
   } \\ {
 c2 c8. b16 c4
 e,2 r
   } \\ {
 \oneVoice
 s1
 e8 a b c d2
   }
1, why is the snippet shown without the surronding \relative c'',
it makes it confusing -- it starts in the wrong octave, doesn't it
If you click on the image you see the ly-file, and that in fact uses 
surrounding \relative c''. But it's assumed in the text.


2, the e,2 in the second voice is hidden by the d8 in the third voice
isn't that a bug ?
(I think you mean the e8 in the third voice.) I don't think it is a bug, 
but it's contradictory to the text; as it says: "[...] beat 1 in bar 2, 
where the automatic merging fails.". The merging appears fine!


3, if I remove the \oneVoice the graphics becomes sane, why is the
\oneVoice there ?

Yes, it is the \oneVoice that makes the merging happen, which was not 
supposed according to the text. My best explanation would be that 
\oneVoice makes the voice behave like it were a single voice instead of 
voice 3. And that do seem appropriate for the passage.


Best
Peter


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

merging notes

2013-09-05 Thread Karl Hammar 
In Documentation/out-www/notation.pdf, under 1.5.2 Multiple voices,
Collision resolution

http://www.lilypond.org/doc/v2.16/Documentation/notation/multiple-voices#collision-resolution

<<
  {
c8 d e d c d c4
g'2 fis
  } \\ {
c2 c8. b16 c4
e,2 r
  } \\ {
\oneVoice
s1
e8 a b c d2
  }
>>

1, why is the snippet shown without the surronding \relative c'',
   it makes it confusing -- it starts in the wrong octave, doesn't it

2, the e,2 in the second voice is hidden by the d8 in the third voice
   isn't that a bug ?

3, if I remove the \oneVoice the graphics becomes sane, why is the
   \oneVoice there ?

///

Now, I want to merge two same looking notes. It works well for the
c4 in the third beat, 1st measure, above.

I have:

\version "2.17.10"

lcl = { \revert MultiMeasureRest #'staff-position }
ma = \relative c' { \lcl d1 | g2 g | R1\fermataMarkup }
mb = \relative c' { \lcl d1 | d2 d | R1\fermataMarkup }

\new Staff <<
  \new Voice = "Va" { \voiceOne \ma }
  \new Voice = "Vb" { \voiceTwo \mb }
>>

I need to name the voices for a later \lyricsto,
I want the \voiceOne/Two so the stems comes out right.
(I'm using lilypond 2.17.10)

How do I make the first d1's merge ?
How do I make the \fermataMarkup merge ?

Regards,
/Karl Hammar

---
Aspö Data
Lilla Aspö 148
S-742 94 Östhammar
Sweden
+46 173 140 57



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

Re: Merging notes and shiftOn

2012-05-12 Thread Trevor Daniels 

Nick Payne wrote Saturday, May 12, 2012 7:23 AM


On 12/05/12 16:06, Nick Payne wrote:
In the documentation on collision resolution 
(http://lilypond.org/doc/v2.15/Documentation/notation/multiple-voices#collision-resolution), 
it states: "The \shiftOn command allows (but does not force) the notes in 
a voice to be shifted. When \shiftOn is applied to a voice, a note or 
chord in that voice is shifted *only* if its stem would otherwise collide 
with a stem from another voice, and only if the colliding stems point in 
the same direction." (the emphasis on *only* is mine).


However, in the example below, where I have to use shiftOff in the middle 
voice (to get the two F notes to merge) and shiftOn in the treble voice 
(to prevent the merged half notes from having their heads filled in), the 
two A half notes in the treble voice *are* being shifted, though from my 
reading of the sentence quoted above, the shift is not needed.


\version "2.15.38"

treble = \relative c''' {
\shiftOn
a2 a
}

bass = \relative c' {
f2 f
}

middle = \relative c' {
\shiftOff f8[ c'] b c f,[ c'] b c
}

\score {
\new Staff {
\clef treble
\mergeDifferentlyHeadedOn
<<
\context Voice = "1" { \voiceOne \treble }
\context Voice = "2" { \voiceTwo \bass }
\context Voice = "3" { \voiceThree \middle }
>>
}
\layout { }
}


p.s. I have just found out that if I replace \shiftOn with \shiftOn 
\override NoteColumn #'force-hshift = #0, then the notes in the treble 
voice do not actually get moved, and I still get the correct merging of 
the notes in the other voices. However, it still seems that the 
documentation does not correctly describe how shiftOn actually behaves.


You're right.  In your example the stems don't actually collide
because of the large vertical separation, but their note columns
still clash.  Perhaps we should change "collide" to "align" and
"colliding" to "aligning" in the text.  Maybe we need to add a
bit about "force-hshift not being overridden" too, which seems
a good work-around in this situation.

Ideally the code should be amended to test for a vertical
separation sufficiently large to avoid the stems overlapping,
in which case a shift would not be needed, and then the text
as written would be correct.

Trevor


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

Re: Merging notes and shiftOn

2012-05-11 Thread Nick Payne 

On 12/05/12 16:06, Nick Payne wrote:
In the documentation on collision resolution 
(http://lilypond.org/doc/v2.15/Documentation/notation/multiple-voices#collision-resolution), 
it states: "The \shiftOn command allows (but does not force) the notes 
in a voice to be shifted. When \shiftOn is applied to a voice, a note 
or chord in that voice is shifted *only* if its stem would otherwise 
collide with a stem from another voice, and only if the colliding 
stems point in the same direction." (the emphasis on *only* is mine).


However, in the example below, where I have to use shiftOff in the 
middle voice (to get the two F notes to merge) and shiftOn in the 
treble voice (to prevent the merged half notes from having their heads 
filled in), the two A half notes in the treble voice *are* being 
shifted, though from my reading of the sentence quoted above, the 
shift is not needed.


\version "2.15.38"

treble = \relative c''' {
\shiftOn
a2 a
}

bass = \relative c' {
f2 f
}

middle = \relative c' {
\shiftOff f8[ c'] b c f,[ c'] b c
}

\score {
\new Staff {
\clef treble
\mergeDifferentlyHeadedOn
<<
\context Voice = "1" { \voiceOne \treble }
\context Voice = "2" { \voiceTwo \bass }
\context Voice = "3" { \voiceThree \middle }
>>
}
\layout { }
}


p.s. I have just found out that if I replace \shiftOn with \shiftOn 
\override NoteColumn #'force-hshift = #0, then the notes in the treble 
voice do not actually get moved, and I still get the correct merging of 
the notes in the other voices. However, it still seems that the 
documentation does not correctly describe how shiftOn actually behaves.


Nick

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

Merging notes and shiftOn

2012-05-11 Thread Nick Payne 
In the documentation on collision resolution 
(http://lilypond.org/doc/v2.15/Documentation/notation/multiple-voices#collision-resolution), 
it states: "The \shiftOn command allows (but does not force) the notes 
in a voice to be shifted. When \shiftOn is applied to a voice, a note or 
chord in that voice is shifted *only* if its stem would otherwise 
collide with a stem from another voice, and only if the colliding stems 
point in the same direction." (the emphasis on *only* is mine).


However, in the example below, where I have to use shiftOff in the 
middle voice (to get the two F notes to merge) and shiftOn in the treble 
voice (to prevent the merged half notes from having their heads filled 
in), the two A half notes in the treble voice *are* being shifted, 
though from my reading of the sentence quoted above, the shift is not 
needed.


\version "2.15.38"

treble = \relative c''' {
\shiftOn
a2 a
}

bass = \relative c' {
f2 f
}

middle = \relative c' {
\shiftOff f8[ c'] b c f,[ c'] b c
}

\score {
\new Staff {
\clef treble
\mergeDifferentlyHeadedOn
<<
\context Voice = "1" { \voiceOne \treble }
\context Voice = "2" { \voiceTwo \bass }
\context Voice = "3" { \voiceThree \middle }
>>
}
\layout { }
}
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user