> The Barbers Adagio for violin, clarinet and organ is working great.
> But while writing I came across the following problems/issues/questions.
> First, I'm on SuSE 6.3 running Lily 1.2.17.
Below, I will refer to some of the example files for Lilypond.
I'm not sure if they're included in the RPM, otherwise you
could download the source files of your Lilypond version
(lilypond-1.2.17.tar.gz) and extract the directories
lilypond-1.2.17/input/test/ and lilypond-1.2.17/mutopia/
> 1.
> I couldn't add any "stuff" to chords. For example, if i did
> <c e g>, that worked fine, but if I did <c e g>-\fermata, I would crash.
> I tried several different styles, and nothing worked. Same goes for
> any markings, such as dynamics, etc.
The markings should be attached to a note, not to the chord,
try <c e g-\fermata >
> 2.
> I wanted to print the organ part with the violin above, but in a
> smaller, light size. Can I have two different staff sizes on one
> score?
Take a look at input/test/staff-size.ly
> 3.
> Is there a way to set Lily to print the score and the parts in one
> file? I had to copy the file four times and adjust the \score block
> to print the parts.
Just write several \score blocks in the same file.
If you want a separate .dvi file for each score, use
the flag -s to ly2dvi.
> 4.
> Related to that, I couldn't seem to make \transpose work on the
> \staff block...I had to put it in the \notes block for that part.
> Hence I have a score that has the clarinet staff in a different key
> from the rest of the parts. I'd like to be able to use the
> instrument's native key for its part, and \transpose when I print that
> part on the master score.
\transpose works only on the music as you have noted.
Take a look at mutopia/N.W.Gade/score.ly and the included
files to see how to handle the transposing. (It's only done
for the MIDI generation, not for the score, but the idea is
the same.)
> 5.
> I'm not entirely clear on octaves. Its hard to know when you're
> typing in the parts whether you need to give it a ' or a ,. The only
> way I could do it was to do the best I could during entry, and then
> compile, look at it, go back and change it again. And of course the
> octave change affects all the notes after it...just wondering if
> anyone had a helpful tip on how to make this easier. Yes I'm using
> \relative...maybe that's actually making it more difficult?
The principle of \relative mode is that Lilypond takes the note
closest to the previous one. If you write "c d" it will chose
the d one step above the c instead of the d 7 steps below.
If you write "c f" you get the f 4 steps above c instead of the
f 5 steps below, whereas if you write "c g" it goes down 4 steps
instead of up 5 steps. If you wanted the g above the c, you would
write "c g'". The idea is that most intervals in ordinary music
are small, so this will save some typing.
> 6.I couldn't figure out how to print the part names next to the
> staves. What I ended up doing was putting in text above the first
> note on each instrument's part, but of course this didn't propagate to
> the other pages.
The page layout handling provided by ly2dvi is just one suggestion.
If you want something else, do the following:
- ly2dvi -kK yourfile.ly
- Edit the LaTeX file yourfile_ly*.tex to get any desired page
layout, for example inserting the instrument name into the
page header.
- latex yourfile_ly*.tex
If you later on update your Mudela files, just run
'lilypond yourfile.ly' and 'latex yourfile_ly*.tex'
> 7.How do you print page numberings? They show up in kghostview, but
> not in print.
??? The default page size is A4, maybe the page number is
outside the page if you print on letter size paper?
By the way, the page layout has been improved in the
latest development versions.
> 8.How do you print either numbers in squares, or measure numbers.
> Again, I did this by putting text above a note, but if that not
> happened to be a chord or something, I couldn't do it, so violin ended
> up with some measure numbers and clarinet with some others.
Just include the Bar_number_engraver, this is done by
\score{
...
\paper{
\translator{\OrchestralScoreContext}
...
}
}
For the parts, you can use the \OrchestralPartStaffContext
Again, I guess you could get some inspiration from the example
in mutopia/N.W.Gade/
/Mats
