Keith OHara writes:
> Urs Liska openlilylib.org> writes:
>
>> Keith wrote:
>> > I suggest looking over the existing partcombine bugs, and orchestral
>> > scores, to see what problems generally need solving.
>
>> If there's anything I can do to help (without understanding more than
>> basic Sch
Urs Liska openlilylib.org> writes:
> Keith wrote:
> > I suggest looking over the existing partcombine bugs, and orchestral
> > scores, to see what problems generally need solving.
> If there's anything I can do to help (without understanding more than
> basic Scheme and without any option to h
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
"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
On Sat, 29 Nov 2014 18:09:34 -0800, Dan Eble wrote:
On Nov 29, 2014, at 18:48 , Keith OHara wrote:
Oh, so you meant let the Scheme portion dictate to partcombine_iterator which
_input_ voice, as it iterates the music expression produced by \partcombine, to
use.
My reasoning probably need
On Nov 29, 2014, at 18:48 , Keith OHara wrote:
>
> Oh, so you meant let the Scheme portion dictate to partcombine_iterator which
> _input_ voice, as it iterates the music expression produced by \partcombine,
> to use.
My reasoning probably needs more clarification. The iterator takes sequence
On Nov 29, 2014, at 18:48 , Keith OHara wrote:
>
> On Sat, 29 Nov 2014 14:44:48 -0800, Dan Eble wrote:
>
>> This suggestion was motivated by recent work on cases in which both parts
>> are resting. If the desired action is to route only one of the voices to the
>> shared voice, the Scheme hal
On Sat, 29 Nov 2014 14:44:48 -0800, Dan Eble wrote:
On Nov 29, 2014, at 16:46 , Keith OHara wrote:
Dan Eble faithful.be> writes:
I would like the Scheme portion of the part
combiner to dictate the names of the voices to use at every moment.
Simply letting us specify the Voices _once_ fo
On Nov 29, 2014, at 16:46 , Keith OHara wrote:
>
> Dan Eble faithful.be> writes:
>
>> I would like the Scheme portion of the part
>> combiner to dictate the names of the voices to use at every moment.
>
> Simply letting us specify the Voices _once_ for the whole output of
> \partcombine would
Dan Eble faithful.be> writes:
> I would like to break the rigid link between the split states
> (apart, unisilence, etc.) and the names of the
> voices into which the Part_combine_iterator routes events.
The patch back at
http://lists.gnu.org/archive/html/lilypond-devel/2008-09/msg00079.html
To those familiar with the part combiner:
I would like to break the rigid link between the split states (apart,
unisilence, etc.) and the names of the voices into which the
Part_combine_iterator routes events. I would like the Scheme portion of the
part combiner to dictate the names of the voi
13 matches
Mail list logo
