[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: why must a full measure rest (2/2) have a direction that will cause
From: |
Carl Sorensen |
Subject: |
Re: why must a full measure rest (2/2) have a direction that will cause a collision? |
Date: |
Tue, 21 Sep 2021 01:58:53 +0000 |
User-agent: |
Microsoft-MacOutlook/10.10.1b.201012 |
On 9/20/21, 7:10 PM, "lilypond-user on behalf of Kenneth Wolcott"
<lilypond-user-bounces+carl.d.sorensen=gmail.com@gnu.org on behalf of
kennethwolcott@gmail.com> wrote:
see attachment of what looks fine (to me) even though I received the
warnings...
On Mon, Sep 20, 2021 at 6:06 PM Kenneth Wolcott
<kennethwolcott@gmail.com> wrote:
>
> why must a full measure rest (2/2) have a direction that will cause a
collision?
>
> I tried using \stemDown, but that had no effect.
>
> warning:
> ========
> blah.ly:34:7: warning: cannot resolve rest collision: rest direction not
set
> {
> d,1\rest d,1\rest d,1\rest d,1\rest b1\rest b1\rest }
> ===========
>
> My cue notes are well above the bass clef d, and well above the treble
clef b.
>
> ++++++++++++++
> <<
> { d,1\rest d,1\rest d,1\rest d,1\rest b1\rest b1\rest }
> \new CueVoice {
> \stemUp r4 b, cs ds'^"Tromboni" |
> e4 fs gs r |
> r4 a b cs' |
> d'4 ds' e' \cueClef "treble" \tuplet 3/2 { c''8 c'' c'' } |
> c''4 c''8 c'' c''4 c''8 c'' |
> c''4 c'' c'' c'' |
> \cueClefUnset
> }
> >>
> +++++++++++++++
Your code did not produce a warning when I compiled it in 2.22.1
But it also didn't show the same as your screenshot.
And it didn't have the "\language english" statement that would allow it to
compile.
Please give us a compilable snippet that shows your problem, so I can see if
it's reproducible on my machine.
Thanks,
Carl