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 Why is the documentation/website/etc. so lousy?
125 LilyPond development is moving quite fast, documentation will often lag
126 a bit behind. We must always make a choice between writing more
127 documentation, writing HTML, writing more code and answering email.
129 If you think you can make a correction, or devised a solution that
130 should be documented, please write it up, and us a diff.
132 @node Language- mudela, Do you support -, Documentation, FAQ - GNU LilyPond FAQs
133 @section Language: mudela
135 @subsubsection Why do I have to type the accidentals to the note if I
136 specified them in the keysignature?
145 Independently of how it was written and what the current key was, you
146 would say that you are playing and reading "two C-sharp" notes, so you
147 have to enter C-sharp twice.
149 @subsubsection What is @code{cis} anyway
151 @code{cis} is the dutch naming for C-sharp. The notes are named
152 a, b,.., g. The suffix -is means sharp, and -es flat. This system is
153 common in a number of languages (such as swedish, dutch, german.)
154 Certain other languages (such as English, French and Italian) just add
155 the word for "sharp" to the notename.
157 We chose the Dutch system, because we're dutch. You are free to chose
158 whatever names you like; they are user definable.
160 @subsubsection Why are [] around the notes, and () inbetween?
162 [] designate beams, a note can only be in one beam at the same
163 time. () is a slur, which connects notes. You need to be able to
171 @subsubsection I want to insert some TeX commands.
173 You shouldn't: it's against LilyPond philosophy to have typesetting
174 commands in the mudela source. Moreover, this would be difficult.
175 LilyPond uses TeX like a glorified output engine: the output consists
176 of (x,y) positions and symbols. You can only sensibly do TeX stuff in
177 the symbol string. You can access the symbol string easily for some
178 symbols (notably lyrics and @code{^"text"} commands).
180 @node Do you support -, How do I -, Language- mudela, FAQ - GNU LilyPond FAQs
181 @section Do you support ...
183 @subsubsection Do you support pop songs (chords, single staff, lyrics)?
185 Yes, see the @file{twinkle-pop} example.
187 @subsubsection Do you support guitar chord diagrams?
189 No. Go ahead and send a patch.
191 We ourselves don't play guitar, and don't know the fine points of this
192 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 subsubsection 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{staffLineLeading} 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
230 < \melodic \type Staff = "treble" \trebleMelody
231 \lyric \type Lyrics = "tlyrics" \trebtext
232 \type Staff = "bass" \melodic \bassMelody
233 \lyric \type Lyrics = "blyrics" \basstext
240 @subsubsection How do I put more than one marking on a note.
249 or use spacing-notes to put markings at different horizontal positions
253 @{ s4\ff s4^"text" s4-\marcato s4 @}
258 This also works for crescendi, eg,
267 @subsubsection How do I combine multiple pieces into one document
269 There are several solutions:
279 produces one combined @file{foo.dvi}
280 @item make a toplevel @file{.ly} file that contains al pieces:
290 @item make a hybrid TeX/LilyPond @file{.doc} document (see the
291 @file{Documentation/tex} directory).
294 For the first two solutions, you will need to move @code{\header} info
295 in each individual piece from toplevel into the @code{\paper} block.
297 There are several examples in the @file{mutopia} directory.
299 @subsubsection How do I get bar numbers?
301 See @file{input/test/bar-scripts.ly}.
303 @subsubsection How do I change the tagline 'Lily was here'
305 In the @code{\header} field, add a @code{tagline} entry, eg
308 tagline="Typeset by GNU LilyPond"
312 to get a bit less frivolous tagging.
314 @node Development, Running, How do I -, FAQ - GNU LilyPond FAQs
317 @subsubsection Could you implement feature XXXX? It is really easy, just extend the syntax to allow YYYY!
319 In general finding a cute syntax (such as YYYY) isn't very hard. The
320 complicated issue how to adapt the internals to do XXXX. The parser is
321 really a simple front end to the complicated internals.
323 @subsubsection Can I join in on LilyPond development? How do I do this?
325 Yes, we do frequent releases, you are welcome to send in a patch or do
326 suggestions. Join the list @email{gnu-music-discuss@@gnu.org} to
330 @subsubsection Is there a GUI frontend? Should I start building one?
332 LilyPond currently has no graphical interface. We (LilyPond authors)
333 don't feel the need to write a GUI, but several others do:
335 Matthew Hiller has extended Midiscore and Koobase to handle mudela.
336 Check out @uref{http://zoo.cs.yale.edu/~meh25/}. He is now working on
337 `Denemo', a GTK based notation program (which is still being developed).
339 Federico Mena-Quintero and Elliot Lee of RedHat Advanced Development
340 labs have plans to write a GNOME based Music notation program. However,
341 there is no code, only plans.
343 Chris Cannam is working a rewrite of Rosegarden. The new design should
344 be more modular, and could conceivably be used to output
345 mudela. However, the not much seems to have happened the past year. See
346 @uref{http://www.all-day-breakfast.com/rosegarden/development.html}.
349 @subsubsection I want to implement XXXX! How should I do this?
351 Your best bet of getting us to include code, is to present it as a
352 "fait accompli", i.e., to send a patch to the mailing list.
354 Please use the diff command to generate a patch, and don't send complete
355 files, even if the diff is larger than the whole file.
357 Don't forget to put your name and e-mail address in the file
358 @file{Documentation/topdocs/AUTHORS.texi}, or you won't get credits
362 @subsubsection Your make system does not adhere to GNU coding standards, could you please fix it?
364 No. We have evaluated the standard GNU combination for compiling
365 programs (autoconf, automake, libtool) and found to be inadequate for
368 @subsubsection gdb crashes when I debug!
370 Upgrade/downgrade to 4.17.
372 @node Running, Copyright, Development, FAQ - GNU LilyPond FAQs
375 @subsubsection I use dvilj4, and there are lots of warning messages for the printing
377 You should use dvips and ghostscript to print the @code{dvi} output: the
378 slurs and beams are PS @code{\special} commands.
381 subsubsection My symbols are all messed up after I upgraded, I get the wrong symbols and dvi-checksum errors!
383 We obviously mucked with the fonts in the upgrade. Remove @emph{all}
384 previous fonts, including the @file{.pk} and @file{.tfm} fonts in
385 @file{/var/lib/texmf}. A script automating this has been included, see
386 @file{buildscripts/clean-fonts.sh}.
388 @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.
390 Mats Bengtsson <mats.bengtsson@@s3.kth.se> writes:
392 The simple solution used by Anthony Fok in the Debian distribution of
393 Lilypond is to link the mf/ directory to
394 /usr/lib/texmf/fonts/source/public/lilypond Depending on what
395 distribution of teTeX and Linux you have installed, there might also
396 be other places like /usr/local/lib/texmf/fonts/source/public/lilypond
397 or /var/spool/texmf//fonts/source/public/lilypond
399 Wherever you put it, don't forget to run mktexlsr (or texhash for
400 older installations) afterwards, so that TeX will find the files.
401 Also, don't forget to remove all old .tfm and .*pk files when the font
402 is updated (as it will be in version 1.1.40, for example).
404 @subsubsection Are there scalable versions of the font?
406 Yes, they are type-3 fonts. In the @file{mf/}
413 in the mf/ subdirectory. This will also make @file{mfplain} for metapost.
414 The @file{pfa}s will be in the subdirectory @file{out/}.
416 @subsubsection How does PS output work?
420 Generate the PostScript Type-3 fonts.
422 Run lilypond with option @code{-f ps}:
429 @item To view the @file{.ps} output with GhostView, set GS_FONTPATH to the
430 directory containing the @file{pfa}s. In the source tree, this is @file{mf/out/}.
432 i.e. do something like:
435 export GS_FONTPATH=$HOME/usr/src/lilypond/mf/out
442 Direct PS output is still experimental. For creating nice looking ps
443 output, use TeX and @code{dvips}.
446 @subsubsection The beams and slurs are gone if use the XDvi magnifying glass!?
448 The beams and slurs are done in PostScript. XDvi doesn't show
449 PostScript in the magnifying glass. Complain to the XDvi maintainers.
452 @subsubsection A lot of musical stuff doesn't make it to the MIDI file, eg. dynamics, articulation, etc.
454 The MIDI output was originally put in as a proof that MIDI could be
455 done, and as a method of proof"reading" the input. The MIDI support
456 is by no means finished. Patches appreciated.
458 @node Copyright, Windows32, Running, FAQ - GNU LilyPond FAQs
461 @subsubsection What is Urtext? Critical Edition?
465 It may be translated best as `that what the composer intended to tell
468 Peter Chubb <peterc@@aurema.com> writes:
470 An Urtext is a reconstruction of the earliest form of a text,
471 including mistakes the original author wrote. Where there is no
472 available facsimile of the original, creating this can involve some
473 inspired detective work (in comparing various later editions and
474 trying to deduce what the original form was). As far as copyright
475 goes, my guess is that, for works that are otherwise out of copyright,
476 an Urtext is copyright to the person who reconstructed it, as a
477 derived work from the editions s/he consulted. If the edition is
478 created directly from a facsimile, as would be the case for most
479 Urtext editions of music, then the amount of new (copyright) material
482 A critical edition is an edition that is designed for critical
483 study of a text. It'll usually have lots of footnotes, alternative
484 readings, possible realisations of bass parts and harmonies, etc. It
485 aims to elucidate the author's original intentions, as opposed to
486 reproduce exactly what was written. The critical apparatus will be
487 copyright to its author.
489 A playing edition is one that has been edited for modern usage.
490 It'll have fewer or no alternative readings, it'll be in modern
491 notation, it may have additional editorial marks (phrase marks, slurs,
492 etc.) will often have a fully realised basso continuo part (if oone
493 was present in the original) and may have had key changes, time
494 signature changes, time compression (original in 4/1, playing edition
495 in 4/4, for example, with all semibreves replaced with crotchets)
496 Copyright is in the arranger/editor.
498 @subsubsection How does copyright for sheet music work? Can I enter and spread my newly bought Bach urtext?
500 Silas S. Brown <ssb22@@hermes.cam.ac.uk>:
504 There are several aspects to sheet music copyright:
506 1. The music itself - copyright for the composer's life plus 70 years (so
507 not applicable to Bach).
509 2. If the music is an arrangement, then the arranger holds copyright on
510 that arrangement. However, you can produce your own arrangement using
511 that arrangement as a reference point. Obviously your arrangement must be
512 sufficently different to be called your own arrangement - you need to do
513 more than change one note!
515 3. In some countries, the same applies for editions. This could be
516 relevant to the Bach example. If a modern person has edited the music,
517 then they hold the copyright on the edition. This does not stop you from
518 removing the editorial features - remove all editorial slurs, phrasemarks,
519 ornaments etc and only leave those that you know to be original. You can
520 then add some of your own if you want to be your own editor.
522 4. If there are lyrics, then the lyricist also holds copyright. This
523 does not stop you from using the music without the lyrics if it is
524 otherwise out of copyright.
526 5. The copyright of the printed page is held by the publisher for 30
527 years after printing (25 in some countries). This stops you from
528 photocopying (unless it's "fair use" eg. you're partially sighted and need
529 to enlarge the music) or otherwise reproducing the typesetting that is
530 used on it. But the copyright is only held over the typesetting work, not
531 the music itself. Since Mudela specifies the notes, independently of any
532 typesetting work that went into your reference copy, you are not
533 duplicating any of the publisher's work.
535 6. If you want to violate copyright, there are two main cases where you
536 may do so: fair use, and with permission. The former is rather fuzzily
537 defined, but it includes such things as including small extracts of a
538 score in a critique, and making a large print or Braille copy for a blind
539 or partially-sighted performer (many people argue that in this case it
540 should always be kept with the original copy and/or destroyed after it is
541 no longer needed). The latter is obvious: You can always write to the
542 composer, arranger, editor, lyricist or publisher in subsubsection and ask if
543 you can do whatever it is you're trying to do. Some will respond more
544 readily than others, but anything that they say will override any copying
545 restrictions imposed on you.
547 References - best one I know is the UK-based Performing Right Society,
548 @uref{http://www.prs.co.uk/} (especially "membership") and their links to other
549 international equivalents.
552 Werner Lemberg @email{wl@@gnu.org} writes:
556 Typesetting [at least in Austria or Germany, but not in France] [..]
557 isn't copyrighted -- typesetting is a handcraft, not an
560 What's copyrighted in an Urtext edition is the editor's comment or
561 the revision remarks, cadenzas added by the editor, etc.
563 Urtext editions per se are @emph{not} copyrighted -- if you print
564 exactly what the composer has written, how can there some copyright be
565 added? Copyrighted are usually only the `Critical notes', the foreword,
566 and the cadenzas some editors have added.
568 This means that the `Photocopying forbidden' sign in many scores is not
569 always correct for e.g. J.S. Bach -- you are allowed to copy the pages
570 which don't contain editorial stuff which is probably copyrighted.
572 A very unfortunate situation for the publishers.
577 Glen Prideaux, @email{glenprideaux@@MailAndNews.com}:
580 One has to be careful. In Australia typesetting IS covered by copyright, but
581 only for 25 years (as opposed to 50 years from the death of the
582 author/composer/artist for virtually any other copyright). If the
583 typesetting originates in a country that does not protect typesetting then
584 there may indeed be no copyright protection available to control the use of
588 Juergen Reuter @email{reuterj@@ira.uka.de}
590 [More information can be had at: ]
592 @uref{http://lcweb.loc.gov/copyright/}
595 @uref{http://fairuse.stanford.edu/}
596 (meta site about copyright with many links to other resources)
598 @uref{http://host.mpa.org/crc.html}
599 (copyright from the viewpoint of the USA music publishers' association)
601 @uref{http://www.wipo.int}
602 (World Intellectual Property Organization (a UNO agency); with
603 information about international copyright)
607 See @uref{http://www.geocities.com/Vienna/Studio/1714/harpsichord.html}
608 for a summary of copyright relative to old music, also for the
609 expert forum for such subsubsections.
612 @node Windows32, Top, Copyright, FAQ - GNU LilyPond FAQs
615 @subsubsection I downloaded the windows32 port, and it doesn't match the website!
617 The website is usually made from the latest snapshots. Binary releases,
618 in particular the windows32 binaries, are only made every once in a while.
619 They may lag several versions behind the latest version.
621 @subsubsection But i want a native DOS/Windows-NT/95 port
623 Reconsider. Try Linux. It's fun!