Quoting Janek Warchoł :
I might try to convert one of the scores from partcombine to your approach.
You may want to take a look at
https://github.com/janek-warchol/warsztat-nutowy/tree/master/epifania/Cantate%20Domino%20%28Miskinis%29
which was created by my fellow choir members - crowd-engrav
Hi,
2013/6/22 Pavel Roskin :
> It looks like you created an alternative to partcombine! That's very
> impressive!
It's almost like implementing the partcombine logic in LilyPond itself :)
> But I wonder what limitations your approach has compared to
> partcombine.
as far as i know, the drawbac
Quoting Janek Warchoł :
2013/6/22 Pavel Roskin :
You forgot the source.
oops, sorry!
It looks like you created an alternative to partcombine! That's very
impressive! But I wonder what limitations your approach has compared
to partcombine.
It would be nice to have an "official" snip
2013/6/22 Pavel Roskin :
> Quoting Janek Warchoł :
>
>> That's quite a coincidence! I've been doing a similar thing recently.
>> You may be interested in looking at the attachment, which is the
>> solution i found for partcombining vocal stuff (the example is quite
>> artificial) - to obtain singl
Quoting Janek Warchoł :
That's quite a coincidence! I've been doing a similar thing recently.
You may be interested in looking at the attachment, which is the
solution i found for partcombining vocal stuff (the example is quite
artificial) - to obtain single voice parts, you'd simply have to us
Quoting David Kastrup :
Partly it might be the fault of having constructed a minimal example:
one that clearly shows the perceived symptom, but not really a
compelling motivation for wanting to change the behavior.
Perhaps some more info about the use case might help with prioritizing
this?
H
Eluze writes:
> Pavel Roskin wrote
>> If rests are omitted, they should not collide with anything. But they
>> do. Example:
>>
>> I get a warning:
>>
>> rests.ly:6:20: warning: cannot resolve rest collision: rest direction not
>> set
>>\new Voice {
>> r4 }
>
> if
f you omit "\omit Rest" you get exactly the same messages!
so I think polyphonic notation with \voiceXXX should be used.
Eluze
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Omitted-rests-should-not-collide-with-anything-tp147229p147246.html
Sent from the Bu
If rests are omitted, they should not collide with anything. But they
do. Example:
\version "2.17.20"
\score {
<<
\new Staff
<<
\new Voice { r4 }
\new Voice { \omit Rest r4 }
>>
>>
}
I get a warning:
rests.ly:6:20: warning: cannot resolve rest collision: rest dir
