Percent signs in ghostscript output files (i.e. those after
-sOutputFile) should be duplicated on the command line. It's not a
format string bug as I initially suspected, it's a documented feature.
http://ghostscript.com/doc/8.63/Use.htm#File_output
"Note: Since the % character is used to p
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
> I'm not top posting.
\version "2.16.2"
% If a clef is changed in retrograde it only prints the new clef
% It does not move the notes to their new locations on the staff
% All notes here are the same pitch but during clef changes it is printed
% incorrectly
\relative c' {
c1 % printed correc
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
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 you omit "\omit Rest" you get
"Connor Harris" wrote in message
news:loom.20130622t060235-...@post.gmane.org...
In 4/2 time, full-measure breve rests in the second voice on a staff
collide
can collide with notes in the first voice in the bottom space on the
staff.
This LilyPond file demonstrates three examples; the third, w
11 matches
Mail list logo
