Re: how to resolve note collisons ?

2005-04-03 Thread Gilles
Hello.
 
> But this did not help me. The problem remains (with 2.4.2 version) 
> exactly the same.  I have the very same warning message during 
> compilation (translated from french) :
> 
> Warning : too much "column-note" collisions. Will be ignored.

I would guess that this warning comes from something else, as it 
doesn't show up when I compile your test case (see the attached
file "test.ly").  Here I get on stdout:

GNU LilyPond 2.4.2
Processing `test.ly'
Parsing...
Interpreting music... [3]
Preprocessing graphical objects...
Calculating line breaks...
Interpreting music...
MIDI output to `test.midi'...
Track...
Layout output to `test.tex'...
Converting to `test.dvi'...
Converting to `test.ps'...
Converting to `test.pdf'...


Best regards,
Gilles
\version "2.4.2"

global = {
 \time 4/4
 \key c \major
}

dessus = \relative c' {
 r4 g'4 fis4 g4
 % 35 :
 d4 g4. f8 [ e8 d8 ]
}

basse = \relative c {
 \stemDown
 fis4 g4 d4 g4 ~
 % 35 :
 g8 [ f8 e8 d8 ] c2
}

choraltheme = \relative c {
 d'1
 % 35 :
 % the following instruction does nothing ; why ?
 g,1
}
\score {
   {
 \context PianoStaff <<
   \context Staff = "dessus" <<
 \global
 \clef violin
 \dessus
   >>
   \context Staff = "basse" <<
 \global
 \clef bass
 \context Voice = "basse" { \voiceTwo \basse }
 \context Voice = "choral" { \voiceOne \choraltheme }
   >>
 >>

 \bar "|."
   }
   \layout {}
   \midi{ \tempo 4 = 100  }

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


Re: how to resolve note collisons ? [without shouting ;-)]

2005-04-02 Thread Gilles

> I can't solve note collision in the following example ; I send a picture 
> of the collision.

Modify the "basse" \context, as follows:

%-
   \context Staff = "basse" <<
 \global
 \clef bass
 \context Voice = "basse" { \voiceTwo \basse }
 \context Voice = "choral" { \voiceOne \choraltheme }
   >>
%-
 
> I tried to use the following instruction  to push a note :
> \once \override NoteColumn  #'force-hshift = #10
> with no result.

With the above, it won't be necessary to try and move that note.


Best,
Gilles


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