Hi Dan and Keith,
I just wanted to let you know that I'm following your discussion with
interest, although I don't understand most of it. Any improvements in
the partcombiner are highly welcome and appreciated.
If there's anything I can do to help (without understanding more than
basic Schem
On Sun, 30 Nov 2014 13:46:35 -0800, Dan Eble wrote:
I have a question. If the Scheme code produces something like (‘apart “one”
“two”) with “one” and “two” being the chosen output voices for the input parts
at the moment, would it make sense to write those decisions back to the input
parts
On Nov 30, 2014, at 01:17 , Keith OHara wrote:
>
> If \partcombine can only assume part of the responsibility for routing
> decisions, though, I seems cleaner to enhance the set of split-state tags to
> completely describe the results of \partcombine's analysis, rather than tell
> part_combine
>>Internal Error (overlap) in timesig.C44:
>> Winding number did not return to 0 when x=415.356
>>Internal Error (overlap) in scripts.reverseturn:
>> Fixup error 2 in MergeIntersections.
>>Internal Error (overlap) in clefs.G:
>> monotonic is both needed and unneeded
>>
On 30-11-2014 13:09, Werner LEMBERG wrote:
Because I must consider it a considerable bug, that the Lilypond
build system reports an error, where not even a warning is really
explicable. Returning a wrong errorlevel in the middle of a build
process should never happen...
Well, the rejection of n
> Because I must consider it a considerable bug, that the Lilypond
> build system reports an error, where not even a warning is really
> explicable. Returning a wrong errorlevel in the middle of a build
> process should never happen...
Well, the rejection of newer FontForge versions *is* founded
>> Masamichi HOSODA writes:
>>
Masamichi HOSODA writes:
> In mingw, lilypond crashes as follows.
> Does someone know this reason?
>
> ```
> C:\tmp\lilypond-2.19.16-0.mingw\$_OUTDIR\usr\bin>type test.ly
> { c d e f g a b }
>
> C:\tmp\lilypond-2.19.16-0
"Keith OHara" writes:
> I am eager for either nameable outputs from \partcombine, or
> VoiceGroup, in LilyPond so we can have a stable and functional
> \partcombineUp/Down.
VoiceGroup won't help with merging multiple outputs into one context.
We'd need something like
\context Voice = "unisilen
Werner LEMBERG writes:
> I'm curious: Is there anything new w.r.t. guile 2.0? We had a lot of
> talk, but recently there was only silence... In particular, is
> version 2.0.11 good enough for lilypond?
I differ with "we had a lot of talk". There was a lot of talk about how
important it would
I'm curious: Is there anything new w.r.t. guile 2.0? We had a lot of
talk, but recently there was only silence... In particular, is
version 2.0.11 good enough for lilypond?
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://li
10 matches
Mail list logo
