Missing warning about clashing note columns in 2.19
Is this a bug/regression? 2.18.2 warns about clashing note columns, 2.19.44 does not. \version "2.19.44" << c''4 \\ \stemUp a'2 >> ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: "warning: ignoring too many clashing note columns"
It's almost certainly that you have simultaneous notes in 2 different voices, but have not told Lilypond how to avoid them occupying the same space. Check the notation reference for \voiceOne and \oneVoice. Oh - and the current released version is 2.14, with the current development version being 2.15.40. You're quoting old manuals. See http://lilypond.org/ -- Phil Holmes - Original Message - From: Anders Eriksson To: lilypond-user@gnu.org Sent: Saturday, June 23, 2012 8:19 AM Subject: "warning: ignoring too many clashing note columns" English is not my first language and I have some trouble understanding what this means "If notes from two voices with stems in the same direction are placed at the same position, and both voices have no shift or the same shift specified, the error message "warning: ignoring too many clashing note columns" will appear when compiling the LilyPond file." http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/Simultaneous-notes#Suppressing-warnings-for-clashing-note-columns I understand how to suppress the warnings, but I also would like to understand why! // Anders -- Computer says No! -- ___ 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
"warning: ignoring too many clashing note columns"
English is not my first language and I have some trouble understanding what this means "If notes from two voices with stems in the same direction are placed at the same position, and both voices have no shift or the same shift specified, the error message "warning: ignoring too many clashing note columns" will appear when compiling the LilyPond file." http://lilypond.org/doc/v2.12/input/lsr/lilypond-snippets/Simultaneous-notes#Suppressing-warnings-for-clashing-note-columns I understand how to suppress the warnings, but I also would like to understand why! // Anders -- Computer says No! ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: clashing note columns
Hello, On 20 October 2011 10:31, Nick Payne wrote: > )On 20/10/11 20:12, David Bobroff wrote: > > On 10/20/2011 8:46 AM, David Bobroff wrote: > > In a piece I'm doing in LilyPond I have a lot more single-staff polyphony > than I've dealt with before. I'm getting loads of: > > warning: ignoring too many clashing note columns > > The *output* looks fine. > > Ah, it seems I found my answer here: > > http://lilypond.org/doc/v2.14/Documentation/snippets/simultaneous-notes#suppressing-warnings-for-clashing-note-columns > > > Just be aware that if you turn on this override (\override NoteColumn > #'ignore-collision = ##t), and are also merging differently headed notes in > different voices, then the heads of merged half notes get filled in. Without > the override they don't: > Added doc enhancement (and patch) http://code.google.com/p/lilypond/issues/detail?id=2138 Thanks -- -- James ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Clashing note columns
- Original Message -
From: "Kris Van Bruwaene"
To:
Sent: Saturday, December 10, 2011 12:00 PM
Subject: Re: Clashing note columns
Here is an example.
Kris
http://old.nabble.com/file/p32951130/lilytest.ly lilytest.ly
If you'd cut even more of the code out, you would have seen that the lyrics
are irrelevant to the clashing notes. The notes clash because Lilypond uses
voices to split the parts in a single stave, and these are called voiceOne,
voiceTwo, etc. But you've redefined these, so it doesn't work. Redefine
your music with different names, and base your song on this structure:
\score {
<<
\new Staff = sopStaff {
<<
\new Voice = sopSplitpart { \voiceOne \voiceTwoA }
\new Voice = sopVoice { \voiceTwo \voiceOneA }
>>
}
>>
}
I think you'll find that this will work.
--
Phil Holmes
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Clashing note columns
Kris Van Bruwaene writes:
>> David Kastrup wrote:
>>>
>>> Kris Van Bruwaene writes:
>>>
I am typesetting a choral piece wich has two voices coming in unisono on
a
single staff, one with a whole note (g1), the other with two half notes
(g2
g2). The whole note and the first half note clash at the start of the
measure. I tried to avoid the clash with the remedies given in the
Lilypond
manual:
1) \once \override NoteColumn #'force-hshift = #2.7 g1
to shift the whole note to the right in the measure; no effect. And
2) in the lyrics:
{ al -- le -- lu -- \once \override LyricText #'self-alignment-X =
#CENTER
ia } (from Lilypond Snippets Lyrics alignment)
No effect either, probably because the syllable "ia" is too short. How
can
I solve this?
>>>
>>> I can't quite see your example code.
>
> Here is an example.
>
> Kris
> http://old.nabble.com/file/p32951130/lilytest.ly lilytest.ly
Well, first of all it is a surprisingly bad idea to redefine Lilypond's
existing commands \voiceOne and \voiceTwo since you will actually need
them for solving your problem.
Once you have renamed your own commands to something sensible, use
Lilypond's own \voiceOne in the upper of your two voices, and Lilypond's
own \voiceTwo in the lower of your two voices (I'd do that in the score
after \global rather than in the music definitions, but that's a matter
of taste).
The collisions will then get resolved amicably without any property
meddling of your own.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Clashing note columns
Here is an example.
Kris
http://old.nabble.com/file/p32951130/lilytest.ly lilytest.ly
David Kastrup wrote:
>
> Kris Van Bruwaene writes:
>
>> I am typesetting a choral piece wich has two voices coming in unisono on
>> a
>> single staff, one with a whole note (g1), the other with two half notes
>> (g2
>> g2). The whole note and the first half note clash at the start of the
>> measure. I tried to avoid the clash with the remedies given in the
>> Lilypond
>> manual:
>> 1) \once \override NoteColumn #'force-hshift = #2.7 g1
>> to shift the whole note to the right in the measure; no effect. And
>> 2) in the lyrics:
>> { al -- le -- lu -- \once \override LyricText #'self-alignment-X =
>> #CENTER
>> ia } (from Lilypond Snippets Lyrics alignment)
>> No effect either, probably because the syllable "ia" is too short. How
>> can
>> I solve this?
>
> I can't quite see your example code.
>
> --
> David Kastrup
>
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
--
View this message in context:
http://old.nabble.com/Clashing-note-columns-tp32919673p32951130.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Clashing note columns
Kris Van Bruwaene writes:
> I am typesetting a choral piece wich has two voices coming in unisono on a
> single staff, one with a whole note (g1), the other with two half notes (g2
> g2). The whole note and the first half note clash at the start of the
> measure. I tried to avoid the clash with the remedies given in the Lilypond
> manual:
> 1) \once \override NoteColumn #'force-hshift = #2.7 g1
> to shift the whole note to the right in the measure; no effect. And
> 2) in the lyrics:
> { al -- le -- lu -- \once \override LyricText #'self-alignment-X = #CENTER
> ia } (from Lilypond Snippets Lyrics alignment)
> No effect either, probably because the syllable "ia" is too short. How can
> I solve this?
I can't quite see your example code.
--
David Kastrup
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Clashing note columns
I am typesetting a choral piece wich has two voices coming in unisono on a
single staff, one with a whole note (g1), the other with two half notes (g2
g2). The whole note and the first half note clash at the start of the
measure. I tried to avoid the clash with the remedies given in the Lilypond
manual:
1) \once \override NoteColumn #'force-hshift = #2.7 g1
to shift the whole note to the right in the measure; no effect. And
2) in the lyrics:
{ al -- le -- lu -- \once \override LyricText #'self-alignment-X = #CENTER
ia } (from Lilypond Snippets Lyrics alignment)
No effect either, probably because the syllable "ia" is too short. How can
I solve this?
Using Lilypond version 2.14.1 on Arch Linux.
--
View this message in context:
http://old.nabble.com/Clashing-note-columns-tp32919673p32919673.html
Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com.
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: clashing note columns
)On 20/10/11 20:12, David Bobroff wrote:
On 10/20/2011 8:46 AM, David Bobroff wrote:
In a piece I'm doing in LilyPond I have a lot more single-staff
polyphony than I've dealt with before. I'm getting loads of:
warning: ignoring too many clashing note columns
The *output* looks fine.
Ah, it seems I found my answer here:
http://lilypond.org/doc/v2.14/Documentation/snippets/simultaneous-notes#suppressing-warnings-for-clashing-note-columns
Just be aware that if you turn on this override (\override NoteColumn
#'ignore-collision = ##t), and are also merging differently headed notes
in different voices, then the heads of merged half notes get filled in.
Without the override they don't:
\version "2.15.14"
\relative c' {
\mergeDifferentlyHeadedOn
<< { c16 a' b a } \\ { c,2 } >>
\override NoteColumn #'ignore-collision = ##t
<< { c16 a' b a } \\ { c,2 } >>
}
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: clashing note columns
On 10/20/2011 8:46 AM, David Bobroff wrote: In a piece I'm doing in LilyPond I have a lot more single-staff polyphony than I've dealt with before. I'm getting loads of: warning: ignoring too many clashing note columns The *output* looks fine. Example: http://notendur.centrum.is/~bobroff/lily/measure.png The 'd' in the half-note chord is tied over from the eighth note and is in the upper voice. If I don't flip the stem direction the stem is up and the note head offset. If I flip the stem it lines up as in the original (shown in the link) but I get the warning. Should I just ignore this and put up with the warnings? It is, of course, more important that the output look good, but I'd also like a 'clean' LilyPond run, too. -David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user Ah, it seems I found my answer here: http://lilypond.org/doc/v2.14/Documentation/snippets/simultaneous-notes#suppressing-warnings-for-clashing-note-columns -David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
clashing note columns
In a piece I'm doing in LilyPond I have a lot more single-staff polyphony than I've dealt with before. I'm getting loads of: warning: ignoring too many clashing note columns The *output* looks fine. Example: http://notendur.centrum.is/~bobroff/lily/measure.png The 'd' in the half-note chord is tied over from the eighth note and is in the upper voice. If I don't flip the stem direction the stem is up and the note head offset. If I flip the stem it lines up as in the original (shown in the link) but I get the warning. Should I just ignore this and put up with the warnings? It is, of course, more important that the output look good, but I'd also like a 'clean' LilyPond run, too. -David ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: ignoring too many clashing note columns
On Sep 11, 2010, at 6:39 PM, Helge Kruse wrote:
> Hello,
>
> I try to write a guitar score. In some measures I found small parts of
> polyphony. I tried to add temporarily a new voice, but I failed. The example
> below shows the intention. The second (commented) line gives nearly the same
> result and Lilypond doesn't show any error. But the g8 should be sound
> longer. That's why I want to tie it to a g4.
>
> Can I add this temporarily polyphony on demand or must it start at the first
> measure filled with lots of silent rests?
>
> Any suggestion is welcome.
>
>
> Helge
>
>
>
> \score
> {
> <<
> \relative c'' {
> c'8 b16 a~ a g16 g8~ << { g4 } \\ { fis8 e } >>
> % c'8 b16 a~ a g16 g8 fis8 e
> }
> \\
> \relative c' {
> a16 e'8. e e,16~e b''8 e,,16
> }
> >>
> }
Remember that you can't tie notes across voice contexts, so you can't use the
<<{}\\{}>> to tie the notes.
\score { << \new Voice { \voiceOne c8 b16 a~ a g16 g8~ << { \voiceOne g4 } \new
Voice { \voiceTwo fis8 e } >> } \new Voice { \voiceTwo a16 e'8. e e,16~ e b''8
e,,16 } >> }
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
ignoring too many clashing note columns
Hello,
I try to write a guitar score. In some measures I found small parts of
polyphony. I tried to add temporarily a new voice, but I failed. The
example below shows the intention. The second (commented) line gives
nearly the same result and Lilypond doesn't show any error. But the g8
should be sound longer. That's why I want to tie it to a g4.
Can I add this temporarily polyphony on demand or must it start at the
first measure filled with lots of silent rests?
Any suggestion is welcome.
Helge
\score
{
<<
\relative c'' {
c'8 b16 a~ a g16 g8~ << { g4 } \\ { fis8 e } >>
% c'8 b16 a~ a g16 g8 fis8 e
}
\\
\relative c' {
a16 e'8. e e,16~e b''8 e,,16
}
>>
}
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Any way to turn off "warning: ignoring too many clashing note columns"?
On Saturday 18 November 2006 23:12, Trevor Bača wrote:
> Hi,
>
> So my question is: is there any way to turn off the clashing note
> column warnings? I think this is the one place where one of Lily's
> warnings truly is completely harmless and I feel safe turning it off.
> More importantly, I really need to see any *other* warnings that Lily
> generates, which is quite hard given the original sourcefile (which
> runs many thousands of lines).
It would not be difficult to add a feature to disable warnings for specific
input spots, so you could write something like:
<<
\new Voice { \noWarning e8 }
\new Voice { \noWarning c8 }
>>
to suppress warnings only for the notes you have made strange tweaks to (I
don't have much time now, but you could ask Han-Wen if he likes the idea, and
if it's sponsorable).
--
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Any way to turn off "warning: ignoring too many clashing note columns"?
On 11/18/06, Trevor Bača <[EMAIL PROTECTED]> wrote:
Hi,
Unlike certain other programs, I've found that the warnings that Lily
issues during parsing, interpretation and preprocessing usually matter
a great deal; warnings are usually a sign either that there's a bug
that needs to be reported or that I'm doing something wrong that will
eventually come to haunt me.
For that reason I like to run completely 'clean' lilypond files that
generate no warnings whatsoever. And, in fact, this has always been
possible to do, even in very complex cases.
But now I've run into the following case:
%%% BEGIN %%%
\version "2.10.0"
\new Staff <<
\new Voice \with {
\override Stem #'direction = #up
} { c''4 c''4 c''4 c''4 }
\new Voice \with {
\override Stem #'transparent = ##t
\override NoteHead #'duration-log = #1
} { e'4 e'4 e'4 e'4 }
\new Voice \with {
\override Stem #'direction = #down
} { c'4 c'4 c'4 c'4 }
>>
%%% END %%%
GNU LilyPond 2.10.0
Processing `348.ly'
Parsing...
Interpreting music... [1]
Preprocessing graphical objects...
348.ly:6:27: warning: ignoring too many clashing note columns
} { c''4 c''4 c''4
c''4 }
348.ly:6:22: warning: ignoring too many clashing note columns
} { c''4 c''4
c''4 c''4 }
348.ly:6:17: warning: ignoring too many clashing note columns
} { c''4
c''4 c''4 c''4 }
348.ly:6:12: warning: ignoring too many clashing note columns
} {
c''4 c''4 c''4 c''4 }
Layout output to `348.ps'...
Converting to `348.pdf'...
The resulting output is letter-prefect (see ex), but there are copious
warnings. What's going on here is that I've concocted a special
notation that renders the middle notes of each 'chord' stemless with
Stem #'transparent = ##t (rather than, say, \remove Stem_engraver).
The Stems in the middle Voice still exist, though, so that clashing
note column warnings result.
So my question is: is there any way to turn off the clashing note
column warnings? I think this is the one place where one of Lily's
warnings truly is completely harmless and I feel safe turning it off.
More importantly, I really need to see any *other* warnings that Lily
generates, which is quite hard given the original sourcefile (which
runs many thousands of lines).
(I could of course pass Lily's output through sed, but that doesn't
seem as clean as a commandline option to disregard this specific
warning, for example.)
Alternatively, is there some way I can doctor up my example to avoid
the clashing note column warnings in the first place (which would
actually be preferrable)?
As of the 2.11 series, there is a new feature that can be turned on with
\override NoteColumn #'ignore-collision = ##t
in the Score context.
The example above then renders with no warnings.
--
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Any way to turn off "warning: ignoring too many clashing note columns"?
Hi,
Unlike certain other programs, I've found that the warnings that Lily
issues during parsing, interpretation and preprocessing usually matter
a great deal; warnings are usually a sign either that there's a bug
that needs to be reported or that I'm doing something wrong that will
eventually come to haunt me.
For that reason I like to run completely 'clean' lilypond files that
generate no warnings whatsoever. And, in fact, this has always been
possible to do, even in very complex cases.
But now I've run into the following case:
%%% BEGIN %%%
\version "2.10.0"
\new Staff <<
\new Voice \with {
\override Stem #'direction = #up
} { c''4 c''4 c''4 c''4 }
\new Voice \with {
\override Stem #'transparent = ##t
\override NoteHead #'duration-log = #1
} { e'4 e'4 e'4 e'4 }
\new Voice \with {
\override Stem #'direction = #down
} { c'4 c'4 c'4 c'4 }
%%% END %%%
GNU LilyPond 2.10.0
Processing `348.ly'
Parsing...
Interpreting music... [1]
Preprocessing graphical objects...
348.ly:6:27: warning: ignoring too many clashing note columns
} { c''4 c''4 c''4
c''4 }
348.ly:6:22: warning: ignoring too many clashing note columns
} { c''4 c''4
c''4 c''4 }
348.ly:6:17: warning: ignoring too many clashing note columns
} { c''4
c''4 c''4 c''4 }
348.ly:6:12: warning: ignoring too many clashing note columns
} {
c''4 c''4 c''4 c''4 }
Layout output to `348.ps'...
Converting to `348.pdf'...
The resulting output is letter-prefect (see ex), but there are copious
warnings. What's going on here is that I've concocted a special
notation that renders the middle notes of each 'chord' stemless with
Stem #'transparent = ##t (rather than, say, \remove Stem_engraver).
The Stems in the middle Voice still exist, though, so that clashing
note column warnings result.
So my question is: is there any way to turn off the clashing note
column warnings? I think this is the one place where one of Lily's
warnings truly is completely harmless and I feel safe turning it off.
More importantly, I really need to see any *other* warnings that Lily
generates, which is quite hard given the original sourcefile (which
runs many thousands of lines).
(I could of course pass Lily's output through sed, but that doesn't
seem as clean as a commandline option to disregard this specific
warning, for example.)
Alternatively, is there some way I can doctor up my example to avoid
the clashing note column warnings in the first place (which would
actually be preferrable)?
--
Trevor Bača
[EMAIL PROTECTED]
clashing-note-columns.png
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: slur between voices ... without clashing note columns
On 8/23/05, Erik Sandberg <[EMAIL PROTECTED]> wrote:
> On Tuesday 23 August 2005 14.38, Trevor Baca wrote:
> > The snippet here correctly renders a slur between voices ... but,
> > unfortunately generates clashing note column warnings in the process.
> >
> > Does anyone see a way to get the same result but without the clashing
> > note columns?
>
> In this particular example, you could do the first and second half of the bar
> as differen voices, something like:
>
> <<
> \context Staff=up {
> <<
> \new Voice { b16[ fis e \change Staff=down g,]( g,8) }
> \new Voice { s2 b16[ fis e \change
> Staff=down g,]( g,8) } }
> >>}
> >>
>
> This also reflects the music content better IMHO.
Yeah, I like that solution.
Here's a cut-and-paste-able version:
%%% REVISED SNIPPET %%
version "2.7.7"
\layout {
raggedright = ##t
}
\score {
\new PianoStaff <<
\context Staff = RH {
\clef treble
\key g \major
\time 2/4
<<
\new Voice {
\stemDown
16[
fis'16
e'16
\change Staff = LH
\stemUp
16](
g,8)
}
\new Voice {
s4
\stemDown
16[
fis'16
d'16
\change Staff = LH
\stemUp
16](
|
g,8)
}
>>
s4.
}
\context Staff = LH {
\clef bass
\key g \major
\time 2/4
g,8
s4.
|
s2
}
>>
}
% REVISED SNIPPET %
Trevor Bača
[EMAIL PROTECTED]
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Re: slur between voices ... without clashing note columns
On Tuesday 23 August 2005 14.38, Trevor Baca wrote:
> The snippet here correctly renders a slur between voices ... but,
> unfortunately generates clashing note column warnings in the process.
>
> Does anyone see a way to get the same result but without the clashing
> note columns?
In this particular example, you could do the first and second half of the bar
as differen voices, something like:
<<
\context Staff=up {
<<
\new Voice { b16[ fis e \change Staff=down g,]( g,8) }
\new Voice { s2 b16[ fis e \change
Staff=down g,]( g,8) } }
>>}
>>
This also reflects the music content better IMHO.
--
Erik
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
slur between voices ... without clashing note columns
The snippet here correctly renders a slur between voices ... but,
unfortunately generates clashing note column warnings in the process.
Does anyone see a way to get the same result but without the clashing
note columns?
Trevor.
% BEGIN SNIPPET %
\version "2.7.7"
wipeNote = {
\once \override NoteHead #'transparent = ##t
\once \override Stem #'transparent = ##t
}
\score {
\new PianoStaff <<
\context Staff = "theRH" {
\clef treble
\time 2/4
\key g \major
\stemDown
16
g'16
e'16
\change Staff = theLH
\stemUp
16
\change Staff = theRH
\stemDown
16
fis'16
d'16
\change Staff = theLH
\stemUp
16
\change Staff = theRH
\stemNeutral
|
s2
}
\context Staff = "theLH" {
\clef bass
\time 2/4
\key g \major
g,8
s16
\wipeNote
\stemUp
g16(
\stemNeutral
g,8)
s16
\wipeNote
\stemUp
fis16(
\stemNeutral
|
g,8)
s4.
}
>>
}
%% END SNIPPET %
Trevor Bača - [EMAIL PROTECTED]
slur-cross-voice.png
Description: PNG image
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
