RE: Kneed beams and changes of staff

I reported this at http://lilypond.1069038.n5.nabble.com/Kneed-beam-and-subdivisions-td184473.html and I also offered a 30 EUR bounty to whomever fix this. -- View this message in context: http://lilypond.1069038.n5.nabble.com/Kneed-beams-and-changes-of-staff-tp184339p184553.html Sent from the

RE: Kneed beams and changes of staff

Hi all, I got Elaine Gould's /Behind Bars/ from my library today and this is what she has to say about this issue here (pp. 316--317): I think the key is

RE: Kneed beams and changes of staff

One more thing: this problem is related to the kneed beams behaviour only and is not affected by changes of staff or \autochange, see: \autochange { \override Score.Beam.auto-knee-gap = #3 \tuplet 5/4 {g''32[e'' g''64 d a,32 gis]} } { \override Score.Beam.auto-knee-gap = #1 \tuplet 5/4

RE: Kneed beams and changes of staff

Mark Stephen Mrotek wrote > A rather tedious, yet precise method, is: > > \once \set stemRightBeamCount = #x > \once \set stemLeftBeamCount = #x One one more thing, this method actually does not work. Think like this: the problem isn't the number of beams for each note (these are correct) but

Re: Kneed beams and changes of staff

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

Re: Kneed beams and changes of staff

Hi Kieren, Kieren MacMillan wrote > There are almost certainly other [more automagic] ways… > But have you looked at stemLeftBeamCount and stemRightBeamCount? I have looked at them, but unfortunately I would need one of those automagical ways (I am dealing with algorithmic music and I manually

Re: Kneed beams and changes of staff

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

Re: Kneed beams and changes of staff

Hi Kieren, Kieren MacMillan wrote > 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. Your example shows the problem very clearly indeed. > I’m in no way certain (a) what the current algorithm actually is/does,

RE: Kneed beams and changes of staff

Gilberto, A rather tedious, yet precise method, is: \once \set stemRightBeamCount = #x \once \set stemLeftBeamCount = #x Mark -Original Message- From: lilypond-user-bounces+carsonmark=ca.rr@gnu.org [mailto:lilypond-user-bounces+carsonmark=ca.rr@gnu.org] On Behalf Of Gilberto

RE: Kneed beams and changes of staff

Hi Mark, Mark Stephen Mrotek wrote > A rather tedious, yet precise method, is: > > \once \set stemRightBeamCount = #x > \once \set stemLeftBeamCount = #x This is what Kieren already recommended me in this thread, but it's unfortunately not really possible in my case (and even if I could, I

Re: Kneed beams and changes of staff

Hi Gilberto, > Does anyone here know how can I achieve the look of the red beams There are almost certainly other [more automagic] ways… But have you looked at stemLeftBeamCount and stemRightBeamCount? Hope this helps! Kieren. Kieren MacMillan, composer ‣