1 \input texinfo @c -*-texinfo-*-
3 @settitle FAQ - GNU LilyPond FAQs
8 * Miscellaneous:: Miscellaneous
9 * Installing:: Installing
10 * Documentation:: Documentation
11 * Language- mudela:: Language- mudela
12 * Do you support -:: Do you support -
13 * How do I -:: How do I -
14 * Development:: Development
16 * Copyright:: Copyright
17 * Windows32:: Windows32
19 @chapter FAQ - GNU LilyPond FAQs
22 @node Miscellaneous, ,,top
23 @section Miscellaneous
25 @subsubsection HELP! I'm stuck!
27 Please read this document carefully. If you are still at loss, send
28 your questions to the @strong{mailing list}, and not to authors
31 Note: relative paths are meant to be relative to the source directory
33 @node Installing,, ,top
37 @subsubsection If I install the .exe file on my DOS/windows 3.11 machine, it doesn't work
39 The NT port is done with the Cygnus GNU/Windows32 port of the GNU utils.
40 It does @emph{not} work with windows 3.x; you need Windows-NT (95/98?).
42 @subsubsection Where is guile-config
44 Old RedHat RPMS don't include guile-config. You need guile-config as it
45 was produced during the RPM build run. Build the RPM from source
46 (@file{.src.rpm}), and use the guile-config that is in
47 @file{/usr/src/redhat/BUILD/guile-1.3/guile-config/}.
49 @subsubsection I get all kinds of errors while compiling @file{parser.cc}
51 LilyPond uses features of bison version 1.25. Please confirm that
52 you are using a version 1.25 or better, that is @strong{GNU} bison
53 @strong{1.25}. Don't forget to do "make clean" after installing it. Don't
54 forget to remove the stale @file{bison.simple} as well.
56 If the problem persists, then please send a bug report to the mailing list.
58 @subsubsection I upgraded by applying a patch, and now my configure/build breaks.
60 Patches don't include automatically generated files, i.e.
61 @file{configure} and files generated by @file{configure}. Regenerate them
71 @subsubsection Is there an emacs mode?
73 Yes. It is included with the source archive as @file{lilypond-mode.el}.
74 If you have an RPM it is in @file{/usr/doc/lilypond-X/}. You have to
77 @subsubsection How do I create the @file{.tfm} files?
79 You don't. The @file{.tfm} files should be generated automatically by
80 Metafont when you run TeX. Check your TeX installation, or ask
81 your local TeX guru. The supplied @file{.afm} files are intended to
82 be used by LilyPond, not by any other programs.
84 @node Documentation,, ,top
85 @section Documentation
87 @subsubsection What a sober website/manual you have there!
89 LilyPond development is moving fast, so the documentation will often be out
90 of date. But don't hesitate to point out inaccuracies. Whip up your
91 mail reader and write to the mailing list.
93 @subsubsection Please take me off your mailing list, I get so much mail!
95 Don't ask Han-wen, don't ask David. Instead, read about
96 @uref{../../index.html#mailing-lists, the mailing lists} here.
100 @node Language- mudela,, ,top
101 @section Language: mudela
103 @subsubsection Why do I have to type the accidentals to the note if I
104 specified them in the keysignature?
113 Independently of how it was written and what the current key was, you
114 would say that you are playing and reading "two C-sharp" notes, so you
115 have to enter C-sharp twice.
117 @subsubsection What is @code{cis} anyway
119 @code{cis} is the dutch naming for C-sharp. The notes are named
120 a, b,.., g. The suffix -is means sharp, and -es flat. This system is
121 common in a number of languages (such as swedish, dutch, german.)
122 Certain other languages (such as English, French and Italian) just add
123 the word for "sharp" to the notename.
125 We chose the Dutch system, because we're dutch. You are free to chose
126 whatever names you like; they are user definable.
128 @subsubsection Why are [] around the notes, and () inbetween?
130 [] designate beams, a note can only be in one beam at the same
131 time. () is a slur, which connects notes. You need to be able to
139 @subsubsection I want to insert some TeX commands.
141 You shouldn't: it's against LilyPond philosophy to have typesetting
142 commands in the mudela source. Moreover, this would be difficult.
143 LilyPond uses TeX like a glorified output engine: the output consists
144 of (x,y) positions and symbols. You can only sensibly do TeX stuff in
145 the symbol string. You can access the symbol string easily for some
146 symbols (notably lyrics and @code{^"text"} commands).
148 @node Do you support -,, ,top
149 @section Do you support ...
151 @subsubsection Do you support pop songs (chords, single staff, lyrics)?
153 Yes, see the @file{twinkle-pop} example.
155 @subsubsection Do you support guitar chord diagrams?
157 No. We ourselves don't play guitar, and don't know the fine points of
158 this notation. We would welcome anyone who could give this a try.
160 @subsubsection Do you support TAB notation?
162 No. The same as for the previous question goes.
165 @subsubsection Do you support multiple staff-sizes?
167 Yes. At this time you can choose between 11, 13, 16, 19, 20, 23 and 20
168 pt staff-size. Use the @code{staffSpace} property for setting the
169 size of the staff, and @code{fontSize} for setting the size of the
172 @subsubsection Do you support Gregorian chant notation?
177 @subsubsection Do you support grace notes?
179 Yes. See @file{input/test/grace.ly}.
181 @node How do I -,, ,top
182 @section How do I ....
184 @subsubsection How do I change the TeX layout?
186 See @file{lilyponddefs.tex}, it has some comments. Or use @file{ly2dvi}.
188 @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!
190 You change the order lyrics and staves. You have to name all
191 staves (lyric and melodic), otherwise they will end up in the same
195 < \melodic \type Staff = "treble" \trebleMelody
196 \lyric \type Lyrics = "tlyrics" \trebtext
197 \type Staff = "bass" \melodic \bassMelody
198 \lyric \type Lyrics = "blyrics" \basstext
205 @subsubsection How do I put more than one marking on a note.
214 or use spacing-notes to put markings at different horizontal positions
218 @{ s4\ff s4^"text" s4-\marcato s4 @}
223 This also works for crescendi, eg,
232 @subsubsection How do I combine multiple pieces into one document
234 There are several solutions:
244 produces one combined @file{foo.dvi}
245 @item make a toplevel @file{.ly} file that contains al pieces:
255 @item make a hybrid TeX/LilyPond @file{.doc} document (see the
256 @file{Documentation/tex} directory).
259 For the first two solutions, you will need to move @code{\header} info
260 in each individual piece from toplevel into the @code{\paper} block.
262 There are several examples in the @file{mutopia} directory.
264 @subsubsection How do I get bar numbers?
266 See @file{input/test/bar-scripts.ly}.
268 @subsubsection How do I change the tagline 'Lily was here'?
270 In the @code{\header} field, add a @code{tagline} entry, e.g.
273 tagline="Typeset by GNU LilyPond"
277 @subsubsection Can I make blank manuscript paper with LilyPond?
279 Theoretically, yes but it is easier to do with (La)TeX. This LaTeX file
280 will do the trick for you:
284 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
286 % Mats Bengtsson, 18/5 2000
287 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
288 \documentclass[a4paper]@{article@}
290 \usepackage@{ifthen@}
291 \usepackage[noheadfoot,hmargin=15mm,vmargin=20mm]@{geometry@}
295 \newcounter@{staffnumber@}
296 \newlength@{\interstaffline@}
298 \newcommand@{\drawline@}@{\hbox@{\rule@{\textwidth@}@{0.5pt@}@}
299 \nointerlineskip\vskip\interstaffline\nointerlineskip@}
301 \newcommand@{\printstaff@}@{\vfill
302 \vbox@{\drawline\drawline\drawline\drawline\drawline@}
306 \typeout@{@}\typeout@{@}
307 \typein[\staffsize]@{Type in the staff size (20pt is a common value):@}
308 \setlength@{\interstaffline@}@{\staffsize@}
309 \setlength@{\interstaffline@}@{.25\interstaffline@}
311 \typein[\num]@{Type in the number of staffs:@}
312 \setcounter@{staffnumber@}@{\num@}
314 \mbox@{@} % To get a starting point for the \vfill
315 \whiledo@{\value@{staffnumber@}>0@}@{%
316 \printstaff \addtocounter@{staffnumber@}@{-1@}@}
322 @node Development,, ,top
325 @subsubsection Could you implement feature XXXX? It is really easy, just extend the syntax to allow YYYY!
327 In general finding a cute syntax (such as YYYY) isn't very hard. The
328 complicated issue how to adapt the internals to do XXXX. The parser is
329 really a simple front end to the complicated internals.
331 @subsubsection Can I join in on LilyPond development? How do I do this?
333 Yes, we do frequent releases, you are welcome to send in a patch or do
334 suggestions. Join the list @email{gnu-music-discuss@@gnu.org} to
338 @subsubsection Is there a GUI frontend? Should I start building one?
340 LilyPond currently has no graphical interface. We (LilyPond authors)
341 don't feel the need to write a GUI, but several others do:
343 Matthew Hiller has extended Midiscore and Koobase to handle mudela.
344 Check out @uref{http://zoo.cs.yale.edu/~meh25/}. He is now working on
345 `Denemo', a GTK based notation program (which is still being developed).
347 Federico Mena-Quintero and Elliot Lee of RedHat Advanced Development
348 labs have plans to write a GNOME based Music notation program. However,
349 there is no code, only plans.
351 Chris Cannam is working a rewrite of Rosegarden. The new design should
352 be more modular, and could conceivably be used to output
353 mudela. However, the not much seems to have happened the past year. See
354 @uref{http://www.all-day-breakfast.com/rosegarden/development.html}.
357 @subsubsection I want to implement XXXX! How should I do this?
359 Your best bet of getting us to include code, is to present it as a
360 "fait accompli", i.e., to send a patch to the mailing list.
362 Please use the diff command to generate a patch, and don't send complete
363 files, even if the diff is larger than the whole file.
365 Don't forget to put your name and e-mail address in the file
366 @file{Documentation/topdocs/AUTHORS.texi}, or you won't get credits
370 @subsubsection Your make system does not adhere to GNU coding standards, could you please fix it?
372 No. We have evaluated the standard GNU combination for compiling
373 programs (autoconf, automake, libtool) and found to be inadequate for
376 @subsubsection How do I inspect @code{String}s and @code{SCM} values in GDB?
378 Use the following command definitions, which can be put in
383 print $arg0->strh_.data->data_byte_p_
387 call gh_display($arg0)
392 @subsubsection GDB crashes when I debug!
394 Upgrade/downgrade to 4.17.
399 @subsubsection Correcting errors is so tedious. Is there a better way?
401 As of 1.3.73, lilypond provides support for the xdvi @code{src:}
402 special. This can be used with Xdvik (22.16 or better) and xdvi (22.28
403 or better) to go to the place in the input that corresponds to a symbol
404 in the output: click on the note, and your editor jumps to the place
409 Decide if you want column positioning, and edit @file{lily.scm}
410 according to the comments at the function @code{define-origin}.
414 Put this in @file{~/.emacs}:
419 For column positioning, apply @uref{this
420 patch,http://www.cs.uu.nl/~hanwen/software/emacsclient-column} to
421 @code{emacsclient.c} and @code{server.el}. Stick the compiled
422 emacsclient into a bin directory, and put @code{server.el} into a elisp
423 directory (eg. @file{~/usr/share/emacs/}). Add the following to your
424 @file{.emacs} init file, before invoking server-start.
426 (setq load-path (cons (concat (getenv "HOME") "/usr/share/emacs")
432 Warning: @uref{Xdvik,ftp://ftp.cs.uu.nl/pub/tex-archive/dviware/xdvik/},
433 which is shipped with most TeX distributions, doesn't work very well for
434 src specials. You're better off using plain xdvi.
436 xdvi -srcmode -srcvisibility output.dvi
439 Click control-mouse button 2 for making emacs jump to the appropriate place.
441 For column positioning you must install this @uref{patch,
442 http://www.cs.uu.nl/~hanwen/software/xdvik-src} to make Xdvik emit
443 column numbers. Add the command line option @code{-srceditorcommand
444 "emacsclient --no-wait +%l:%c %f"}
448 @uref{Xdvi,ftp://ftp.math.berkeley.edu/pub/Software/TeX/xdvi.tar.gz} has
449 better support for src specials. Apply @uref{this patch,
450 http://www.cs.uu.nl/~hanwen/software/xdvi-src}. Before starting, set the
451 environment variable @code{XEDITOR} to @code{"emacsclient --no-wait +%d
452 %s"}. When viewing, control-mousebutton 1 will take you to the correct
453 line/column. Control-mousebutton 2 will show all clickable boxes.
457 dvips will complain about the specials, but the complaints are harmless.
460 @subsubsection I use dvilj4, and there are lots of warning messages for the printing
462 You should use dvips and ghostscript to print the @code{dvi} output: the
463 slurs and beams are PS @code{\special} commands.
466 @subsubsection My symbols are all messed up after I upgraded, I get the wrong symbols and dvi-checksum errors!
468 We obviously mucked with the fonts in the upgrade. Remove @emph{all}
469 previous fonts, including the @file{.pk} and @file{.tfm} fonts in
470 @file{/var/lib/texmf}. A script automating this has been included, see
471 @file{buildscripts/clean-fonts.sh}.
473 @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.
475 Mats Bengtsson <mats.bengtsson@@s3.kth.se> writes:
477 The simple solution used by Anthony Fok in the Debian distribution of
478 Lilypond is to link the mf/ directory to
479 /usr/lib/texmf/fonts/source/public/lilypond Depending on what
480 distribution of teTeX and Linux you have installed, there might also
481 be other places like /usr/local/lib/texmf/fonts/source/public/lilypond
482 or /var/spool/texmf//fonts/source/public/lilypond
484 Wherever you put it, don't forget to run mktexlsr (or texhash for
485 older installations) afterwards, so that TeX will find the files.
486 Also, don't forget to remove all old .tfm and .*pk files when the font
487 is updated (as it will be in version 1.1.40, for example).
489 @subsubsection Are there scalable versions of the font?
491 Yes, they are type-3 fonts. In the @file{mf/}
498 in the mf/ subdirectory. This will also make @file{mfplain} for metapost.
499 The @file{pfa}s will be in the subdirectory @file{out/}.
501 @subsubsection How does PS output work?
505 Generate the PostScript Type-3 fonts.
507 Run lilypond with option @code{-f ps}:
514 @item To view the @file{.ps} output with GhostView, set GS_FONTPATH to the
515 directory containing the @file{pfa}s. In the source tree, this is @file{mf/out/}.
517 i.e. do something like:
520 export GS_FONTPATH=$HOME/usr/src/lilypond/mf/out
527 Direct PS output is still experimental. For creating nice looking ps
528 output, use TeX and @code{dvips}.
531 @subsubsection The beams and slurs are gone when using the XDvi magnifying glass!?
533 Various dynamic symbols, such as beams, crescendi, slurs are done in
534 PostScript. XDvi doesn't show PostScript in the magnifying glass.
535 Complain to the XDvi maintainers.
538 @subsubsection Beams, slurs and crescendi are not displayed at all!
540 See previous answer. XDvi uses GhostScript for displaying PostScript,
541 check that you have GhostScript installed. If you use a different
542 DVI viewer, check if it will display embedded PostScript. Don't worry,
543 the symbols should appear on the printout.
545 @subsubsection A lot of musical stuff doesn't make it to the MIDI file, eg. dynamics, articulation, etc.
547 The MIDI output was originally put in as a proof that MIDI could be
548 done, and as a method of proof"reading" the input. The MIDI support
549 is by no means finished. Patches appreciated.
551 @node Copyright,, ,top
554 @subsubsection What is Urtext? Critical Edition?
558 It may be translated best as `that what the composer intended to tell
561 Peter Chubb <peterc@@aurema.com> writes:
563 An Urtext is a reconstruction of the earliest form of a text,
564 including mistakes the original author wrote. Where there is no
565 available facsimile of the original, creating this can involve some
566 inspired detective work (in comparing various later editions and
567 trying to deduce what the original form was). As far as copyright
568 goes, my guess is that, for works that are otherwise out of copyright,
569 an Urtext is copyright to the person who reconstructed it, as a
570 derived work from the editions s/he consulted. If the edition is
571 created directly from a facsimile, as would be the case for most
572 Urtext editions of music, then the amount of new (copyright) material
575 A critical edition is an edition that is designed for critical
576 study of a text. It'll usually have lots of footnotes, alternative
577 readings, possible realisations of bass parts and harmonies, etc. It
578 aims to elucidate the author's original intentions, as opposed to
579 reproduce exactly what was written. The critical apparatus will be
580 copyright to its author.
582 A playing edition is one that has been edited for modern usage.
583 It'll have fewer or no alternative readings, it'll be in modern
584 notation, it may have additional editorial marks (phrase marks, slurs,
585 etc.) will often have a fully realised basso continuo part (if oone
586 was present in the original) and may have had key changes, time
587 signature changes, time compression (original in 4/1, playing edition
588 in 4/4, for example, with all semibreves replaced with crotchets)
589 Copyright is in the arranger/editor.
591 @subsubsection How does copyright for sheet music work? Can I enter and spread my newly bought Bach urtext?
593 Silas S. Brown <ssb22@@hermes.cam.ac.uk>:
597 There are several aspects to sheet music copyright:
599 1. The music itself - copyright for the composer's life plus 70 years (so
600 not applicable to Bach).
602 2. If the music is an arrangement, then the arranger holds copyright on
603 that arrangement. However, you can produce your own arrangement using
604 that arrangement as a reference point. Obviously your arrangement must be
605 sufficently different to be called your own arrangement - you need to do
606 more than change one note!
608 3. In some countries, the same applies for editions. This could be
609 relevant to the Bach example. If a modern person has edited the music,
610 then they hold the copyright on the edition. This does not stop you from
611 removing the editorial features - remove all editorial slurs, phrasemarks,
612 ornaments etc and only leave those that you know to be original. You can
613 then add some of your own if you want to be your own editor.
615 4. If there are lyrics, then the lyricist also holds copyright. This
616 does not stop you from using the music without the lyrics if it is
617 otherwise out of copyright.
619 5. The copyright of the printed page is held by the publisher for 30
620 years after printing (25 in some countries). This stops you from
621 photocopying (unless it's "fair use" eg. you're partially sighted and need
622 to enlarge the music) or otherwise reproducing the typesetting that is
623 used on it. But the copyright is only held over the typesetting work, not
624 the music itself. Since Mudela specifies the notes, independently of any
625 typesetting work that went into your reference copy, you are not
626 duplicating any of the publisher's work.
628 6. If you want to violate copyright, there are two main cases where you
629 may do so: fair use, and with permission. The former is rather fuzzily
630 defined, but it includes such things as including small extracts of a
631 score in a critique, and making a large print or Braille copy for a blind
632 or partially-sighted performer (many people argue that in this case it
633 should always be kept with the original copy and/or destroyed after it is
634 no longer needed). The latter is obvious: You can always write to the
635 composer, arranger, editor, lyricist or publisher in subsubsection and ask if
636 you can do whatever it is you're trying to do. Some will respond more
637 readily than others, but anything that they say will override any copying
638 restrictions imposed on you.
640 References - best one I know is the UK-based Performing Right Society,
641 @uref{http://www.prs.co.uk/} (especially "membership") and their links to other
642 international equivalents.
645 Werner Lemberg @email{wl@@gnu.org} writes:
649 Typesetting [at least in Austria or Germany, but not in France] [..]
650 isn't copyrighted -- typesetting is a handcraft, not an
653 What's copyrighted in an Urtext edition is the editor's comment or
654 the revision remarks, cadenzas added by the editor, etc.
656 Urtext editions per se are @emph{not} copyrighted -- if you print
657 exactly what the composer has written, how can there some copyright be
658 added? Copyrighted are usually only the `Critical notes', the foreword,
659 and the cadenzas some editors have added.
661 This means that the `Photocopying forbidden' sign in many scores is not
662 always correct for e.g. J.S. Bach -- you are allowed to copy the pages
663 which don't contain editorial stuff which is probably copyrighted.
665 A very unfortunate situation for the publishers.
670 Glen Prideaux, @email{glenprideaux@@MailAndNews.com}:
673 One has to be careful. In Australia typesetting IS covered by copyright, but
674 only for 25 years (as opposed to 50 years from the death of the
675 author/composer/artist for virtually any other copyright). If the
676 typesetting originates in a country that does not protect typesetting then
677 there may indeed be no copyright protection available to control the use of
681 Juergen Reuter @email{reuterj@@ira.uka.de}
683 [More information can be had at: ]
685 @uref{http://lcweb.loc.gov/copyright/}
688 @uref{http://fairuse.stanford.edu/}
689 (meta site about copyright with many links to other resources)
691 @uref{http://host.mpa.org/crc.html}
692 (copyright from the viewpoint of the USA music publishers' association)
694 @uref{http://www.wipo.int}
695 (World Intellectual Property Organization (a UNO agency); with
696 information about international copyright)
700 See @uref{http://www.geocities.com/Vienna/Studio/1714/harpsichord.html}
701 for a summary of copyright relative to old music, also for the
702 expert forum for such subsubsections.
705 @node Windows32,, ,top
708 @subsubsection I downloaded the windows32 port, and it doesn't match the website!
710 The website is usually made from the latest snapshots. Binary releases,
711 in particular the windows32 binaries, are only made every once in a while.
712 They may lag several versions behind the latest version.
714 @subsubsection But i want a native DOS/Windows-NT/95 port
716 Reconsider. Try Linux. It's fun!