|
From: | Knute Snortum |
Subject: | Re: Fermata above and below bar line generates warnings |
Date: | Sat, 25 Feb 2017 17:07:04 -0800 |
On Sat, Feb 25, 2017 at 4:42 PM, Knute Snortum <address@hidden> wrote:
> The following code produces the correct output of fermatas above and below
> the bar line, but it also emits warnings. Is there another way to do this
> without warnings, or can the warnings be suppressed? I got this code from:
>
What warnings? Without sharing that info, (1) you are expecting us to
compile it ourselves (not a big hurdle, but potentially a redundant
one which may prevent people who are away from their workstations from advising)
and (2) nobody can know if you are getting a unique warning.
Starting lilypond.exe 2.19.55 [Untitled]...
Processing `C:/Users/Knute/AppData/Local/Temp/frescobaldi-ctt4d4ig/tmp5l5e6d3u/document.ly'
Parsing...
Interpreting music...
C:/Users/Knute/AppData/Local/Temp/frescobaldi-ctt4d4ig/tmp5l5e6d3u/document.ly:13:7: warning: Two simultaneous mark events, junking this one
\mark \markup { \musicglyph #"scripts.dfermata" }
C:/Users/Knute/AppData/Local/Temp/frescobaldi-ctt4d4ig/tmp5l5e6d3u/document.ly:8:7: warning: Previous mark event here
\mark \markup { \musicglyph #"scripts.ufermata" }
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `./tmp-lilypond-hzkSsS'...
Converting to `document.pdf'...
Deleting `./tmp-lilypond-hzkSsS'...
Success: compilation successfully completed
Completed successfully in 1.1".
> http://lsr.di.unimi.it/LSR/Snippet?id=10
>
> \version "2.19.55"
>
> \score {
> \new GrandStaff <<
> \context Staff = one {
> c'1 \bar "|."
> \override Score.RehearsalMark.break-visibility = Oftentimes searching the web or specifically the LP archives will lead
> #begin-of-line-invisible
> \mark \markup { \musicglyph #"scripts.ufermata" }
> }
> \context Staff = two \with { \consists "Mark_engraver" } {
> c'1
> \override Staff.RehearsalMark.direction = #DOWN
> \mark \markup { \musicglyph #"scripts.dfermata" }
> }
> >>
> }
>
to past threads in which others have already encountered/debugged
the same problem.
I *strongly* suggest googling this issue yourself first - particularly
if there is a line or two in the log that start with "warning: ...".
--
Jeffery Shivers
jefferyshivers.com
soundcloud.com/jefferyshivers
[Prev in Thread] | Current Thread | [Next in Thread] |