Hello,
I want to transpose a song consisting of leadsheat and ukulele. It's my
first song I typeset with Lilypond.
At least I get an output that shows the most parts. But I am not
satisfied in some points. I hope you can give me some hints how to
improve it.
Hello Helge,
I am just a user like yourself, I will try to help you.
Lilypond is great as you can use many hacks and shortcuts.
A good practise is to create a folder somewhere where it will stay for long time.
And let Lilypond know about this folder in
Edit > Preferences > Lilypond Preferences > Lilypond include path
Here you can add your 'hacks'.
- There are a lot of warnings "No string for pitch #..." In the fret
diagram I find damped strings. E.g. the first fret diagram Dm should
show all for strings corresponding to the appendix A of the notation
reference. How can I get the fret diagram with all for strings.
The program complains that no strings are attached to certain notes.
You should create your own chord definitions in a separate file and store that file in the folder described above.
I am sharing my one with you (
ukulele-chords-de.ly), where I changed the Bs to Hs and the BESs to Bs (to comply with the German language).
If you want to create different chord definitions, just copy/paste one and change accordingly.
You will understand the logic I am sure, it's not so difficult, although it may be overwhelming at first.
- The chord Csus4 is written only as C4 (omitting the sus). Even if the
sus is correct in the sense of music theory, I would like to stay witht
the C4. Unfortunately I didn't fount this in the NR. Any idea?
This is another hack, the 'ignatzek Exceptions'
Again, you will need to define your own names, at least for certain chords.
I created a file 'extras.ly' which you should put in the above-mentioned folder.
There you will see the code and a few examples for chord-name definitions.
Example: <c f g> 1-\markup { \super "4" }
'c f g' here simply means 1.4.5 (it's automatically transposed to any chord); \super makes it small; '4' is the number you need.
- This distance between the last verse and the rythm staff should be
increased.
This is something defined in the \new Staff {\melody}
Here's the code that I added:
\new Staff \with {
\override VerticalAxisGroup.default-staff-staff-spacing.basic-distance = #30 } { \melody }
Play with the number to adjust to your nneds.
If there are other clumsy things in my notation, any comment is appreciated.
Adding \paper {indent = 0} at the bottom of the document will bring the first line of the staff to the left .
Otherwise, it looks great for a first attempt on Lilypond!