Yes, I see that now with the slurs -- the following line seems to fix it:
\set Staff.quotedEventTypes = #'(note-event rest-event slur-event)
(posted here for posterity)
However, I don't see anything relevant to the unfolding and polyphony issues
... could you shed some light on this?
--KR
On Tu
2008/3/18, Mats Bengtsson <[EMAIL PROTECTED]>:
> See the documentation of quotedEventTypes at
>
> http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Quoting-other-voices#Quoting-other-voices
> It's not a bug but a feature ;-)
Oh yes, I should have checked it. (Plus I remember having
tran
See the documentation of quotedEventTypes at
http://lilypond.org/doc/v2.11/Documentation/user/lilypond/Quoting-other-voices#Quoting-other-voices
It's not a bug but a feature ;-)
/Mats
Valentin Villenave wrote:
2008/3/17, Koy Rehme <[EMAIL PROTECTED]>:
I've discovered a set of bugs rel
2008/3/17, Koy Rehme <[EMAIL PROTECTED]>:
> I've discovered a set of bugs relating to the cue system.
Honestly, I don't know if these are actually bugs.
- LilyPond's support for cue notes is still somehow limited.
- Your reports were written with an old version of LilyPond (the
syntax has evolve
> I'm not top posting.
I've discovered a set of bugs relating to the cue system. I'll
be the first to admit that I'm experienced with lilypond -- this
could be from ignorance more than anything else
The following:
\version "2.10.33"
cues = \relative c'' {
R1 | << { e4( f) } \\ { c2 } >> c2
}
