Re: Sorry I figured it out
Jozsa Marton writes: With notepad (and some other Win apps) quotation marks can be used to save new file with an extension other than TXT: song.ly Then we should probably mention this problem and workaround in Getting Started. But we'll need to make another/extra page for windows users anyway when we have clickable .ly's. Jan. -- Jan Nieuwenhuizen [EMAIL PROTECTED] | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: parenthesized grace note
See http://lilypond.org/doc/v1.8/input/regression/out-www/collated-files.html#molecule-hacking.ly Mats [EMAIL PROTECTED] wrote: anyone have a method for putting parentheses around a grace note (other than building the whole thing with \markup)? specifically, i wish to have a parenthesized small notehead beside the main note of a trill, to indicate the trill note. yes, i have seen the discussion about placing an accidental above the trill sign; that is not what i'm looking for. thanks! -p ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Questions about guitar tablature support
Hello, First, congrats for all the new features in since 1.6, I am very impressed and my scores look a lot better. Since I'm a good tester for drums and guitar (I do all my music with lilypond) I have a few guitar tab questions: - Hammer/Tap/Pull-off support: in a guitar tab, you can do tapping, which is a technique consisting in not using your right hand to squeeze the string, but hit it at the wanted fret to produce a sound, or pull the string of of where it was pressed to let a lower pressed note sound. In guitar tablature this is usually done by having a H,T,P letter above the tablature number and having the notes slured. In the case of a Hammer, the note is slured from nothing. The way I do it now is with normal text on top of the note, but would be easier to have that as an articulation. - Unfretted notes: these are produced when you mute the string(s) with your left hand without actually pressing them at any fret, and picking them with your right hand, it produces a percussion sound. The actual note head and tablature head should be a cross (x) while you can still specify an approximate note for it for the musical stave. - Palm-mute: this is when you leave your hand laying slightly on the string while playing normally, it produces a mufled sound which is very commonly used. The notation is usually a P.M. sign under the first note, and a dashed line going from this sign until the last note that is palm-muted, thus making it possible to have whole sections of palm-mute. - glissandos to or from nowhere: in guitar tablature, you can have glissandos to no note, up and down. Right now in lilypond, if I want a glissando, I have to put a note to gliss to, or from, but in typical guitar tablature you are not bound to gliss exactly to or from an exact note, it is usually implied that the glissando should be done to or from the farthest place possible on the fretboard. - Harmonics: you can play a harmonic on a string by touching the string but not pressing it down the fret, at a specified position and then sqeazing it with your right hand. Typical notation is to specify normally where the string is touched by a number, and having the text harm. on top of it, while the note from the partition stave has a square head. You can also have artificial harmonics of two sorts, the first is when you need to press a tab with your left hand while tapping the wanted harmonic with your right hand. In this case the notation is to write the pressed tab normally, while having the harmonic tab between parethesis. The second kind is more complex and I haven't checked all my notations for consensus. Is there any plans to implement such things ? If yes, I will make all the research needed about exactly how it should look and all the special cases, and will provide all the info I can gather. Thanks. -- Stéphane Epardaud ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: papersize problem
The simple reason is that the ly2dvi script doesn't know about the legal and ledger paper sizes. I just tried to add the support but ran into a small problem; Would you expect a ledger paper to be used mainly in landscape or in portrait orientation? It turns out that dvips (that we use to convert .dvi to .ps files) expects ledger paper to be 17inch wide and 11inch high, i.e. in landscape orientation. Dvips uses 'tabloid' to denote 17'x11' paper used in portrait orientation. The same naming convention is described, for example, in http://groups.google.com/groups?q=paper+sizes+tabloidhl=enlr=ie=UTF-8oe=UTF-8selm=1995Jun8.104533.18767%40sei.cmu.edurnum=1 What do you think, should we rename 'ledger' to 'tabloid' or change the definitions in ledger-init.ly to correspond to landscape orientation? /Mats Peter Lutek wrote: greetings! on my installation of lilypond (1.8.0 on RedHat9), if i attempt to use papersize = legal or papersize = ledger, i get an ly2dvi warning saying legal or ledger is an invalid value. letter, a3, and a4 are all ok. ledger-init.ly , legal-init.ly , a3-init.ly , a4-init.ly , and letter-init.ly all exist and appear to have the same syntax. why do two of these size definitions not work? -p ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question
Thank you for your quick answer On Thu, 18 Sep 2003 22:41:53 -0300 Ricardo Kirkner [EMAIL PROTECTED] wrote: 1- How do you tell lilypond to typeset all brackets of equal lenghts (or at least not each bracket out of two on a different lenght). I don't know what you mean by this. Could you give an example? I that lily prints something like this (in ascii) | some notes | == 1 bracket | | | ||| | | but I would like to get something more like this |||||||| or at least something like this | | | | | | | | I hope this clarifies (at least a little) what I meant 2- How do you put some words before the Staff and get no errors in the process (i have tried to use the instrument property, but then lily claims the word is not an instrument - in this case Soprano, for example) Do you mean how do you name an instrument? I'm sure that's covered in the manual or examples, but here it is: \property Staff.instrument = #foo I have tried exactly that, but when I compile I get warnings about foo not being an instrument. I know it's just a warning, but I was wondering if it there is another way of doing this that doesn't produce warnings. thanks anyway ricardo ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: papersize problem
Mats == Mats Bengtsson [EMAIL PROTECTED] writes: Mats Would you expect a ledger paper to be used mainly in landscape or Mats in portrait orientation? It turns out that dvips (that we use to Mats convert .dvi to .ps files) expects ledger paper to be 17inch wide Mats and 11inch high, i.e. in landscape orientation. Dvips uses 'tabloid' Mats to denote 17'x11' paper used in portrait orientation. I think there's a case for both -- the usual way to use ledger would be to put letter pages two-up in booklet order, since it would be a pretty long line of music to read. I've thought about using tabloid to do the dowland part songs one to a spread. Legal is closer to the size Dowland's printer used, but it's enough smaller to be a problem. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (801) 365-6574 233 Broadway, Cambridge, MA 02139 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Debian (Sid) packages for Lilypond 1.9.6
Pedro Kroger [EMAIL PROTECTED] writes: It would be nice to have debs of lilypond-unstable for debian stable and testing I gave that a go (see http://afavant.elte.hu/~wferi/lilypond/index_orig.html) and also tried to contact Anthony with some suggestions to make this process easier, but never got a reply. Maybe I could try with your packages if you provided source debs. Feri. ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: papersize problem
You will still have support for both, since tabloid+landscape=ledger. /Mats Laura Conrad wrote: Mats == Mats Bengtsson [EMAIL PROTECTED] writes: Mats Would you expect a ledger paper to be used mainly in landscape or Mats in portrait orientation? It turns out that dvips (that we use to Mats convert .dvi to .ps files) expects ledger paper to be 17inch wide Mats and 11inch high, i.e. in landscape orientation. Dvips uses 'tabloid' Mats to denote 17'x11' paper used in portrait orientation. I think there's a case for both -- the usual way to use ledger would be to put letter pages two-up in booklet order, since it would be a pretty long line of music to read. I've thought about using tabloid to do the dowland part songs one to a spread. Legal is closer to the size Dowland's printer used, but it's enough smaller to be a problem. -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: papersize problem
yes, AFAIK common usage is tabloid for portrait (11x17) and ledger for landscape (17x11). since portrait is probably more generally useful, i would suggest switching 'ledger' to 'tabloid', and maintaining portrait orientation. of course, having both options available would be even better! :) -p Mats Bengtsson wrote: The simple reason is that the ly2dvi script doesn't know about the legal and ledger paper sizes. I just tried to add the support but ran into a small problem; Would you expect a ledger paper to be used mainly in landscape or in portrait orientation? It turns out that dvips (that we use to convert .dvi to .ps files) expects ledger paper to be 17inch wide and 11inch high, i.e. in landscape orientation. Dvips uses 'tabloid' to denote 17'x11' paper used in portrait orientation. The same naming convention is described, for example, in http://groups.google.com/groups?q=paper+sizes+tabloidhl=enlr=ie=UTF-8oe=UTF-8selm=1995Jun8.104533.18767%40sei.cmu.edurnum=1 What do you think, should we rename 'ledger' to 'tabloid' or change the definitions in ledger-init.ly to correspond to landscape orientation? /Mats Peter Lutek wrote: greetings! on my installation of lilypond (1.8.0 on RedHat9), if i attempt to use papersize = legal or papersize = ledger, i get an ly2dvi warning saying legal or ledger is an invalid value. letter, a3, and a4 are all ok. ledger-init.ly , legal-init.ly , a3-init.ly , a4-init.ly , and letter-init.ly all exist and appear to have the same syntax. why do two of these size definitions not work? -p ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Debian (Sid) packages for Lilypond 1.9.6
* Ferenc Wagner ([EMAIL PROTECTED]) wrote: It would be nice to have debs of lilypond-unstable for debian stable and testing I gave that a go (see http://afavant.elte.hu/~wferi/lilypond/index_orig.html) and also tried to contact Anthony with some suggestions to make this process easier, but never got a reply. Maybe I could try with your packages if you provided source debs. I just uploaded the sources to my site (lilypond_1.9.7-1.dsc and lilypond_1.9.7-1.tar.gz). There is no lilypond_1.9.7-1.diff because the original source tree is already debianised. They're apt-getable to. Put this in your sources.list: deb-src http://www.pedrokroeger.net/lilypond/ ./ them: apt-get update apt-get source lilypond Good luck! Pedro ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
No time signature
I need to typseset a piece with no time signature. I don't find in the manual telling me how to do it. I suspect I have to set \property to something, but WHAT? Thanks -- Pierre François (http://www.romanliturgy.org) Roemer Visscherstraat 46 NL-1054 EZ Amsterdam (Netherlands) + 31 20 616 58 46 ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: No time signature
On Fri, 19 Sep 2003 17:45:58 +0200 Pierre Fran [EMAIL PROTECTED] wrote: I need to typseset a piece with no time signature. I don't find in the manual telling me how to do it. Please see the section on invisible grobs in the manual. I highly recommend bookmarking http://mail.gnu.org/archive/html/lilypond-user/ since many questions have already been asked on this mailist; searching the archive can often result in getting an answer much faster than emailing here. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question
On Fri, 19 Sep 2003 09:14:45 -0300 Ricardo Kirkner [EMAIL PROTECTED] wrote: 1- How do you tell lilypond to typeset all brackets of equal lenghts (or at least not each bracket out of two on a different lenght). I don't know what you mean by this. Could you give an example? I that lily prints something like this (in ascii) | some notes | == 1 bracket Ah, I see. In North America, a bracket is normally called a bar. |||||||| You can force that behaviour by including invisible sixteenth notes in every bar. (or, if you use notes faster than a 16th, use invisible 32nds) However, unless your needs are quite special (such as producing a worksheet for students to fill in), I don't recommend doing this. LilyPond does a great job of spacing music beautifully. 2- How do you put some words before the Staff and get no errors in the process (i have tried to use the instrument property, but then lily claims the word is not an instrument - in this case Soprano, for example) Do you mean how do you name an instrument? I'm sure that's covered in the manual or examples, but here it is: \property Staff.instrument = #foo I have tried exactly that, but when I compile I get warnings about foo not being an instrument. I know it's just a warning, but I was wondering if it there is another way of doing this that doesn't produce warnings. Please provide an example and tell us what version you're using. Are you setting the midiInstrument property instead of instrument? Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Awkward Slur
On Wed, 17 Sep 2003 14:46:26 -0400 Will Oram [EMAIL PROTECTED] wrote: http://www.foxchange.com/~spamguy/misc_pictures/slursegment.jpg What's the best way to fix this? Ideally I'd like to make the slur bulge more and have the right end closer to the c4. I've looked through the documentation at http://www.lilypond.org/doc/v1.8/Documentation/user/out-www/lilypond- internals/Slur.html , but didn't get much out of it. control-points looks important, but I have no way of knowing what to do with it. I don't understand slurs either, but I'd just copy and paste that section a whole bunch of times, then tweak lots of slur properties and look at the results. Here's the options that I think you should play with first: attachment-offset beautiful slope-limit height-limit ratio control-points probably _would_ do it, but it looks as though you need to know quite a bit about how LilyPond's slur algorithms work in order to use it. IMO it's much easier to try setting #'beautiful to 0.01, 0.5, 1.5, 5.0, and 10.0. :) HTH, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question
Your Question 1: Historically it has been considerd a bad idea to keep the bar spacing the same between 'lines', presumably because it is wasy to lose track of which 'line' you are reading. Most music publishers/typesetters I have seen will actually go out their way to ensure the lengths are not the same. However, you can make certain adjustments using the \break command to tell Lilypond how many bars (brackets) you have on a line. Also you may notice the space allocated is influenced by the number of 'note positions'. So you could come close by having a set of 'invisible' 16th or 32nd notes in each bar and terminating each 'line' with a \break. Your Question 3: Suggestions: 1) Ask away. This is the only way the documentation writers will know what is frequently asked so they can adjust the documents based on popularity of questions. (I think you'll find that this is one of the friendlier mail lists around.) 2) Look at the 'examples', the 'regression tests' and 'tips and tricks' referenced by the appropriate documentation page from http://www.lilypond.org. Most popular, and many obscure, constructs seem to be there so you can look up the style visually and then click on the file name to see how it's done. You could use the following patterns for the links: http://lilypond.org/doc/vXXX/input/template/out-www/collated-files.html http://lilypond.org/doc/vXXX/examples.html http://lilypond.org/doc/vXXX/input/regression/out-www/collated-files.html http://lilypond.org/doc/vXXX/input/test/out-www/collated-files.html (replacing vXXX with v1.6, v1.8, v1.9 as appropriate) 3) Experiment. I have yet to see anything in the input that will break Lilypond. (Things may not run or work the way I expect, but it won't actually damage the computer or the program!) 4) Search the Lilypond archives - a convenient search field is on the http://www.lilypond.org page. Hope this helps /Hans ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Debian (Sid) packages for Lilypond 1.9.8
Debian Sid packages of Lilypond 1.9.8 are available from my website: http://www.pedrokroeger.net/lilypond/ They're also apt-gettable adding the following line to sources.list: deb http://www.pedrokroeger.net/lilypond/ ./ And running the commands: apt-get update apt-get install lilypond (or apt-get install lilypond=1.9.8-1 in some cases) Check the readme file for some tips: http://www.pedrokroeger.net/lilypond/readme.txt Cheers, Pedro ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Awkward Slur
[EMAIL PROTECTED] writes:
Check out this megaslur using the \translator command:
http://www.foxchange.com/~spamguy/misc_pictures/slursegment.jpg
What's the best way to fix this? Ideally I'd like to make the slur
bulge more and have the right end closer to the c4. I've looked through
the documentation at
http://www.lilypond.org/doc/v1.8/Documentation/user/out-www/lilypond-
internals/Slur.html , but didn't get much out of it. control-points
looks important, but I have no way of knowing what to do with it.
It depends how you far you want to go. The best option would be an S
style slur, ie.
_/
/
but that is not supported by Lilypond out of the box. (Your slur
really is too difficult for lily)
Solutions:
a) force a linebreak halfway the slur
b) Do it manually (See 1.9 CVS)
\version 1.9.8
\header {
texidoc = In extreme cases, you can resort to setting slur
control-points manually. This involves a lot of trial and error,
though
}
\score {\notes \new PianoStaff
\context Staff = up { \clef bass s1 * 6 }
\context Staff = down \relative c {
\clef bass
r4 r8
\once\property Voice.Slur \set #'extra-offset = #'(0 . -8)
\once\property Voice.Slur
\set #'control-points =
#'((0 . -4) (2 . 0) (60 . 0) (63 . 4))
c8( as' f c' as f c as' f
\translator Staff = up
\clef treble
c' as f' c as' f c' as
f' c as' f c'4)
}
\paper { raggedright = ##t }
}
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: papersize problem
On Friday 19 September 2003 05:37 am, Mats Bengtsson wrote: Would you expect a ledger paper to be used mainly in landscape or Rename ledger to ledger-tabloid. Is there some reason for not having ledger-[portrait] and ledger-landscape? You can add them and also legal-tabloid later and not have to rename stuff again. legal-tabloid is nice. It doesn't fall off the stand, and a lot more printers can do it. Why not other sizes two up also? daveA -- Why should any country entrust its young people to the leadership of the same geniuses who *invaded the wrong country*? Answer: Money. The U.S. is broke, and stiffed Gulf War partners. *U.S.* troops and vets *don't* trust Bush. D. Raleigh Arnold dra@ http://www.openguitar.com [EMAIL PROTECTED] ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: emacs lilypond-mode still not working with Pedro's 1.9.6
* Paul Scott ([EMAIL PROTECTED]) wrote:
Loading lilypond-mode (source)...
File mode specification error: (invalid-read-syntax #)
After reinstalling 1.8.1 from Debian unstable emacs works correctly.
Which version of Debian are you running? full unstable or mixed
unstable? Which version of emacs are you using?
mixed unstable
GNU Emacs 21.3.1 (i386-pc-linux-gnu, X toolkit) of 2003-09-13 on raven,
modified by Debian
I discovered what is wrong. Actually it's kind of my fault :( There is
a python script now that generates the lilypond.words file. The script
itself rather then lilypond.words was copied to the package. I'm
building another package with this issue fixed. I'll send a patch to
the devel list after I have double-checked the debian/rules script.
Meanwhile you might want to copy the attached lilypond.words to
/usr/share/emacs/site-lisp/ after installing lilypond-1.9.8
Cheers,
Pedro
\( - _ \) -
\[ - _ \] -
- _ -
- _ -
\\\( - _ \\\) -
\\\[ - _ \\\] -
\\\ - _ \\\! -
\\\ - _ \\\! -
\\center - \ _ -
\\column - \ _ -
\\context\ Staff\ = - % { _ } -
\\context\ Voice\ = - % { _ } -
\\markup - { _ } -
\\notes - { _ } -
\\relative - % { _ } -
\\score - { \\n \? \\simultaneous { \\n _ \\n } \! \\n \\paper { } \\n \? \\midi { }
\\n \! } \\n -
\\simultaneous - { _ } -
\\sustainDown - _ \\sustainUp -
\\times - % { _ } -
\\transpose - % { _ } -
Accidental
Accidental_engraver
Arpeggio_engraver
Auto_beam_engraver
Axis_group_engraver
BarLine
Bar_engraver
Bar_number_engraver
Beam
Beam_engraver
Break_align_engraver
Breathing_sign_engraver
ChoirStaff
ChordNameVoice
ChordNames
Chord_name_engraver
Chord_tremolo_engraver
Clef_engraver
Cluster_spanner_engraver
Collision_engraver
Custos
Custos_engraver
Dot_column_engraver
Dynamic_engraver
Dynamic_performer
Extender_engraver
FiguredBass
Figured_bass_engraver
Fingering_engraver
Font_size_engraver
Forbid_line_break_engraver
Glissando_engraver
Grace_beam_engraver
GrandStaff
GregorianTranscriptionStaff
GregorianTranscriptionVoice
Grob_pq_engraver
Hyphen_engraver
InnerChoirStaff
InnerStaffGroup
Instrument_name_engraver
KeySignature
Key_engraver
Key_performer
LigatureBracket
Ligature_bracket_engraver
Lyric_engraver
Lyric_performer
Lyric_phrasing_engraver
Lyrics
LyricsVoice
Mark_engraver
Melisma_engraver
Metronome_mark_engraver
Multi_measure_rest_engraver
New_fingering_engraver
NoteHead
NoteNames
Note_head_line_engraver
Note_heads_engraver
Note_name_engraver
Note_performer
Note_swallow_translator
Ottava_spanner_engraver
Output_property_engraver
Percent_repeat_engraver
Phrasing_slur_engraver
PianoStaff
Piano_pedal_engraver
Piano_pedal_performer
Pitch_squash_engraver
Repeat_acknowledge_engraver
Rest_collision_engraver
Rest_engraver
Rest_swallow_translator
RhythmicStaff
Rhythmic_column_engraver
Score
Script
Script_column_engraver
Script_engraver
SeparatingGroupSpanner
Separating_line_group_engraver
SeparationItem
Skip_event_swallow_translator
Slash_repeat_engraver
Slur
Slur_engraver
Spacing_engraver
Span_arpeggio_engraver
Span_bar_engraver
Span_dynamic_performer
Staff
StaffContainer
StaffGroup
StaffSymbol
Staff_collecting_engraver
Staff_symbol_engraver
Stanza_number_engraver
Stem
Stem_engraver
String_number_engraver
Swallow_performer
System_start_delimiter_engraver
TabStaff
TabVoice
Tab_note_heads_engraver
Tempo_performer
TextSpanner
Text_engraver
Text_spanner_engraver
Thread
Thread_devnull_engraver
Tie_engraver
Tie_performer
Time_signature_engraver
Time_signature_performer
Timing_engraver
Timing_translator
Tuplet_engraver
VaticanaStaff
VaticanaVoice
Vaticana_ligature_engraver
VerticalAlignment
Vertical_align_engraver
Voice
Voice_devnull_engraver
VoltaBracket
Volta_engraver
\\ChoirStaffContext
\\ChordNamesContext
\\EasyNotation
\\FiguredBassContext
\\GrandStaffContext
\\GregorianTranscriptionStaffContext
\\GregorianTranscriptionVoiceContext
\\InnerChoirStaffContext
\\InnerStaffGroupContext
\\LyricsContext
\\LyricsVoiceContext
\\NoteNamesContext
\\OrchestralScoreContext
\\PianoStaffContext
\\RemoveEmptyStaffContext
\\RhythmicStaffContext
\\ScoreContext
\\StaffContainerContext
\\StaffContext
\\StaffGroupContext
\\TabStaffContext
\\TabVoiceContext
\\ThreadContext
\\VaticanaStaffContext
\\VaticanaVoiceContext
\\VoiceContext
\\accent
\\accentus
\\accepts
\\acciaccatura
\\addlyrics
\\aeolian
\\alias
\\alternative
\\apply
\\applycontext
\\applyoutput
\\appoggiatura
\\arpeggio
\\arpeggioBracket
\\ascendens
\\auctum
\\autoBeamOff
\\autoBeamOn
\\autochange
\\bar
\\bigger
\\blackTriangleMarkup
\\blotdiameter
\\bold
\\box
\\bracket
\\break
\\breathe
\\breve
\\cadenzaOff
\\cadenzaOn
\\caesura
\\cavum
\\center
\\char
\\chordmodifiers
\\chords
\\circulus
\\clef
\\cm
\\coda
\\column
\\combine
\\consists
\\consistsend
\\context
\\cr
\\cresc
\\dashBar
\\dashDash
\\dashDot
\\dashHat
\\dashLarger
\\dashPlus
\\dashUnderscore
\\decr
\\default
\\defaultAccidentals
\\deminutum
\\denies
\\descendens
\\description
\\dim
\\dir-column
\\divisioMaior
\\divisioMaxima
\\divisioMinima
\\dorian
Re: Debian (Sid) packages for Lilypond 1.9.6
Pedro Kroger [EMAIL PROTECTED] writes:
deb-src http://www.pedrokroeger.net/lilypond/ ./
OK, I got it. Kinda worked, I put the results on the same
page (http://afavant.elte.hu/~wferi/lilypond). There were
some problems though:
Imagemagick is needed.
autotrace 0.29 is enough.
texinfo 4.1 is enough.
scrollkeeper is needed.
#include stdio.h into lily/parser.yy
g++ 2.95 is enough. (configure problem!)
dpkg-gencontrol: warning: unknown substitution variable ${misc:Depends}
And some random error messages while compiling the
documentation:
mftrace 1.0.19
Font `cmcsc7'...
Unknown encoding `TeX text without f-ligatures'; assuming tex256.
Font `cmtt17'...
Unknown encoding `TeX typewriter text'; assuming tex256.
dvips -u +lilypond.map -o out-www/lilypond.pdf.pdfps -t a4 -Ppdf out-www/lilypond.dvi
This is dvips(k) 5.86e Copyright 2001 Radical Eye Software (www.radicaleye.com)
' TeX output 2003.09.19:2101' - out-www/lilypond.pdf.pdfps
tex.proalt-rule.protexc.promusic-drawing-routines.pstexps.pro
special.pro. cmcsc10.pfbcmsl9.pfbcmtt12.pfbcmti9.pfbfeta11.pfa
cmbx7.pfbcmbx8.pfbfeta-nummer6.pfacmr12.pfbparmesan26.pfa
feta20.pfacmtt6.pfacmti8.pfbparmesan16.pfacmtt8.pfb
feta-braces30.pfa
Warning: module writet1 of dvips (file feta-braces30.pfa): character 127 is mapped to
.notdef
Writing header field `subtitle' to `puer-fragment.subtitle'...
programming error: Degenerate bow: infinite steepness reqd (Continuing; cross thumbs)
Now processing: `lily-240809831.ly'
Parsing...
Interpreting music...programming error: Grob NoteHead has no interface for property
delta-pitch (Continuing; cross thumbs)
/usr/local/src/lilypond-1.9.7/input/test/ancient-font.ly:51:3: warning: note head
`noteheads-vaticana_rvirga' not found:
c
d
/usr/local/src/lilypond-1.9.7/input/test/ancient-font.ly:45:6: warning: note head
`noteheads-vaticana_virga' not found:
b! de
s'! ges! fes!
programming error: round filled box horizontal extent smaller than blot; decreasing
blot (Continuing; cross thumbs)
Calculating line breaks... programming error: Grob KeySignature has no interface for
property style (Continuing; cross thumbs)
/usr/local/src/lilypond-1.9.7/input/test/ancient-font.ly:192:10: warning: flag
`neo_mensurald4' not found:
r2 r4 r8
r16 r16
/usr/local/src/lilypond-1.9.7/input/test/bagpipe.ly:53:26: warning: Weird stem size;
check for narrow beams:
gdcg = \notes{ \grace {
g'32[ d c]}}
Now processing: `lily-1024333031.ly'
Calculating line breaks... programming error: Unknown prefatory spacing. (Continuing;
cross thumbs)
/usr/local/src/lilypond-1.9.7/input/test/engraver-example.lyinc:8:12: warning: Junking
event: `KeyChangeEvent':
\key d\majo
r
[6]
Preprocessing graphical objects...
Calculating line breaks... warning: No spacing wishes found. Does your score have a
staff?
warning: No spacing wishes found. Does your score have a staff?
/usr/local/src/lilypond-1.9.7/input/test/mensural-ligatures.ly:37:7: warning:
Programming error: Infinity or NaN encountered:
e1
f1 a\breve g\longa^\fermata
Now processing: `lily-600227557.ly'
Interpreting music...warning: Symbol is not a parent context: Staff. Ignored
Preprocessing graphical objects...
Calculating line breaks... warning: Too many clashing notecolumns. Ignoring them.
Feri.
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Debian (Sid) packages for Lilypond 1.9.6
[EMAIL PROTECTED] writes: Pedro Kroger [EMAIL PROTECTED] writes: deb-src http://www.pedrokroeger.net/lilypond/ ./ OK, I got it. Kinda worked, I put the results on the same page (http://afavant.elte.hu/~wferi/lilypond). There were some problems though: Imagemagick is needed. autotrace 0.29 is enough. 0.30 is necessary for mftrace. 0.29 works but crashes sometimes. texinfo 4.1 is enough. 4.1 will fill your HD with 200 copies of music-glossary.info. #include stdio.h into lily/parser.yy thanks. g++ 2.95 is enough. (configure problem!) We had many hard-to-trace coredump problems with this GCC version. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: emacs lilypond-mode still not working with Pedro's 1.9.6
Pedro Kroger wrote: * Paul Scott ([EMAIL PROTECTED]) wrote: GNU Emacs 21.3.1 (i386-pc-linux-gnu, X toolkit) of 2003-09-13 on raven, modified by Debian I discovered what is wrong. Actually it's kind of my fault :( There is a python script now that generates the lilypond.words file. The script itself rather then lilypond.words was copied to the package. I'm building another package with this issue fixed. I'll send a patch to the devel list after I have double-checked the debian/rules script. Meanwhile you might want to copy the attached lilypond.words to /usr/share/emacs/site-lisp/ after installing lilypond-1.9.8 We're much closer. I now get with C-c C-f and similar with C-c C-l lilypond /home/paul/music/saso/pebcl.ly lilypond (GNU LilyPond) 1.9.8 lilypond: error: `/usr/bin/lilypond-bin --version ' failed (132) 2Dvi exited abnormally with code 1 at Fri Sep 19 14:20:24 Thanks, Paul ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question
| some notes | == 1 bracket
Ah, I see. In North America, a bracket is normally called a bar.
first of all, thank you for correcting my terminology. at least now I can
refer to this term correctly :-)
Please provide an example and tell us what version you're using. Are you
setting the midiInstrument property instead of instrument?
here is a part of my source file
theMusic = \context Score
\context ChoirStaff = Choir
\context Staff = SopranoStaffOne
\property Staff.instrument = #Soprano
\addlyrics
\context Voice = SopranoOneVoice { \SopranoOneNotes }
\context Lyrics = SopranoOneLyrics { \SopranoOneLyrics }
... here go other voices ...
the output I get is:
Interpreting music...
MIDI output to 'test.ly'
Track ... warning: no such instrument: 'soprano'
I know it is just a warning, but I would like not to have it. :-)
i am using lilypond version 1.8.1 (under cygwin)
i appreciate your help
ricardo
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question
Ricardo,
I used to get these warnings too, but I think I'm correct in saying that
they ceased when I started using separate score blocks for paper and midi
output. (Lily 1.8.1 under cygwin).
I use two global sections, one for paper and one for midi (to give me tempo
changes without getting warning messages about junking tempo request) as in
a typical example below:
globalpaper = \notes {
\key f \major
\time 3/4
\skip 2.*8
\time 1/2
\skip 2*1
\time 2/2
\skip 1*12
\bar |.
}
globalmidi = \notes {
\repeat volta 2 {
\tempo 2.=72
\skip 2.*8 }
\tempo 2=72
\skip 2*1
\repeat volta 2 {
\skip 1*10 }
\alternative {{ s1 }{ s1 }}
}
Then
voiceSopA = some notes
wordsSopA = some lyrics
etc for other voices, then I incorporate global paper within the voice
definitions
SopranoA = \notes
\addlyrics
\context Staff=SopA {
\property Staff.instrument = S 1
\property Staff.midiInstrument = acoustic grand
\VoiceDefault
\context Voice=SopA
\globalpaper
\voiceSopA
}
\context Lyrics=SopA
\context LyricsVoice=SopAVA
\property LyricsVoice . stanza = 1.
\wordsSopAVA
\context LyricsVoice=SopAVB
\property LyricsVoice . stanza = 2.
\wordsSopAVB
etc for the other voices, and finally score block for paper output only
\score { \notes \transpose c c
\context ChoirStaff = All
\context InnerChoirStaff = Sops
\SopranoA
\SopranoB
\Tenor
\paper {
textheight = 25.0\cm
interscoreline = 10.0\mm
interscorelinefill = 1
\translator {
\ScoreContext
breakAlignOrder = #'(
instrument-name
left-edge
ambitus
span-bar
breathing-sign
clef
key-signature
staff-bar
time-signature
custos
)
}
\translator {
\VoiceContext
\consists Ambitus_engraver
}
\translator{
\ScoreContext StanzaNumber \override #'break-align-symbol
= #'begin-of-note }
}
}
and a score block for midi only
\score { \notes \transpose c c
\apply #unfold-repeats
\globalmidi
\SopranoA
\SopranoB
\Tenor
\midi { \tempo 2=108 }
}
Warren Stickney
Wellington,
New Zealand
Replying to your:
--
Message: 7
Date: Fri, 19 Sep 2003 20:57:16 -0300
From: Ricardo Kirkner [EMAIL PROTECTED]
Subject: Re: Newbie question
To: Graham Percival [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Message-ID: [EMAIL PROTECTED]
Content-Type: text/plain; charset=iso-8859-1
| some notes | == 1 bracket
Ah, I see. In North America, a bracket is normally called a bar.
first of all, thank you for correcting my terminology. at least now I can
refer to this term correctly :-)
Please provide an example and tell us what version you're using. Are you
setting the midiInstrument property instead of instrument?
here is a part of my source file
theMusic = \context Score
\context ChoirStaff = Choir
\context Staff = SopranoStaffOne
\property Staff.instrument = #Soprano
\addlyrics
\context Voice = SopranoOneVoice { \SopranoOneNotes }
\context Lyrics = SopranoOneLyrics { \SopranoOneLyrics }
... here go other voices ...
the output I get is:
Interpreting music...
MIDI output to 'test.ly'
Track ... warning: no such instrument: 'soprano'
I know it is just a warning, but I would like not to have it. :-)
i am using lilypond version 1.8.1 (under cygwin)
i appreciate your help
ricardo
--
___
Lilypond-user mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-user
strange lyrics behaviour
hi: sorry to bother again, but i am having some trouble with the lyrics. I just don't know what it can be happening. when i add lyrics to the first staff, i have no problems. they get added correctly when i want to add lyrics to some other staff, the lyrics are wrongly placed, and i have many lines of error telling warning: lyrics found without any matching notehead however, if i add the duration of the corresponding note to the lyrics, then they get correctly placed. the question is: why is that happening but with the first staff? I attach the troublesome file, so you can see for yourself. just now, the bass voice has the durations, but if you put all the durations out, then those strange things happen hope that someone can give me some insight here, since i believe it must be some wrong stuff in my file that is crashing everything (by that i mean, my mistake -- just i can not find where ;-P ) thanks ricardo tant.ly Description: Binary data ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question
On Sat, 20 Sep 2003 14:49:11 +1200 Warren Stickney [EMAIL PROTECTED] wrote: I use two global sections, one for paper and one for midi (to give me tempo changes without getting warning messages about junking tempo request) as in a typical example below: BTW, now that metronome markings have been added to 1.8.x, you don't need to seperate global tempo changes from the rest of global stuff. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
Re: Newbie question
On Fri, 19 Sep 2003 20:57:16 -0300 Ricardo Kirkner [EMAIL PROTECTED] wrote: Please provide an example and tell us what version you're using. Are you setting the midiInstrument property instead of instrument? here is a part of my source file Sorry, could you provide a complete example (so that I can easily compile it on my own)? I suspect that you're doing something wierd in the layout of your lilypond file, and to check that I'll need to see the whole thing. Cheers, - Graham ___ Lilypond-user mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-user
