lilypond-user
[Top][All Lists]
Advanced

[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: Kenneth Wolcott
Subject: Re: why must a full measure rest (2/2) have a direction that will cause a collision?
Date: Mon, 20 Sep 2021 19:54:02 -0700

Thanks, Carl.

Here's the erroi stream with the reduced Lilypond code.

Thanke,
Ken

GNU LilyPond 2.22.1
Processing `Hungarian_March_from_La_Damnation_de_Faust_MWE.ly'
Parsing...
Interpreting music...[8][8]
Preprocessing graphical objects...
Interpreting music...
MIDI output to `Hungarian_March_from_La_Damnation_de_Faust_MWE.midi'...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Hungarian_March_from_La_Damnation_de_Faust_MWE.ly:22:17: warning:
cannot resolve rest collision: rest direction not set
    { \stemDown
                d,1\rest d,1\rest d,1\rest d,1\rest b1\rest b1\rest }
Hungarian_March_from_La_Damnation_de_Faust_MWE.ly:22:17: warning:
cannot resolve rest collision: rest direction not set
    { \stemDown
                d,1\rest d,1\rest d,1\rest d,1\rest b1\rest b1\rest }
Hungarian_March_from_La_Damnation_de_Faust_MWE.ly:22:35: warning:
cannot resolve rest collision: rest direction not set
    { \stemDown d,1\rest d,1\rest
                                  d,1\rest d,1\rest b1\rest b1\rest }
Hungarian_March_from_La_Damnation_de_Faust_MWE.ly:22:35: warning:
cannot resolve rest collision: rest direction not set
    { \stemDown d,1\rest d,1\rest
                                  d,1\rest d,1\rest b1\rest b1\rest }
Converting to `Hungarian_March_from_La_Damnation_de_Faust_MWE.pdf'...
Success: compilation successfully completed

%%%%%%%%%%%%%%%%%
\version "2.22.0"

global = {
  \language "english"
  \time 2/2
  \key c \major
  \clef bass
  \tempo "Allegro marcato" 2=88
}

\header {
  title = "Hungarian March"
  subtitle = "(from \"La damnation de Faust\")"
  composer = "Berlioz"
}

tuba = {
  \global
  \compressMMRests { R1*14 }
%  \compressMMRests { R1*6 }
<<
    { \stemDown 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
    }
  >>
  \bar "|."
}

\score {
  \new Staff \with { instrumentName = "Tuba" } {
    \set Staff.midiInstrument = "tuba"
    \tuba
  }
  \layout {}
  \midi {}
}
%%%%%%%%%%%%%%%%%

On Mon, Sep 20, 2021 at 6:59 PM Carl Sorensen <c_sorensen@byu.edu> wrote:
>
>
>
> 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
>
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]