Re: Bug: instrumentName is not being vertically centered when using template 'piano centered dynamics'
I think Wilbert has already provided a very accurate description of the problem and its solution (to just move the Dynamics context outside the PianoStaff). I can add a sentence in the section on Instrument names. However, I also agree with Wilbert's It would be nice ..., so an ambitious bug meister could file it as a low-priority feature request. A very similar kind of problem was fixed in 2.11.23, see http://lists.gnu.org/archive/html/lilypond-user/2007-06/msg00064.html /Mats Graham Percival wrote: Thanks for the report -- but is this a report about the docs, or a bug in the program? If it's something about the docs, please note that the templates are generated from LSR; they should be fixed in there. If it's a bug in the program, please create a minimal example. Cheers, - Graham On Thu, 31 Jan 2008 17:44:05 + (UTC) Moritz Baumann [EMAIL PROTECTED] wrote: I'm not top posting. Example: \version 2.11.23 upper = \relative c'' { \clef treble \key c \major \time 4/4 a b c d } lower = \relative c { \clef bass \key c \major \time 4/4 a2 c } dynamics = { s2\fff\ s4 s\!\pp } pedal = { s2\sustainDown s2\sustainUp } \score { \new PianoStaff \set PianoStaff.instrumentName = Piano \new Staff = upper \upper \new Dynamics = dynamics \dynamics \new Staff = lower \clef bass \lower \new Dynamics = pedal \pedal \layout { \context { \type Engraver_group \name Dynamics \alias Voice % So that \cresc works, for example. \consists Output_property_engraver \override VerticalAxisGroup #'minimum-Y-extent = #'(-1 . 1) \override DynamicLineSpanner #'Y-offset = #0 pedalSustainStrings = #'(Ped. *Ped. *) pedalUnaCordaStrings = #'(una corda tre corde) \consists Piano_pedal_engraver \consists Script_engraver \consists Dynamic_engraver \consists Text_engraver \override TextScript #'font-size = #2 \override TextScript #'font-shape = #'italic \consists Skip_event_swallow_translator \consists Axis_group_engraver } \context { \PianoStaff \accepts Dynamics } } } \score { \new PianoStaff \new Staff = upper \upper \dynamics \new Staff = lower \lower \dynamics \new Dynamics = pedal \pedal \midi { \context { \type Performer_group \name Dynamics \consists Piano_pedal_performer } \context { \PianoStaff \accepts Dynamics } } } ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: instrumentName is not being vertically centered when using template 'piano centered dynamics'
Graham Percival wrote: You hear that, Valentin? Be ambitious. :) This is probably related to Trevor's recent email to -devel about adding Dynamics to performer-init.ly. No! You will see exactly the same problem if you include a Lyrics or a FiguredBass or a ChordNames or whatever context in a PianoStaff or GrandStaff. /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: instrumentName is not being vertically centered when using template 'piano centered dynamics'
You hear that, Valentin? Be ambitious. :) This is probably related to Trevor's recent email to -devel about adding Dynamics to performer-init.ly. But since it involves piano and I'm strictly strings-only, (and since I'm not Bug Meister any more) I happily haven't looked at any of these emails. Cheers, - Graham On Mon, 04 Feb 2008 14:54:32 +0100 Mats Bengtsson [EMAIL PROTECTED] wrote: I think Wilbert has already provided a very accurate description of the problem and its solution (to just move the Dynamics context outside the PianoStaff). I can add a sentence in the section on Instrument names. However, I also agree with Wilbert's It would be nice ..., so an ambitious bug meister could file it as a low-priority feature request. A very similar kind of problem was fixed in 2.11.23, see http://lists.gnu.org/archive/html/lilypond-user/2007-06/msg00064.html /Mats Graham Percival wrote: Thanks for the report -- but is this a report about the docs, or a bug in the program? If it's something about the docs, please note that the templates are generated from LSR; they should be fixed in there. If it's a bug in the program, please create a minimal example. Cheers, - Graham On Thu, 31 Jan 2008 17:44:05 + (UTC) Moritz Baumann [EMAIL PROTECTED] wrote: I'm not top posting. Example: \version 2.11.23 upper = \relative c'' { \clef treble \key c \major \time 4/4 a b c d } lower = \relative c { \clef bass \key c \major \time 4/4 a2 c } dynamics = { s2\fff\ s4 s\!\pp } pedal = { s2\sustainDown s2\sustainUp } \score { \new PianoStaff \set PianoStaff.instrumentName = Piano \new Staff = upper \upper \new Dynamics = dynamics \dynamics \new Staff = lower \clef bass \lower \new Dynamics = pedal \pedal \layout { \context { \type Engraver_group \name Dynamics \alias Voice % So that \cresc works, for example. \consists Output_property_engraver \override VerticalAxisGroup #'minimum-Y-extent = #'(-1 . 1) \override DynamicLineSpanner #'Y-offset = #0 pedalSustainStrings = #'(Ped. *Ped. *) pedalUnaCordaStrings = #'(una corda tre corde) \consists Piano_pedal_engraver \consists Script_engraver \consists Dynamic_engraver \consists Text_engraver \override TextScript #'font-size = #2 \override TextScript #'font-shape = #'italic \consists Skip_event_swallow_translator \consists Axis_group_engraver } \context { \PianoStaff \accepts Dynamics } } } \score { \new PianoStaff \new Staff = upper \upper \dynamics \new Staff = lower \lower \dynamics \new Dynamics = pedal \pedal \midi { \context { \type Performer_group \name Dynamics \consists Piano_pedal_performer } \context { \PianoStaff \accepts Dynamics } } } ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: unpacking .sh file
On Ubuntu, the simplest method is to right-click, go into properties and under the permissions tab click 'enable execution'. The file can then be double-clicked to run the install script. I don't know if Kubuntu is set up exactly the same, though. Andrew On Feb 4, 2008 4:38 PM, Jack K Blackhall [EMAIL PROTECTED] wrote: I am pretty new ot linux and am using Kubuntu. I have downloaded the binary file but can't figure out how to compile and run it. Can you help? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
unpacking .sh file
I am pretty new ot linux and am using Kubuntu. I have downloaded the binary file but can't figure out how to compile and run it. Can you help? ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Bug: score-final mark mangles score-final tuplet bracket
On Feb 4, 2008 7:10 PM, Trevor Bača [EMAIL PROTECTED] wrote: Hi Valentin, Could you please consider this one for the tracker? It's quite specific thing ever, but highly reproducible (and quite irritating). === The score-final mark badly mangles the score-final tuplet bracket in the snippet below: %%% BEGIN MANGLE %%% \version 2.11.34 \new Staff { \set tupletFullLength = ##t \time 1/8 \times 2/3 { c'16 c'16 c'16 } \times 2/3 { c'16 c'16 c'16 } \times 2/3 { c'16 c'16 c'16 } \override Score.RehearsalMark #'break-visibility = ##(#t #t #t) \override Score.RehearsalMark #'direction = #down \override Score.RehearsalMark #'break-align-symbol = #'clef \override Score.RehearsalMark #'self-alignment-X = #right \mark Composed Feb 2007 - Feb 2008 } %%% END %%% FWIW, you do seem to need all five settings above to induce the problem. (Actually, mark direction can be either up or down, but appears more clearly with the mark set down.) Oops. Here's a pic of the resulting output. -- Trevor Bača [EMAIL PROTECTED] attachment: mangled-bracket.png___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Bug: score-final mark mangles score-final tuplet bracket
Hi Valentin, Could you please consider this one for the tracker? It's quite specific thing ever, but highly reproducible (and quite irritating). === The score-final mark badly mangles the score-final tuplet bracket in the snippet below: %%% BEGIN MANGLE %%% \version 2.11.34 \new Staff { \set tupletFullLength = ##t \time 1/8 \times 2/3 { c'16 c'16 c'16 } \times 2/3 { c'16 c'16 c'16 } \times 2/3 { c'16 c'16 c'16 } \override Score.RehearsalMark #'break-visibility = ##(#t #t #t) \override Score.RehearsalMark #'direction = #down \override Score.RehearsalMark #'break-align-symbol = #'clef \override Score.RehearsalMark #'self-alignment-X = #right \mark Composed Feb 2007 - Feb 2008 } %%% END %%% FWIW, you do seem to need all five settings above to induce the problem. (Actually, mark direction can be either up or down, but appears more clearly with the mark set down.) -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: regressions: lyrics-after-grace.ly
I don't think this is necessary; if it works for aftergrace, it'll work for grace as well. If it would be useful to add an extra test, I'm sure that Han-Wen will do it. Cheers, - Graham On Sun, 3 Feb 2008 17:05:17 -0600 Stan Sanderson [EMAIL PROTECTED] wrote: 2.11.38 regression/lyrics-after-grace.ly (confusing?) Lyrics are ignored for aftergrace notes. The test verifies the statement; however, the rendered example appears to be a normal grace note tied to the second c. Only the fact that the grace note is closer to the first c than the second gives it away. Perhaps the test could be expanded (or a second test added) to demonstrate that Lyrics are ignored for grace notes, including aftergrace notes. Stan ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond