lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Fix temporary polyphony "for good" (was 'Re: Ties in complex polypho


From: David Kastrup
Subject: Re: Fix temporary polyphony "for good" (was 'Re: Ties in complex polyphony')
Date: Sat, 19 Oct 2013 15:35:41 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Kieren MacMillan <address@hidden> writes:

> Dear 'Pond (especially David K),
>
>> I'd like to tie the common notes below:
>> {
>> <<{a1~}\\{f4 e}>>
>> a1
>> }
>> 
>> But I'm not sure I'm doing it correctly.
>
> As this is a repeating, repetitive, periodic, cyclical, seasonal,
> perennial, regular, frequent, favo(u)rite, and recurrent trope on this
> list… Is it not possible — once and for all — to solve the "temporary
> polyphony" issue?

If it was that easy to do, don't you think this would already have been
done?

What do you think the groundwork of issues 3553, 3303, 3292, and
particularly 3225 is supposed to be for?  Have you read the issue
description of issue 3225?

But to do this properly will likely require a different translator group
with a different way of routing its grobs than Engraver_group does.

> I believe the consensus, at one point, was that it would be best if Lilypond 
> (by default) interpreted
>
>     << a \\ b >>
>
> as
>
>   << { \voiceOne a } \\ \new Voice = "2" { \voiceTwo b } >> \oneVoice
>
> The only points of debate were:
> 1. Should the new voice be explicitly named, and if so what name?; and
> 2. Is the parser/lexer/whatever in any shape to easily handle this
> "expansion" (if I recall correctly, Han-Wen suggested it might be
> difficult).

I think it's more inconsistent than difficult.  With the current setup,
at least you can pick your main Voice to be named "1" or "2" and then
have the respective split voice fall into place.

> What say ye?
> If I were a better programmer, with more time, I would try this myself
> — but I'm quite happy (as always) to pay for someone else to do it, if
> the bounty isn't too high.

I am hauling this one in quite slowly.  Of course, for the last haul the
bounty won't be too high and you'll find a lot of people able or willing
to put the last piece into place for a small fee.  But the code base is
not yet where this would be trivial to do.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]