[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Script and staff-pading question
From: |
Mats Bengtsson |
Subject: |
Re: Script and staff-pading question |
Date: |
Thu, 12 Apr 2007 12:41:54 +0200 |
User-agent: |
Thunderbird 1.5.0.10 (X11/20070221) |
As you can notice at the chart of all available scripts in the section
on "Articulation",
some articulations stay close to the note head, whereas others always
are typeset
above/below the stave. The staff-padding property is only in effect for the
articulations that always are typeset outside the stave, such as
staccatissimo,
stopped, turn and lost of others. Once you think of it, this design
choice in
LilyPond makes sense.
The obvious follow-up question is how LilyPond determines which
articulations
should follow the note head into the stave and which should stay outside.
The answer can be found in the initalization file scm/script.scm, where
the articulations that should follow the note head have the property
quantize-position set.
/Mats
Dmytro O. Redchuk wrote:
Hello,
manual says that articultaions' position can be controlled by Script's
parameters, but i can not manage to do so.
Please, take a look:
% -----------------------------------------------------
\version "2.10.20"
\relative c' {
\stemDown
%
% This "\override" works:
\override Script #'padding = #1.5
%
c-> d-> e-> f-> g-> a-> b-> c->
%
% while this one -- doesn't:
\override Script #'staff-padding = #3
%
c,-> d-> e-> f-> g-> a-> b-> c->
}
% -----------------------------------------------------
The second "\override" does nothing -- it but should?
(This is somewhat related to my previous question -- regarding
staff-padding and TextScript under slurred note, i guess)
--
=============================================
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: address@hidden
WWW: http://www.s3.kth.se/~mabe
=============================================