The brackets end in the correct place, according to Elaine Gould - they should 
end after the "notehead".  The collision with the arpeggio is a bug.

--
Phil Holmes


  ----- Original Message ----- 
  From: Simon Bailey 
  To: lilypond-user 
  Sent: Thursday, August 22, 2013 10:21 AM
  Subject: strange octavation behaviour


  hi,


  consider the following snippet:


  --------
  \version "2.17.20"
  \new PianoStaff <<
    \new Staff \relative c'''' {
      \ottava #1 <g c e>4.\arpeggio b8 a4 f \ottava #0 |
      R1
      \ottava #1 <g c e>4.\arpeggio b8 a4 f \ottava #0 |
    }
    \new Staff \relative c'' {
      \set PianoStaff.connectArpeggios = ##t
      \ottava #1 <e g c>2\arpeggio \ottava #0 r2 |
      R1
      \ottava #1 <e g c>2\arpeggio r \ottava #0 |
    }
  >>
  --------


  when compiled, it produces the output in the attached PNG.


  the first bar is the correct notation (i.e. the ottava bracket should stop 
before the rest), but the ottava bracket is pushed into the arpeggio and ends 
directly after the half note. in the third bar, the ottava bracket starts in 
the correct place, but is somewhat too long. (actually i think it's too short 
-- shouldn't the octavation spanner go as far as the note/rest _sounds_?).


  setting minimum-length just exacerbates the problem in the first bar by 
shifting the "8va" further to the left…


  ideal behaviour:
  - ottava brackets should be vertically aligned
  - ottava brackets should be as long as the duration of the note[s]


  is there any way to magically create this behaviour?


  thanks, regards,
  sb


  --
  Oompa Loompa of Science
  +43 699 190 631 25




------------------------------------------------------------------------------


  _______________________________________________
  lilypond-user mailing list
  [email protected]
  https://lists.gnu.org/mailman/listinfo/lilypond-user

<<ottavabug.png>>

_______________________________________________
lilypond-user mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/lilypond-user

Reply via email to