|
From: | Federico Bruni |
Subject: | convert-ly rule for \stringTuning |
Date: | Wed, 24 Apr 2013 22:27:50 +0200 |
\set TabStaff.stringTunings = #'(2 -3 -5 -8 -13 -20)
has been converted to:
\set TabStaff.stringTunings = #`(,(ly:make-pitch 0 1 NATURAL) ,(ly:make-pitch -1 5 NATURAL) ,(ly:make-pitch -1 4 NATURAL) ,(ly:make-pitch -1 2 NATURAL) ,(ly:make-pitch -2 6 NATURAL) ,(ly:make-pitch -2 2 NATURAL) )
I wonder why convert-ly has not managed to convert to a more user-friendly input, that is:
\set TabStaff.stringTunings = \stringTuning <e, b, e g a d'>
I'm not able to find the commit which introduced \stringTuning...
I found just this old commit:
commit 17f11c2f5ab963bfb07b7652b4860dc4dda5540a
Author: Carl Sorensen <address@hidden>
Date: Thu Dec 23 08:19:46 2010 -0700
The result of convert-ly was intended..
* python/convertrules.py
- Add rule to convert \set stringTunings = #'(...) to
\set stringTunings = #`((ly:make-pitch x y z)...)
with ly:make-pitch entries automatically calculated.
[Prev in Thread] | Current Thread | [Next in Thread] |