Peter, I've forwarded this to bug-lilypond, because it is a bug. \contextStringTuning sets a context property for the FretBoards context. This creates a FretBoards context if one doesn't exist.
I'll investigate possible fixes.
In the meantime, since you're not using FretBoards in this layout, put the
following in your file before the score:
contextStringTuning =
#(define-music-function (parser location tuning chord)
(symbol? ly:music?)
(_ "Convert @{chord} to a string tuning stored in @code{tuning},
and set @code{stringTunings} of the current context to the
newly-defined tuning.
@{chord} must be in absolute pitches and should have the highest
string number (generally the lowest pitch) first. @code{tuning}
should be a string that will be converted to a symbol.")
(begin
(chord->tuning parser tuning chord)
#{
\set TabStaff.stringTunings = $(ly:parser-lookup parser tuning)
#}))
HTH,
Carl
------ Forwarded Message
From: Peter Crighton <petecrigh...@googlemail.com>
Date: Fri, 19 Aug 2011 06:58:05 -0600
To: LilyPond Mailing List <lilypond-user@gnu.org>
Conversation: Custom Tuning creating space beneath the first system
Subject: Custom Tuning creating space beneath the first system
Hi everybody.
When I create a custom tuning via \contextStringTuning there is some
extra vertical space (only) beneath the first system. When creating it
via \set TabStaff.stringTunings everything's perfect.
Is this a bug? Can it be fixed? I'd like to use \contextStringTuning,
because it's more compact.
--
Peter Crighton | (mainly) Progressive Rock musician based in
Mainz/Wiesbaden, Germany
http://www.petercrighton.de
------ End of Forwarded Message
customTuning.ly
Description: customTuning.ly
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
