Issue 836 in lilypond: Enhancement: output-suffix as a (Score) context property
Status: Accepted
Owner: v.villenave
Labels: Type-Enhancement Priority-Low
New issue 836 by v.villenave: Enhancement: output-suffix as a (Score)
context property
http://code.google.com/p/lilypond/issues/detail?id=836
Ian has posted this idea, related to issue 404 and issue 714 :
http://lists.gnu.org/archive/html/lilypond-devel/2009-09/msg00411.html
It would be nice if one could tweak the output filename
\book {
\new Score \with {output-prefix = VocalScore}
{
\vocalMusic
}
}
Or even:
\book {
\score \with {output-prefix = PianoVocalScore}
...
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Enhancement request: Define output-suffix as a configurable context property.
On Thu, Sep 17, 2009 at 11:26 PM, Ian Hulin i...@hulin.org.uk wrote: Valentin, could we have a tracker, please? Here you go: http://code.google.com/p/lilypond/issues/detail?id=836 Cheers, Valentin ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ottava too far from clef in \clef F^8
This is weird! For alto clefs, \clef C^8, the '8' is placed just on
top of the stave, but for bass clefs it's separated for some strange
reason. For octava indications below the clef, the placement is OK for
all the clef symbols. I used \override Score.Clef #'stencil =
#(make-stencil-boxer 0 0 ly:clef::print) to check the bounding box of
the clef symbols, but it seems correct so I have no idea why this happens.
The problem existed already in version 2.10, so it's not related to the
new spacing implementation in 2.12 or 2.13.
Extended test case:
\score {
\override Score.Clef #'stencil = #(make-stencil-boxer 0 0 ly:clef::print)
\new Staff { \clef G^8 g''1 }
\new Staff { \clef F^8 c'1 }
\new Staff { \clef C^8 c''1 }
\new Staff { \clef G_8 g1 }
\new Staff { \clef F_8 c,1 }
\new Staff { \clef C_8 c1 }
\layout{ragged-right = ##t }
}
/Mats
Peter Chubb wrote:
Hi,
The `8' is too far from the F clef with Lilypond 2.12.2 --
from the score, one cannot tell whether it belongs to the bass or
treble staves.
\version 2.12.2
\score {
\new Staff { g'1 }
\new Staff { \clef F^8 c'1 }
}
Produces this:
Peter C
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
--
=
Mats Bengtsson
Signal Processing
School of Electrical Engineering
Royal Institute of Technology (KTH)
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: mats.bengts...@ee.kth.se
WWW: http://www.s3.kth.se/~mabe
=
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Ottava too far from clef in \clef F^8
Am Freitag, 18. September 2009 14:07:37 schrieb Mats Bengtsson:
This is weird! For alto clefs, \clef C^8, the '8' is placed just on
top of the stave,
This looks very weird for a mid-line \clef soprano^8, since the (smaller)
clef on the lowest staff line will not even touch the middle staff line, but
the
8 is printed above the top staff line...
\score {
\override Score.Clef #'stencil = #(make-stencil-boxer 0 0 ly:clef::print)
\override Score.OctavateEight #'stencil = #(make-stencil-boxer 0 0
ly:text-interface::print)
\new Staff { \clef tenor_8 c1 \clef soprano^8 g''1 }
\layout{ragged-right = ##t }
}
but for bass clefs it's separated for some strange
reason. For octava indications below the clef, the placement is OK for
all the clef symbols.
Well, a mid-line \clef tenor_8 has a similar problem as soprano^8,
although the space is not that large.
Also \clef bass_8 has a very large space between the clef and the 8...
See the attached example with different clef changed in mid-line.
I used \override Score.Clef #'stencil =
#(make-stencil-boxer 0 0 ly:clef::print) to check the bounding box of
the clef symbols, but it seems correct so I have no idea why this happens.
The bounding box of the OctavationEight are also correct...
Another think about the octavation is the horizontal alignment of the number:
For the treble_8 and the bass^8, the 8 is too far to the right for my
taste (it is centered, which does not look good with the clef shape!).
Cheers,
Reinhold
--
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
\pointAndClickOff
\score {
\override Score.Clef #'stencil = #(make-stencil-boxer 0 0 ly:clef::print)
\override Score.OctavateEight #'stencil = #(make-stencil-boxer 0 0 ly:text-interface::print)
\new Staff { \clef G^8 g''1 \clef F^8 c'1 }
\new Staff { \clef F^8 c'1 \clef C^8 c''1 }
\new Staff { \clef C^8 c''1 \clef G_8 g1 }
\new Staff { \clef G_8 g1 \clef F_8 c,1 }
\new Staff { \clef F_8 c,1 \clef C_8 c1 }
% \new Staff { \clef C_8 c1 \clef alto_8 g1 }
\new Staff { \clef alto_8 c1 \clef soprano_8 g1 }
\new Staff { \clef soprano_8 c1 \clef tenor_8 g1 }
\new Staff { \clef tenor_8 c1 \clef soprano^8 g''1 }
\new Staff { \clef soprano^8 c''1 \clef alto^8 g''1 }
\new Staff { \clef alto^8 c''1 \clef tenor^8 g''1 }
\new Staff { \clef tenor^8 c''1 \clef G^8 g''1 }
\layout{ragged-right = ##t }
}
clef.pdf
Description: Adobe PDF document
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: [frogs] Enhancement request: Define output-suffix as a configurable context property.
On 9/17/09 3:26 PM, Ian Hulin i...@hulin.org.uk wrote: Also, could anyone who could give me a steer into defining a new context property give me a pointer as to where to look in the code for examples where this is implemented for existing properties? I'd really like to have access to an exemplar. At the moment I'm struggling with issues like: Do I need to define the property and access routines C++, i.e. add the new property, accessor routine prototypes and code in score.hh and score.cc, with scheme bindings in score-scheme.cc. However, looking at the code it looks like the Score class is relatively light and only has properties like music_, input_location_ header_, defs_ user_key_ and error_found_. So lilypond properties which can be applied to \score blocks, like autoAccidentals must use a different mechanism. My approach was to look in the IR for context properties. Then I picked one (chordChanges) and did git grep for it. It turned up scm/define-context-properties.scm which is where all of the context properties are defined. Do you need more than this? HTH, Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
