lilypond-devel
[Top][All Lists]
Advanced

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

Re: [partcombine] honouring Voice context name


From: Flaming Hakama by Elaine
Subject: Re: [partcombine] honouring Voice context name
Date: Thu, 8 Jun 2017 13:25:11 -0700

From: David Kastrup <address@hidden>
To: Dan Eble <address@hidden>
Cc: Kieren MacMillan <address@hidden>, LilyPond Development
Team <address@hidden>
Bcc:
Date: Thu, 08 Jun 2017 12:03:04 +0200
Subject: Re: [partcombine] honouring Voice context name
Dan Eble <address@hidden> writes:

>> On Jun 7, 2017, at 09:34, Kieren MacMillan
>> <address@hidden> wrote:
>>
>> As a first step, I would offer that we should figure out how (if?)
>> the "one" context can be funnelled seamlessly into the "shared" and
>> "solo" contexts — as I see it, that's the main problem with lyrics
>> getting disconnected (etc.).
>
> If we’re going to ask that kind of question, let’s mention a more
> radical redesign.
>
> The context properties of a part, such as stem direction, need to
> change as the part’s relationship with other parts changes.  The
> current part combiner accomplishes this with a set of voices with
> fixed properties.  It slices the part into pieces and distributes them
> to the voice with the appropriate properties.
>
> Could it not leave the parts where they are (continuous parts in
> exactly one voice context per part) and change their context
> properties instead?

For shared/non-shared stems that would not seem to fit the current
logic.  Mind you: for piano music the rather rigid relation of stems and
slurs and noteheads with voices is a problem.

So changing this seems attractive but it would be a very fundamental
change.

--
David Kastrup


This hints back to the broader topic, of what are the intended uses of the
grand unified partcombine. (And whether or how many of these are captured
in existing tickets.)

While it is ideal to design to handle all cases including the most
complicated, does anyone typically combine piano parts?   What is the
musical use-case for this?

Or, putting it another way, how general is the issue of the "rigid relation
of stems and slurs and noteheads" within parts that people will want to
combine?  My hunch is that they don't much overlap:  if you are adding
rigid structures, what makes you think you should be able to automagically
combine something with it?


HTH,

David Elaine Alt
415 . 341 .4954                                           "*Confusion is
highly underrated*"
address@hidden
self-immolation.info
skype: flaming_hakama
Producer ~ Composer ~ Instrumentalist
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-


reply via email to

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