Re: Diatonic Instruments (Mountain Dulcimer)
On 27 July 2011 03:21, Blake Thornton wrote: > > This looks like it will be PERFECT. But, it didn't work. I think the > problem is on my end, I can't seem to get the fret-letter-tablature-format > to work properly. Instead, I get an error: > Unbound Variable: fret-letter-tablature > > here's my output: > > > blake@valerie:~/Desktop/MusicBooks/Lilypond/Tex$ lilypond Dulcimer.ly > GNU LilyPond 2.12.3 > Processing `Dulcimer.ly' > Parsing... > Dulcimer.ly:17:23: error: GUILE signaled an error for the expression > beginning here > tablatureFormat = # > fret-letter-tablature-format > Unbound variable: fret-letter-tablature-format > Interpreting music... /usr/share/lilypond/2.12.3/scm/lily-library.scm:149:5: > In procedure apply in expression (process-procedure book paper ...): > /usr/share/lilypond/2.12.3/scm/lily-library.scm:149:5: Wrong type argument > in position 1: # > > > (I'm running ubuntu) You are using LilyPond version 2.12.3. Last stable version is 2.14.2. I suspect #fret-letter-tablature-format requires a recent version of LilyPond. Please consider updating. Cheers, Xavier -- Xavier Scheuer ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: MacOSX Lion
Hello, As mentionned here ( http://old.nabble.com/Error-opening-2.14.2-td32140373.html http://old.nabble.com/Error-opening-2.14.2-td32140373.html ) it is related to the included editor. For now, Lilypond works if you use : - terminal command - another text editor (JEdit with Lilypondtool, for instance) Philippe -- View this message in context: http://old.nabble.com/MacOSX-Lion-tp32145670p32145757.html Sent from the Gnu - Lilypond - User mailing list archive at Nabble.com. ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: Diatonic Instruments (Mountain Dulcimer)
Okay, I updated my version of lilypond and it is almost perfect. Thank
you!
Here is the main problem I see now. Lilypond favors the higher strings.
Thus, lilypond will try to put the melody on the first string (which is
the top string in the tablature). But, for dulcimer tablature, the
strings are generally numbered in reverse order. Thus, if we keep the
string labeled 1, 2, 3 then I want string 3 (the melody string) favored
instead of string 1. This can be solved by manually telling lilypond
which string to use, but that is a bit of a pain.
I put my snippet below to illustrate this. The first two measures are
what I want (and did by manually entering the string number), the next two
measures are what is generated automatically by lilypond.
Thanks!
Blake
\version "2.14.2"
notesA = \relative c' {
g4\1 a\2 d4\3 e\3
fis\3 g\3 a\3 b\3
}
notesB = \relative c' {
g4 a d e
fis g a b
}
<<
\new Staff {
\notesA
\notesB
}
\new TabStaff
\with {
stringTunings = #`(
,(ly:make-pitch -1 1 0)
,(ly:make-pitch -1 5 0)
,(ly:make-pitch 0 1 0)
)
%TabStaff.stringTunings = #'(14 11 7 2 19 )
fretLabels = #'(
"0" "0+" "1" "1+" "2" "3" "3+" "4" "4+" "5" "6" "6+"
"7" "7+" "8" "8+" "9" "10" "10+" "11" "11+" "12" "13" "13+"
"14" "14+" "15" "15+" "16" "17" "17+" "18" "18+" "19" "20" "20+")
tablatureFormat = #fret-letter-tablature-format
}
\new TabVoice {
\notesA
\notesB
}
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
Re: printed bars thickness inconsistencies
2011/7/26 Jean-Alexis Montignies : > It looks much better on screen (Preview.app: MacOS X system renderer) and on > Xerox Phaser 5400! > > Remains a little bit of smearing on the top of the staff, but this is much > less than before and could be some rounding/smoothing issue in the renderers. > More specifically, on screen, the horizontal edge of the barline rect looks > not smoothed, while the vertical edge is. Don't know enough about PS if this > can be controlled, or if it's really an issue (in any case minor). > > Thickness looks consistent now. Good, thanks for reporting! I hope that current output could be improved even more - if Finale can handle these things perfectly, then we should be able too :) See "Postscript printer errors with rounded barlines" thread on devel. > (extreme zoom, notice the round edge of the stall line on the right :) ) :P cheers, Janek ___ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
Slurs and PhrasingSlurs with simultaneous start or end
The automatic positioning of Slurs and PhrasingSlurs that both either
start or finish on the same note is not very good. See below. Commercial
scores that I have where this happens position the two slurs so that
they don't intersect or touch, as in the second bar where the
PhrasingSlur has been tweaked so that it doesn't intersect the slur:
\version "2.14.0"
offsetPhrasingSlurPos =
#(define-music-function (parser location offsets) (pair?)
#{
\once \override PhrasingSlur #'positions = #(lambda (grob)
`(,(+ (car $offsets) (cdar (ly:phrasingslur::calc-control-points
grob))) .
,(+ (cdr $offsets) (cdr (cadddr
(ly:phrasingslur::calc-control-points grob))
#})
\relative c'' {
\time 3/4
\slurDashed
c16\(( d) e f g8\) c,8 d16\(( c) b a\)
\offsetPhrasingSlurPos #'(0.3 . 0) c16\(( d) e f g8\) c,8
\offsetPhrasingSlurPos #'(0.3 . 0) d16\(( c) b a\)
}
Nick
<>___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
