1 \input texinfo @c -*-texinfo-*-
3 @settitle FAQ - GNU LilyPond FAQs
5 @node Top, , Windows32, (dir)
8 * FAQ - GNU LilyPond FAQs:: FAQ - GNU LilyPond FAQs
13 @node FAQ - GNU LilyPond FAQs, Miscellaneous, , Top
15 * Miscellaneous:: Miscellaneous
16 * Installing:: Installing
17 * Documentation:: Documentation
18 * Language- mudela:: Language- mudela
19 * Do you support -:: Do you support -
20 * How do I -:: How do I -
21 * Development:: Development
23 * Copyright:: Copyright
24 * Windows32:: Windows32
26 @chapter FAQ - GNU LilyPond FAQs
29 @node Miscellaneous, Installing, FAQ - GNU LilyPond FAQs, FAQ - GNU LilyPond FAQs
30 @section Miscellaneous
32 @subsubsection HELP! I'm stuck!
34 Please read this document carefully. If you are still at loss, send
35 your questions to the @strong{mailing list}, and not to authors
38 Note: relative paths are meant to be relative to the source directory
40 @node Installing, Documentation, Miscellaneous, FAQ - GNU LilyPond FAQs
44 @subsubsection If I install the .exe file on my DOS/windows 3.11 machine, it doesn't work
46 The NT port is done with the Cygnus GNU/Windows32 port of the GNU utils.
47 It does @emph{not} work with windows 3.x; you need Windows-NT (95/98?).
49 @subsubsection Where is guile-config
51 Old RedHat RPMS don't include guile-config. You need guile-config as it
52 was produced during the RPM build run. Build the RPM from source
53 (@file{.src.rpm}), and use the guile-config that is in
54 @file{/usr/src/redhat/BUILD/guile-1.3/guile-config/}.
56 @subsubsection I get all kinds of errors while compiling @file{parser.cc}
58 LilyPond uses features of bison version 1.25. Please confirm that
59 you are using a version 1.25 or better, that is @strong{GNU} bison
60 @strong{1.25}. Don't forget to do "make clean" after installing it. Don't
61 forget to remove the stale @file{bison.simple} as well.
63 If the problem persists, then please send a bug report to the mailing list.
65 @subsubsection I upgraded by applying a patch, and now my configure/build breaks.
67 Patches don't include automatically generated files, i.e.
68 @file{configure} and files generated by @file{configure}. Regenerate them
78 @subsubsection Some of your neat scripts fail, what directories do you use:
80 [This only applies if you don't do @code{make install}, and run out
81 of the source directory]
83 I have a directory which contains all our development projects
90 which looks like @file{/usr/}
103 @file{~/usr/bin/} is in the variable PATH, and contains symbolic links
104 to the compiled executables. Unpacked sources, releases and patches are
105 in subdirectories under @file{~/usr/src/}.
107 @subsubsection Is there an emacs mode?
109 Yes. It is included with the source archive as @file{lilypond-mode.el}.
110 If you have an RPM it is in @file{/usr/doc/lilypond-X/}. You have to
113 @subsubsection How do I create the @file{.tfm} files?
115 You don't. The @file{.tfm} files should be generated automatically by
116 Metafont when you run TeX. Check your TeX installation, or ask
117 your local TeX guru. The supplied @file{.afm} files are intended to
118 be used by LilyPond, not by any other programs.
120 @node Documentation, Language- mudela, Installing, FAQ - GNU LilyPond FAQs
121 @section Documentation
123 @subsubsection What a sober website/manual you have there!
125 LilyPond development is moving quite fast, documentation will often lag
126 a bit behind. But don't hesitate to point out inaccuracies. Whip up
127 your mail reader and write to the mailing list.
129 @subsubsection Please take me off your mailing list, I get so much mail!
131 Don't ask Han-wen, don't ask David. Instead, read about
132 @uref{../../index.html#mailing-lists, the mailing lists} here.
134 @node Language- mudela, Do you support -, Documentation, FAQ - GNU LilyPond FAQs
135 @section Language: mudela
137 @subsubsection Why do I have to type the accidentals to the note if I
138 specified them in the keysignature?
147 Independently of how it was written and what the current key was, you
148 would say that you are playing and reading "two C-sharp" notes, so you
149 have to enter C-sharp twice.
151 @subsubsection What is @code{cis} anyway
153 @code{cis} is the dutch naming for C-sharp. The notes are named
154 a, b,.., g. The suffix -is means sharp, and -es flat. This system is
155 common in a number of languages (such as swedish, dutch, german.)
156 Certain other languages (such as English, French and Italian) just add
157 the word for "sharp" to the notename.
159 We chose the Dutch system, because we're dutch. You are free to chose
160 whatever names you like; they are user definable.
162 @subsubsection Why are [] around the notes, and () inbetween?
164 [] designate beams, a note can only be in one beam at the same
165 time. () is a slur, which connects notes. You need to be able to
173 @subsubsection I want to insert some TeX commands.
175 You shouldn't: it's against LilyPond philosophy to have typesetting
176 commands in the mudela source. Moreover, this would be difficult.
177 LilyPond uses TeX like a glorified output engine: the output consists
178 of (x,y) positions and symbols. You can only sensibly do TeX stuff in
179 the symbol string. You can access the symbol string easily for some
180 symbols (notably lyrics and @code{^"text"} commands).
182 @node Do you support -, How do I -, Language- mudela, FAQ - GNU LilyPond FAQs
183 @section Do you support ...
185 @subsubsection Do you support pop songs (chords, single staff, lyrics)?
187 Yes, see the @file{twinkle-pop} example.
189 @subsubsection Do you support guitar chord diagrams?
191 No. We ourselves don't play guitar, and don't know the fine points of
192 this notation. We would welcome anyone who could give this a try.
194 @subsubsection Do you support TAB notation?
196 No. The same as for the previous question goes.
199 @subsubsection Do you support multiple staff-sizes?
201 Yes. At this time you can choose between 11, 13, 16, 19, 20, 23 and 20
202 pt staff-size. Use the @code{staffSpace} property for setting the
203 size of the staff, and @code{fontSize} for setting the size of the
206 @subsubsection Do you support Gregorian chant notation?
211 @subsubsection Do you support grace notes?
213 Yes. See @file{input/test/grace.ly}.
215 @node How do I -, Development, Do you support -, FAQ - GNU LilyPond FAQs
216 @section How do I ....
218 @subsubsection How do I change the TeX layout?
220 See @file{lilyponddefs.tex}, it has some comments. Or use @file{ly2dvi}.
222 @subsubsection How do I place lyrics under @emph{each} of the staves in a score, as choral music. I can work out how to put lyrics for each line all under the top line, or at the bottom but not between!
224 You change the order lyrics and staves. You have to name all
225 staves (lyric and melodic), otherwise they will end up in the same
229 < \melodic \type Staff = "treble" \trebleMelody
230 \lyric \type Lyrics = "tlyrics" \trebtext
231 \type Staff = "bass" \melodic \bassMelody
232 \lyric \type Lyrics = "blyrics" \basstext
239 @subsubsection How do I put more than one marking on a note.
248 or use spacing-notes to put markings at different horizontal positions
252 @{ s4\ff s4^"text" s4-\marcato s4 @}
257 This also works for crescendi, eg,
266 @subsubsection How do I combine multiple pieces into one document
268 There are several solutions:
278 produces one combined @file{foo.dvi}
279 @item make a toplevel @file{.ly} file that contains al pieces:
289 @item make a hybrid TeX/LilyPond @file{.doc} document (see the
290 @file{Documentation/tex} directory).
293 For the first two solutions, you will need to move @code{\header} info
294 in each individual piece from toplevel into the @code{\paper} block.
296 There are several examples in the @file{mutopia} directory.
298 @subsubsection How do I get bar numbers?
300 See @file{input/test/bar-scripts.ly}.
302 @subsubsection How do I change the tagline 'Lily was here'?
304 In the @code{\header} field, add a @code{tagline} entry, e.g.
307 tagline="Typeset by GNU LilyPond"
311 @subsubsection Can I make blank manuscript paper with LilyPond?
313 Theoretically, yes but it is easier to do with TeX:
316 \def\foo@{\hbox@{\vrule width 15.0cm height 0.5pt depth 0.0pt@}
318 \vskip 5pt\nointerlineskip@}
319 \def\musicline@{\vbox @{
332 @node Development, Running, How do I -, FAQ - GNU LilyPond FAQs
335 @subsubsection Could you implement feature XXXX? It is really easy, just extend the syntax to allow YYYY!
337 In general finding a cute syntax (such as YYYY) isn't very hard. The
338 complicated issue how to adapt the internals to do XXXX. The parser is
339 really a simple front end to the complicated internals.
341 @subsubsection Can I join in on LilyPond development? How do I do this?
343 Yes, we do frequent releases, you are welcome to send in a patch or do
344 suggestions. Join the list @email{gnu-music-discuss@@gnu.org} to
348 @subsubsection Is there a GUI frontend? Should I start building one?
350 LilyPond currently has no graphical interface. We (LilyPond authors)
351 don't feel the need to write a GUI, but several others do:
353 Matthew Hiller has extended Midiscore and Koobase to handle mudela.
354 Check out @uref{http://zoo.cs.yale.edu/~meh25/}. He is now working on
355 `Denemo', a GTK based notation program (which is still being developed).
357 Federico Mena-Quintero and Elliot Lee of RedHat Advanced Development
358 labs have plans to write a GNOME based Music notation program. However,
359 there is no code, only plans.
361 Chris Cannam is working a rewrite of Rosegarden. The new design should
362 be more modular, and could conceivably be used to output
363 mudela. However, the not much seems to have happened the past year. See
364 @uref{http://www.all-day-breakfast.com/rosegarden/development.html}.
367 @subsubsection I want to implement XXXX! How should I do this?
369 Your best bet of getting us to include code, is to present it as a
370 "fait accompli", i.e., to send a patch to the mailing list.
372 Please use the diff command to generate a patch, and don't send complete
373 files, even if the diff is larger than the whole file.
375 Don't forget to put your name and e-mail address in the file
376 @file{Documentation/topdocs/AUTHORS.texi}, or you won't get credits
380 @subsubsection Your make system does not adhere to GNU coding standards, could you please fix it?
382 No. We have evaluated the standard GNU combination for compiling
383 programs (autoconf, automake, libtool) and found to be inadequate for
386 @subsubsection gdb crashes when I debug!
388 Upgrade/downgrade to 4.17.
390 @node Running, Copyright, Development, FAQ - GNU LilyPond FAQs
393 @subsubsection I use dvilj4, and there are lots of warning messages for the printing
395 You should use dvips and ghostscript to print the @code{dvi} output: the
396 slurs and beams are PS @code{\special} commands.
399 @subsubsection My symbols are all messed up after I upgraded, I get the wrong symbols and dvi-checksum errors!
401 We obviously mucked with the fonts in the upgrade. Remove @emph{all}
402 previous fonts, including the @file{.pk} and @file{.tfm} fonts in
403 @file{/var/lib/texmf}. A script automating this has been included, see
404 @file{buildscripts/clean-fonts.sh}.
406 @subsubsection all the pk and tfm fonts are created in the directory where the mudela file is, not in "/var/spool/texmf" where I think they should be.
408 Mats Bengtsson <mats.bengtsson@@s3.kth.se> writes:
410 The simple solution used by Anthony Fok in the Debian distribution of
411 Lilypond is to link the mf/ directory to
412 /usr/lib/texmf/fonts/source/public/lilypond Depending on what
413 distribution of teTeX and Linux you have installed, there might also
414 be other places like /usr/local/lib/texmf/fonts/source/public/lilypond
415 or /var/spool/texmf//fonts/source/public/lilypond
417 Wherever you put it, don't forget to run mktexlsr (or texhash for
418 older installations) afterwards, so that TeX will find the files.
419 Also, don't forget to remove all old .tfm and .*pk files when the font
420 is updated (as it will be in version 1.1.40, for example).
422 @subsubsection Are there scalable versions of the font?
424 Yes, they are type-3 fonts. In the @file{mf/}
431 in the mf/ subdirectory. This will also make @file{mfplain} for metapost.
432 The @file{pfa}s will be in the subdirectory @file{out/}.
434 @subsubsection How does PS output work?
438 Generate the PostScript Type-3 fonts.
440 Run lilypond with option @code{-f ps}:
447 @item To view the @file{.ps} output with GhostView, set GS_FONTPATH to the
448 directory containing the @file{pfa}s. In the source tree, this is @file{mf/out/}.
450 i.e. do something like:
453 export GS_FONTPATH=$HOME/usr/src/lilypond/mf/out
460 Direct PS output is still experimental. For creating nice looking ps
461 output, use TeX and @code{dvips}.
464 @subsubsection The beams and slurs are gone when using the XDvi magnifying glass!?
466 Various dynamic symbols, such as beams, crescendi, slurs are done in
467 PostScript. XDvi doesn't show PostScript in the magnifying glass.
468 Complain to the XDvi maintainers.
471 @subsubsection Beams, slurs and crescendi are not displayed at all!
473 See previous answer. XDvi uses GhostScript for displaying PostScript,
474 check that you have GhostScript installed. If you use a different
475 DVI viewer, check if it will display embedded PostScript. Don't worry,
476 the symbols should appear on the printout.
478 @subsubsection A lot of musical stuff doesn't make it to the MIDI file, eg. dynamics, articulation, etc.
480 The MIDI output was originally put in as a proof that MIDI could be
481 done, and as a method of proof"reading" the input. The MIDI support
482 is by no means finished. Patches appreciated.
484 @node Copyright, Windows32, Running, FAQ - GNU LilyPond FAQs
487 @subsubsection What is Urtext? Critical Edition?
491 It may be translated best as `that what the composer intended to tell
494 Peter Chubb <peterc@@aurema.com> writes:
496 An Urtext is a reconstruction of the earliest form of a text,
497 including mistakes the original author wrote. Where there is no
498 available facsimile of the original, creating this can involve some
499 inspired detective work (in comparing various later editions and
500 trying to deduce what the original form was). As far as copyright
501 goes, my guess is that, for works that are otherwise out of copyright,
502 an Urtext is copyright to the person who reconstructed it, as a
503 derived work from the editions s/he consulted. If the edition is
504 created directly from a facsimile, as would be the case for most
505 Urtext editions of music, then the amount of new (copyright) material
508 A critical edition is an edition that is designed for critical
509 study of a text. It'll usually have lots of footnotes, alternative
510 readings, possible realisations of bass parts and harmonies, etc. It
511 aims to elucidate the author's original intentions, as opposed to
512 reproduce exactly what was written. The critical apparatus will be
513 copyright to its author.
515 A playing edition is one that has been edited for modern usage.
516 It'll have fewer or no alternative readings, it'll be in modern
517 notation, it may have additional editorial marks (phrase marks, slurs,
518 etc.) will often have a fully realised basso continuo part (if oone
519 was present in the original) and may have had key changes, time
520 signature changes, time compression (original in 4/1, playing edition
521 in 4/4, for example, with all semibreves replaced with crotchets)
522 Copyright is in the arranger/editor.
524 @subsubsection How does copyright for sheet music work? Can I enter and spread my newly bought Bach urtext?
526 Silas S. Brown <ssb22@@hermes.cam.ac.uk>:
530 There are several aspects to sheet music copyright:
532 1. The music itself - copyright for the composer's life plus 70 years (so
533 not applicable to Bach).
535 2. If the music is an arrangement, then the arranger holds copyright on
536 that arrangement. However, you can produce your own arrangement using
537 that arrangement as a reference point. Obviously your arrangement must be
538 sufficently different to be called your own arrangement - you need to do
539 more than change one note!
541 3. In some countries, the same applies for editions. This could be
542 relevant to the Bach example. If a modern person has edited the music,
543 then they hold the copyright on the edition. This does not stop you from
544 removing the editorial features - remove all editorial slurs, phrasemarks,
545 ornaments etc and only leave those that you know to be original. You can
546 then add some of your own if you want to be your own editor.
548 4. If there are lyrics, then the lyricist also holds copyright. This
549 does not stop you from using the music without the lyrics if it is
550 otherwise out of copyright.
552 5. The copyright of the printed page is held by the publisher for 30
553 years after printing (25 in some countries). This stops you from
554 photocopying (unless it's "fair use" eg. you're partially sighted and need
555 to enlarge the music) or otherwise reproducing the typesetting that is
556 used on it. But the copyright is only held over the typesetting work, not
557 the music itself. Since Mudela specifies the notes, independently of any
558 typesetting work that went into your reference copy, you are not
559 duplicating any of the publisher's work.
561 6. If you want to violate copyright, there are two main cases where you
562 may do so: fair use, and with permission. The former is rather fuzzily
563 defined, but it includes such things as including small extracts of a
564 score in a critique, and making a large print or Braille copy for a blind
565 or partially-sighted performer (many people argue that in this case it
566 should always be kept with the original copy and/or destroyed after it is
567 no longer needed). The latter is obvious: You can always write to the
568 composer, arranger, editor, lyricist or publisher in subsubsection and ask if
569 you can do whatever it is you're trying to do. Some will respond more
570 readily than others, but anything that they say will override any copying
571 restrictions imposed on you.
573 References - best one I know is the UK-based Performing Right Society,
574 @uref{http://www.prs.co.uk/} (especially "membership") and their links to other
575 international equivalents.
578 Werner Lemberg @email{wl@@gnu.org} writes:
582 Typesetting [at least in Austria or Germany, but not in France] [..]
583 isn't copyrighted -- typesetting is a handcraft, not an
586 What's copyrighted in an Urtext edition is the editor's comment or
587 the revision remarks, cadenzas added by the editor, etc.
589 Urtext editions per se are @emph{not} copyrighted -- if you print
590 exactly what the composer has written, how can there some copyright be
591 added? Copyrighted are usually only the `Critical notes', the foreword,
592 and the cadenzas some editors have added.
594 This means that the `Photocopying forbidden' sign in many scores is not
595 always correct for e.g. J.S. Bach -- you are allowed to copy the pages
596 which don't contain editorial stuff which is probably copyrighted.
598 A very unfortunate situation for the publishers.
603 Glen Prideaux, @email{glenprideaux@@MailAndNews.com}:
606 One has to be careful. In Australia typesetting IS covered by copyright, but
607 only for 25 years (as opposed to 50 years from the death of the
608 author/composer/artist for virtually any other copyright). If the
609 typesetting originates in a country that does not protect typesetting then
610 there may indeed be no copyright protection available to control the use of
614 Juergen Reuter @email{reuterj@@ira.uka.de}
616 [More information can be had at: ]
618 @uref{http://lcweb.loc.gov/copyright/}
621 @uref{http://fairuse.stanford.edu/}
622 (meta site about copyright with many links to other resources)
624 @uref{http://host.mpa.org/crc.html}
625 (copyright from the viewpoint of the USA music publishers' association)
627 @uref{http://www.wipo.int}
628 (World Intellectual Property Organization (a UNO agency); with
629 information about international copyright)
633 See @uref{http://www.geocities.com/Vienna/Studio/1714/harpsichord.html}
634 for a summary of copyright relative to old music, also for the
635 expert forum for such subsubsections.
638 @node Windows32, Top, Copyright, FAQ - GNU LilyPond FAQs
641 @subsubsection I downloaded the windows32 port, and it doesn't match the website!
643 The website is usually made from the latest snapshots. Binary releases,
644 in particular the windows32 binaries, are only made every once in a while.
645 They may lag several versions behind the latest version.
647 @subsubsection But i want a native DOS/Windows-NT/95 port
649 Reconsider. Try Linux. It's fun!