Re: Problem with Chord Names
Hi Rick, all,
I'm not sure I follow this (I have only been playing around with
lilypond for a few weeks), does this put the chord names over all of the
staves, or can it put chord names over just certain staffs and the only
in sections where I want to have chord names.
What I gave you puts the chords above everything, which is what I use for my
scores. It's most convenient if you're directing.
For the part extractions, I include the chords in every part, as it gives the
players a solid sense of where they are.
But you can choose to do it differently.
I would also encourage you to use relative octave mode (see the manual, it
saves you all that octave ' and , typing), as well as transposition, so you
can enter all the horn parts the way they sound, not having to transpose in
your head.
That's why I never got far on the tenor saxophone... I can't stand thinking
C and hearing Bb.
This score does all the required stuff and then some:
\version 1.6.6
\header {
title = Song
subtitle = (tune)
composer = Me
meter = moderato
piece = Swing
}
\include paper16.ly
\include english.ly
Some macros %%%
sl = {
\property Voice.NoteHead \override #'style = #'slash
\property Voice.Stem \override #'length = #0 }
nsl = {
\property Voice.NoteHead \revert #'style
\property Voice.Stem \revert #'length }
cr = \property Voice.NoteHead \override #'style = #'cross
ncr = \property Voice.NoteHead \revert #'style
Keys'n'thangs %
global = \notes {
\time 4/4
}
Concert = \notes \key c \major
Bb = \notes \key d \major
Eb = \notes \key a \major
% Horns
% -- Trumpet --
trpt = \notes {
c''1 c'' c''
}
trumpet = {
\global
\property Staff.instrument = #Trumpet
\clef treble
\Bb
\context Staff
\trpt
}
% -- Alto Saxophone --
alto = \notes {
c''1 c'' c''
}
altosax = {
\global
\property Staff.instrument = #Alto Sax
\clef treble
\Eb
\context Staff
\alto
}
% -- Baritone Saxophone --
bari = \notes {
c''1 c'' \sl b'4^Solo b' b' b' \nsl
}
bariharmony = \chords { s1 s d2:maj e:m.7 }
barisax = {
\global
\property Staff.instrument = #Bari Sax
\clef treble
\Eb
\context Staff
\bari
}
% -- Trombone --
tbone = \notes {
c1 c c
}
trombone = {
\global
\property Staff.instrument = #Trombone
\clef bass
\Concert
\context Staff
\tbone
}
% Rhythm Section #
% -- Guitar --
gtr = \notes {
c''1 \sl b'4 b' b' b' \nsl c''1
}
gtrharmony = \chords {
s1 c2:min.7+ d2:maj.9
}
guitar = {
\global
\property Staff.instrument = #Guitar
\clef treble
\Concert
\context Staff
\gtr
}
%% -- Piano --
rhUpper = \notes {
\voiceOne
c''1 c'' c''
}
rhLower = \notes {
\voiceTwo
e'1 e' e'
}
PianoRH = {
\clef treble
\Concert
\global
\property Staff.instrument = #Piano
\property Staff.instr = #Piano
\property Staff.midiInstrument = acoustic grand
\context Staff
\context Voice = one \rhUpper
\context Voice = two \rhLower
}
lhUpper = \notes {
\voiceOne
g1 g g
}
lhLower = \notes {
\voiceTwo
c1 c c
}
PianoLH = {
\clef bass
\Concert
\global
\property Staff.midiInstrument = acoustic grand
\context Staff
\context Voice = one \lhUpper
\context Voice = two \lhLower
}
% -- Bass Guitar --
bass = \notes {
c1 c c
}
bass = {
\global
\property Staff.instrument = #Bass
\clef bass
\Concert
\context Staff
\bass
}
% -- Drums --
\include drumpitch-init.ly
up = \notes {
hh4 hh4 sn hh4 hh4 sn hh4 hh4 sn hh4 hh4 sn
hh4 hh4 sn hh4 hh4 sn
}
down = \notes {
bd4 s bd s bd s bd s bd s bd s
}
drums = {
\global
\property Staff.instrument = #Drums
\clef percussion
\context Staff
\context Voice = first { \voiceOne \up }
\context Voice = second { \voiceTwo \down }
}
% It All Goes Together Here %%
\score {
\context StaffGroup = horns
\context Staff = trumpet \trumpet
\context Staff = altosax \altosax
\context ChordNames = barichords \bariharmony
\context Staff = barisax \barisax
\context Staff = trombone \trombone
\context
Re: Problem with Chord Names
[EMAIL PROTECTED] writes:
That's why I never got far on the tenor saxophone... I can't stand thinking
C and hearing Bb.
trumpet = {
\Bb
}
% -- Alto Saxophone --
alto = \notes {
c''1 c'' c''
}
altosax = {
\Eb
}
trombone = {
\Concert
doesn't this template miss a few \transposes?
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Fwd: Re: Problem with Chord Names
-- Weitergeleitete Nachricht -- Subject: Re: Problem with Chord Names Date: Mon, 7 Jul 2003 11:15:23 +0200 From: Amelie Zapf [EMAIL PROTECTED] To: [EMAIL PROTECTED] Hi Han-Wen, Rick, all, doesn't this template miss a few \transposes? yes. I just gave that as an additional suggestion. I was too lazy to put that in as well. Amy --- ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: etf2ly wows
On Sun, 06 Jul 2003 08:20:21 +0300 Aaron [EMAIL PROTECTED] wrote: I am experiencing some problems with etf2ly. When I convert from etf to ly the key changes??? Is there something I can do about this?? Either in Finale before I convert or in etf2ly?? I'm not certain how up-to-date etf2ly is -- what version of Finale file are you trying to convert? I suspect that you might even save time by simply re-typing the file into lilypond from scratch, rather than trying to make etf2ly work. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: help required in input/test
On Fri, 04 Jul 2003 18:31:03 +0200 Ferenc Wagner [EMAIL PROTECTED] wrote: Graham Percival [EMAIL PROTECTED] writes: Want to fix problems in the Lilypond documentation I really wonder where Fine tuning a piece went from the Tutorial? It is in stable, but not in development. I find it quite good, by the way, save some disorganization. I don't know; I had a quick poke around in the docs, but I couldn't see it. Han? You've made almost all the changes to tutorial.itely in recent times. What happened to Fine tuning a piece? Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: dashed slur problem
On Sun, 22 Jun 2003 16:05:20 + David Bobroff [EMAIL PROTECTED] wrote: I'm using dashed slurs but I'm having a problem switching between dashed and normal slurs. In the attached *.ly file the problem can be seen on the fourth line of the output. The switching in the first line works fine. In the fourth line it doesn't. If I separate out the fourth line I can get it to work but not if it is in context. In the fourth line the beamed [d cis] and the beamed [cis f] should have normal solid slurs but they have dashed slurs. Assuming this hasn't been solved yet, could you try reorganizing the file somewhat (ie much shorter lines; an absolute maximum of 80 chars per line) and resending it? I've had a poke around, but I can't figure out what's wrong. If the file was a bit less messy, more people might look at it, and somebody might be able to figure it out. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: help required in input/test
[EMAIL PROTECTED] writes: On Fri, 04 Jul 2003 18:31:03 +0200 Ferenc Wagner [EMAIL PROTECTED] wrote: Graham Percival [EMAIL PROTECTED] writes: Want to fix problems in the Lilypond documentation I really wonder where Fine tuning a piece went from the Tutorial? It is in stable, but not in development. I find it quite good, by the way, save some disorganization. I don't know; I had a quick poke around in the docs, but I couldn't see it. Han? You've made almost all the changes to tutorial.itely in recent times. What happened to Fine tuning a piece? Some parts were moved to the refman. Follow the links, in particular, Constructing a tweak -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: help required in input/test
On Mon, 07 Jul 2003 12:13:34 +0200 Han-Wen Nienhuys [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] writes: Han? You've made almost all the changes to tutorial.itely in recent times. What happened to Fine tuning a piece? Some parts were moved to the refman. Follow the links, in particular, Constructing a tweak Thanks. Time for me to recompile my copy of the Lilypond web pages -- I was still looking at 1.7.22 or .23 (I think it was CVS in between those two). Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
pdftex doesn't work
Hello,
I am quite new to lilypond, but as far as I explored it, I like it.
But now I have a problem. I took the source code from the lilypond
tutorial
--- CODE ---
\score {
\notes {
\time 3/4
\clef bass
c2 e4 g2.
f4 e d c2.
}
\paper { }
}
--- CODE ---
saved it to t.ly and invoked ly2dvi --pdftex t.ly. And this is what
it said:
--- Output ---
Running LilyPond...
GNU LilyPond 1.6.9
Now processing: `t.ly'
Verarbeite...
Interpretiere die Noten...[5]
Verarbeite Element vor...
Berechne Position der Spalten... [3][5]
paper output to `t.pdftex'...
Analyzing t.pdftex...
Running LaTeX...
ly2dvi:Fehler: LaTeX failed on the output file.
ly2dvi:Fehler: The error log is as follows:
! File ended while scanning use of \lybox.
inserted text
\par
l.15 \input t.pdftex
I suspect you have forgotten a `}', causing me
to read past where you wante
Traceback (most recent call last):
File /usr/local/bin/ly2dvi, line 1099, in ?
run_latex (files, outbase, extra_init)
File /usr/local/bin/ly2dvi, line 777, in run_latex
raise 'LaTeX error'
LaTeX error
--- Output ---
I have read that the pdftex option is still under development or isn't
it working at all? Or is it a problem on my side?
The normal ly2dvi works fine. I also can do a ly2dvi -k t.ly and a
pdflatex t.latex from the ly2dvi directory and get a good looking pdf
file.
Hope you can help.
--
Arne Bosien [EMAIL PROTECTED]
http://www.tu-harburg.de/~siab0389/
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re[2]: etf2ly wows
I am experiencing some problems with etf2ly. When I convert from etf to ly the key changes??? Is there something I can do about this?? Either in Finale before I convert or in etf2ly?? GP I'm not certain how up-to-date etf2ly is -- what version of Finale file are GP you trying to convert? I suspect that you might even save time by simply GP re-typing the file into lilypond from scratch, rather than trying to make GP etf2ly work. Actually, I've had this problem a few times. There's nothing you can do about it. I hope you didn't have too big a piece to convert, because it's due to the messed up way Finale stores keys. It stores pitches relative to a base (the key). This may sound silly, but I've been using ETF2LY for quite some time now, and I've got around three hundred pages of music typeset. These cases are, albeit not rare, avoidable. I think staying clear of minor keys might do the trick (though I don't have any facts to base my affirmation on). In any case, you'll have no problem if you just enter the accidentals manually (or do a search replace for b to bes, for instance). ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: pdftex doesn't work
The pdftex option is still very experimental and is not always
updated when lilypond changes. Use 'ly2dvi -p' to get a PDF
file.
/Mats
Arne Bosien wrote:
Hello,
I am quite new to lilypond, but as far as I explored it, I like it.
But now I have a problem. I took the source code from the lilypond
tutorial
--- CODE ---
\score {
\notes {
\time 3/4
\clef bass
c2 e4 g2.
f4 e d c2.
}
\paper { }
}
--- CODE ---
saved it to t.ly and invoked ly2dvi --pdftex t.ly. And this is what
it said:
--- Output ---
Running LilyPond...
GNU LilyPond 1.6.9
Now processing: `t.ly'
Verarbeite...
Interpretiere die Noten...[5]
Verarbeite Element vor...
Berechne Position der Spalten... [3][5]
paper output to `t.pdftex'...
Analyzing t.pdftex...
Running LaTeX...
ly2dvi:Fehler: LaTeX failed on the output file.
ly2dvi:Fehler: The error log is as follows:
! File ended while scanning use of \lybox.
inserted text
\par
l.15 \input t.pdftex
I suspect you have forgotten a `}', causing me
to read past where you wante
Traceback (most recent call last):
File /usr/local/bin/ly2dvi, line 1099, in ?
run_latex (files, outbase, extra_init)
File /usr/local/bin/ly2dvi, line 777, in run_latex
raise 'LaTeX error'
LaTeX error
--- Output ---
I have read that the pdftex option is still under development or isn't
it working at all? Or is it a problem on my side?
The normal ly2dvi works fine. I also can do a ly2dvi -k t.ly and a
pdflatex t.latex from the ly2dvi directory and get a good looking pdf
file.
Hope you can help.
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Problem with Chord Names
Hi Han-Wen, all, (re back to list) It would be cool to put it in lilypond as a template file, but for consistency either the \key should go, or the \transpose should be added, right? I'll make you a good, consistent one. Amy ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Jazz Group Template, was: Re: Problem with Chord Names
Hi Han-Wen, Rick, all,
This is a thoroughly cleaned-up version (FYE, for your edification):
\version 1.6.6
\header {
title = Song
subtitle = (tune)
composer = Me
meter = moderato
piece = Swing
tagline = Lilypond example file by Amelie Zapf, Berlin 07/07/2003
}
\include paper16.ly
\include english.ly
Some macros %%%
sl = {
\property Voice.NoteHead \override #'style = #'slash
\property Voice.Stem \override #'length = #0 }
nsl = {
\property Voice.NoteHead \revert #'style
\property Voice.Stem \revert #'length }
cr = \property Voice.NoteHead \override #'style = #'cross
ncr = \property Voice.NoteHead \revert #'style
jzchords = \property ChordNames.ChordName \override #'style = #'jazz
Keys'n'thangs %
global = \notes {
\time 4/4
}
Key = \notes \key c \major
% Horns
% -- Trumpet --
trpt = \notes \transpose d' \relative c'' {
\Key
c1 c c
}
trpharmony = \chords \transpose d { \jzchords }
trumpet = {
\global
\property Staff.instrument = #Trumpet
\clef treble
\context Staff
\trpt
}
% -- Alto Saxophone --
alto = \notes \transpose a' \relative c' {
\Key
c1 c c
}
altoharmony = \chords \transpose a { \jzchords }
altosax = {
\global
\property Staff.instrument = #Alto Sax
\clef treble
\context Staff
\alto
}
% -- Baritone Saxophone --
bari = \notes \transpose a'' \relative c {
\Key
c1 c \sl d4^Solo d d d \nsl
}
bariharmony = \chords \transpose a { \jzchords s1 s d2:maj e:m.7 }
barisax = {
\global
\property Staff.instrument = #Bari Sax
\clef treble
\context Staff
\bari
}
% -- Trombone --
tbone = \notes \relative c {
\Key
c1 c c
}
tboneharmony = \chords { \jzchords }
trombone = {
\global
\property Staff.instrument = #Trombone
\clef bass
\context Staff
\tbone
}
% Rhythm Section #
% -- Guitar --
gtr = \notes \relative c'' {
\Key
c1 \sl b4 b b b \nsl c1
}
gtrharmony = \chords { \jzchords
s1 c2:min.7+ d2:maj.9
}
guitar = {
\global
\property Staff.instrument = #Guitar
\clef treble
\context Staff
\gtr
}
%% -- Piano --
rhUpper = \notes \relative c'' {
\voiceOne
\Key
c1 c c
}
rhLower = \notes \relative c' {
\voiceTwo
\Key
e1 e e
}
lhUpper = \notes \relative c' {
\voiceOne
\Key
g1 g g
}
lhLower = \notes \relative c {
\voiceTwo
\Key
c1 c c
}
PianoRH = {
\clef treble
\global
\property Staff.midiInstrument = acoustic grand
\context Staff
\context Voice = one \rhUpper
\context Voice = two \rhLower
}
PianoLH = {
\clef bass
\global
\property Staff.midiInstrument = acoustic grand
\context Staff
\context Voice = one \lhUpper
\context Voice = two \lhLower
}
piano = {
\context PianoStaff
\property PianoStaff.instrument = #Piano
\context Staff = upper \PianoRH
\context Staff = lower \PianoLH
}
% -- Bass Guitar --
bass = \notes \relative c {
\Key
c1 c c
}
bass = {
\global
\property Staff.instrument = #Bass
\clef bass
\context Staff
\bass
}
% -- Drums --
\include drumpitch-init.ly
up = \notes {
hh4 hh4 sn hh4 hh4 sn hh4 hh4 sn hh4 hh4 sn
hh4 hh4 sn hh4 hh4 sn
}
down = \notes {
bd4 s bd s bd s bd s bd s bd s
}
drums = {
\global
\property Staff.instrument = #Drums
\clef percussion
\context Staff
\context Voice = first { \voiceOne \up }
\context Voice = second { \voiceTwo \down }
}
% It All Goes Together Here %%
\score {
\context StaffGroup = horns
\context Staff = trumpet \trumpet
\context Staff = altosax \altosax
\context ChordNames = barichords \bariharmony
\context Staff = barisax \barisax
\context Staff = trombone \trombone
\context StaffGroup = rhythm
\context ChordNames = chords \gtrharmony
\context Staff = guitar \guitar
\context PianoStaff = piano \piano
\context Staff = bass \bass
\apply #(drums-paper 'drums) \context Staff = drums \drums
Re: pdftex doesn't work
Arne Bosien [EMAIL PROTECTED] writes: But now I have a problem. I took the source code from the lilypond tutorial saved it to t.ly and invoked ly2dvi --pdftex t.ly. And this is what it said: Do you have a particularly reason to use --pdeftex? If not, you should try ly2dvi --pdf. --- Output --- Running LilyPond... GNU LilyPond 1.6.9 Ah, some pdftex bugs have been fixed in 1.6.10, but pdftex is not a much used backend. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: etf2ly wows
yup, thats what I'm doing. oh well. probably the version of finale is just to new... Thanks Aaron On Mon, 2003-07-07 at 12:47, Graham Percival wrote: On Sun, 06 Jul 2003 08:20:21 +0300 Aaron [EMAIL PROTECTED] wrote: I am experiencing some problems with etf2ly. When I convert from etf to ly the key changes??? Is there something I can do about this?? Either in Finale before I convert or in etf2ly?? I'm not certain how up-to-date etf2ly is -- what version of Finale file are you trying to convert? I suspect that you might even save time by simply re-typing the file into lilypond from scratch, rather than trying to make etf2ly work. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Re[2]: etf2ly wows
Hi all, What I am doing is not starting from scratch but converting etf2ly and searching and replacing the wrong notes with the right one. What would be the easiest is a script that transposes the key. ie. you input the new key and it automatically searches and replaces. Does such a script exist?? Thanks Aaron On Mon, 2003-07-07 at 15:07, Jeremy wrote: I am experiencing some problems with etf2ly. When I convert from etf to ly the key changes??? Is there something I can do about this?? Either in Finale before I convert or in etf2ly?? GP I'm not certain how up-to-date etf2ly is -- what version of Finale file are GP you trying to convert? I suspect that you might even save time by simply GP re-typing the file into lilypond from scratch, rather than trying to make GP etf2ly work. Actually, I've had this problem a few times. There's nothing you can do about it. I hope you didn't have too big a piece to convert, because it's due to the messed up way Finale stores keys. It stores pitches relative to a base (the key). This may sound silly, but I've been using ETF2LY for quite some time now, and I've got around three hundred pages of music typeset. These cases are, albeit not rare, avoidable. I think staying clear of minor keys might do the trick (though I don't have any facts to base my affirmation on). In any case, you'll have no problem if you just enter the accidentals manually (or do a search replace for b to bes, for instance). ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Source transposition
Is there a simple way to transpose a mudela source file? I'm thinking to a simple parser that replaces all the note names with the transposed ones. Antonio Palama' ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Jazz Group Template, was: Re: Problem with Chord Names
Amelie Zapf wrote: Hi Han-Wen, Rick, all, This is a thoroughly cleaned-up version (FYE, for your edification): That's really great! FWIW I usually delay the transposition until the \score section leaving the notes in concert pitch before that. That gives me more flexibility to change things like maybe to repeat a phrase with another instrument. Paul Scott ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Re[2]: etf2ly wows
Hi, What I seem to get is that the conversion want to make all my files into c major. The rythem translates perfectly. But the notes not. I can give an example if anyone thinks it worth the time to play with etf2ly. In the mean time I convert and use search and replace to fix the note names. a script would be as I said much quicker. Thanks Aaron On Mon, 2003-07-07 at 21:45, Jan Nieuwenhuizen wrote: Jeremy [EMAIL PROTECTED] writes: Actually, I've had this problem a few times. There's nothing you can do about it. If you cannot reproduce the problem, there's nothing you can do. I think staying clear of minor keys might do the trick But if you can reduce the problem to a real simple etf file that gives the wrong result, you can send a bug report. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Is there something like a Score-O-Matic?
Hello Everyone, I was wonder if someone has come up with a program/script that would produce score templates automatically. I was thinking something like a bash/perl/python script that would allow you to choose the instrumentation, title, key and whatever else could be done from a script, then would automatically produce a directory with all the templates needed for that score. I was even thinking that maybe a Makefile could be used to automatically produce all the parts. Rick Sutphin ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Centering Piano Staff Name
Hello, This is a very minor quibble, but I was wondering if there is a way to center the staff name on a piano staff so that it appears centered between the two staves. Thanks, Rick Sutphin ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
PAS Notation Standards and Lilypond
Hello, I was wondering if anyone as worked on the drum notation for lilypond to make it better conform to PAS (Percussive Arts Society) standards? I edited my drums.scm file (probably not the correct approach), after fighting with define with no luck. I have got most of the notation closer to PAS standards, but I am sure someone who 1) knows lilypond and/or 2) knows drum notation better than me could do a much better job. Thanks, Rick Sutphin ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Jazz Combo Template
Hello, Attached is a template for a small jazz combo (4 horns and rhythm section). It handles part extraction and chord names on the score (once at top) and on individual parts. I put it together with ideas from the lilypond website and some suggestions from [EMAIL PROTECTED] (any hare-brained ideas or stupid mistakes our most likely mine, unfortunately). I have posted it here hoping that it might be useful; if not I would be interested in any comments, suggestions or criticisms. Wild praise and adulation will be accepted as well (yeah right!!!). Rick Sutphin jazz_combo_template.tar.gz Description: GNU Zip compressed data ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: help required in input/test
Graham,
Any advanced Lilypond users out there
Well, I'm not an advanced user but I'll give a try :))
1) add-staccato.ly: the staccatos don't get added. The make-music and
scm stuff needs to be fixed/updated. (hint: add-text-script.ly does
work; maybe that can help you with add-staccato.ly)
Try putting 'EventChord in the place of 'RequestChord around line 18:
(if (equal? (ly:get-mus-property m 'name) 'EventChord)
3) boxed-molecule.ly: knowledge of #'molecule-callback. I think we're
missing a few boxes in this example.
It seems to be working here... (lily 1.7.24 and latest cvs code)
maybe the FIXME in this file can be deleted?
4) chord-names-jazz.ly and chords.ly: both have been massively
commented out. I've never used chords, so I'd appreciate it if somebody
else looked at them.
chord-names-jazz.ly had a few misplaced dots and a
#(set-chord-name-style 'jazz) code that seems not to be necessary
anymore. The corrected code (or at least compilable :)) is as
follows. I couldn't find chords.ly thought.
-
scheme = \chords {
% major chords
c
c:6 % 6 = major triad with added sixth
c:maj % triangle = maj
c:6.9^7 % 6/9
c:9^7 % add9
% minor chords
c:m % m = minor triad
c:m6 % m6 = minor triad with added sixth
c:m7+ % m triangle = minor major seventh chord
c:3-.6.9^7% m6/9
c:m7 % m7
c:3-.9% m9
c:3-.9^7 % madd9
% dominant chords
c:7 % 7 = dominant
c:7.5+% +7 = augmented dominant
c:7.5-% 7b5 = hard diminished dominant
c:9 % 7(9)
c:9- % 7(b9)
c:9+ % 7(#9)
c:13^9.11 % 7(13)
c:13-^9.11% 7(b13)
c:13^11 % 7(9,13)
c:13.9-^11% 7(b9,13)
c:13.9+^11% 7(#9,13)
c:13-^11 % 7(9,b13)
c:13-.9-^11 % 7(b9,b13)
c:13-.9+^11 % 7(#9,b13)
% half diminished chords
c:m5-.7 % slashed o = m7b5
c:9.3-.5- % o/7(pure 9)
% diminished chords
c:m5-.7- % o = diminished seventh chord
}
\score {
\notes
\context ChordNames {
% #(set-chord-name-style 'jazz)
\scheme }
\context Staff \transpose c c' \scheme
}
5) cue-notes.ly: question about music notation: if you have a cue in a
different clef, should you return to the initial clef before you start
the real notes? IIRC you should, but this file originally didn't do
that.
I'm not an expert on that, but the viola parts I usually play return
to the initial clef. I'll check other (and more reliable) editions
thought. Meanwhile, how about uncommenting the line that set the
notes of the horn to the right size? (\property Staff.fontSize\unset)
6) move-mark.ly: I suspect this scheme isn't working. Any scheme
hackers want to take a look?
I'm sorry but I couldn't get this one to work :(( But ... since If
possible, avoid this feature [outputproperty]: the semantics are not
very clean, and the syntax and semantics are up for rewrite (user's
manual) why not change the example to something nicer like:
\context Staff \notes\relative c''{
c1
\once \property Score.RehearsalMark
\set #'extra-offset = #'(-0.3 . 3.0)
\mark A
d
\mark B
e
}
7) music-box.ly: I'm not certain that we need so much blank space in
this example. (ok, this one is a question for Han or Jan)
my vote would be for less space
Cheers,
Pedro
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Centering Piano Staff Name
On Mon, 07 Jul 2003 20:25:18 -0400 Rick Sutphin [EMAIL PROTECTED] wrote: This is a very minor quibble, but I was wondering if there is a way to center the staff name on a piano staff so that it appears centered between the two staves. Yes -- name the PianoStaff instead of the individual staffs. See input/test/instrument-name-grandstaff.ly for a similar example. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
