Re: Kneed beams and changes of staff

[Kieren MacMillan]

arg… Here’s the snippet:

%%%  SNIPPET BEGINS
\version "2.19"
\language "english"

examples = {
  \tuplet 5/4 { c''32[ 32 64 64 32 32] }
  \tuplet 5/4 { e'''32[ 32 64 g64 32 32] }
}

\score {
  \examples
}
%%%  SNIPPET ENDS

On Dec 1, 2015, at 10:34 AM, Kieren MacMillan <address@hidden> wrote:

> Hi Gilberto,
> 
>> I would need one of those automagical ways
> 
> Even if you weren’t dealing with algorithmic music, an automagic way would be 
> much better…
> 
>> What surprises me about the default look is how confusing it actually is!
> 
> True! If you look at the following [even simpler] snippet, it’s clear that 
> things are fine when un-kneed, but go wonky when kneed. It looks like the 
> algorithm says “keep all beams at their highest possible position” instead of 
> [what you want, which is:] “beam the 32nds together across the whole group, 
> and then add the 64th beam(s) where most appropriate”.
> 
> I’m in no way certain (a) what the current algorithm actually is/does, and 
> (b) whether improving it is possible/reasonable/feasible. I’m just “+1”-ing 
> you here, having noticed this for the first time because of your post.
> 
> Here’s hoping you find a good solution!
> Kieren.
________________________________

Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: address@hidden