Here is a minimal (real) example of one measure that generates four warnings.
As you can see the rests in the third voice are simply invoked as "r4" while
the ones in the second voice are given explicit locations (which, again, I want
to do in this case). (I realize the notation convention here
Arle Lommel wrote Wednesday, December 19, 2012 9:41 AM
> For what it is worth, all of the conflicts seem to be between the voices
> "ornamentsVoice" and "rightVoice," both of which often have simultaneous
> rests. The rests from rightVoice are placed automatically (and correctly) in
> the prop
Actually, I spoke too soon. It looked like they were gone, but when I started
checking, my score was severely messed up in other ways by what I had done.
When I reverted and then tried again, the rest collision errors were back, so
the apparent absence was likely unrelated to the change in voice
Thanks Jim. Your example solved it for me. I thought I was using explicit
voices because I declared voices using a "\new Voice {}" construct, but I
hadn't named them explicitly, and that seems to be the difference. Now I am
seeing "real" warnings rather than these ones about rests and that helps
On Wed, Dec 19, 2012 at 08:44:29AM +0100, Arle Lommel wrote:
> Hi all, I am working on the same score that spawned discussion about stem
> lengths and now have another, hopefully less controversial, question.
>
> I keep getting warnings like the following when I run Lilypond:
>
> warning: cannot
Hi all, I am working on the same score that spawned discussion about stem
lengths and now have another, hopefully less controversial, question.
I keep getting warnings like the following when I run Lilypond:
warning: cannot resolve rest collision: rest direction not set
They appear from snippet
