Re: non-markup stencils
Erik Sandberg wrote: On Thursday 05 May 2005 02.21, Han-Wen Nienhuys wrote: 2. the internal design document (some versions have been floating on the lilypond-devel list) That sounds useful. I can't find that document in the ml archives though, do you have any hints about which keywords to search for? try Sorensen Linhardt LilyPond -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lily 2.5.22 compiling
[EMAIL PROTECTED]:~/src/lilypond-2.5.22$ guile-config --version guile-config - Guile version 1.6.5 If it helps to know, compiling the stable version (2.4.5) works, so I have all the necessary software for that. Han-Wen Nienhuys wrote: Phillip Kirlin wrote: Hi all, Here's an error message I'm getting...any ideas? It appears to be something wrong with lily.scm in the Scheme code... which version of GUILE are you running? ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \midi in \book
On Thursday 05 May 2005 17.44, Stephen wrote: > Perhaps my suggestion was not clear enough, I am suggesting placing one > midi block outisde of the score blocks to effect every score block in the > book. This would allow multiple midi scores be automatically concatenated > into a single midi file. Otherwise, only the midi file in the last score is > saved, the previous ones being overwritten. But I suppose multiple midi > files overwriting each other instead of being saved as mid-1, mid-2, etc. > is a bug? and therefore this is fixing a problem that should not exist? The problem with midi files overwriting each other, should be fixed in 2.5.22. -- Erik Sandberg Maintainer of the Lilypond bug CVS archive, http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/lily-bugs/bugs/ http://lilypond.org/doc/v2.5/bugs/out/index.html ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \midi in \book
Yes, this bug has been fixed in recent 2.5.xx versions, if I remember
correctly.
/Mats
Stephen wrote:
Perhaps my suggestion was not clear enough, I am suggesting placing one
midi block outisde of the score blocks to effect every score block in
the book. This would allow multiple midi scores be automatically
concatenated into a single midi file. Otherwise, only the midi file in
the last score is saved, the previous ones being overwritten. But I
suppose multiple midi files overwriting each other instead of being
saved as mid-1, mid-2, etc. is a bug? and therefore this is fixing a
problem that should not exist?
Stephen
- Original Message - From: "Stephen" <[EMAIL PROTECTED]>
To: "Mats Bengtsson" <[EMAIL PROTECTED]>
Cc: "lilypond devel"
Sent: Saturday, April 09, 2005 8:53 AM
Subject: Re: \midi in \book
I am thinking more in terms of making this legal:
\book {
\score { \header { piece = "Adjutant's Call" } \transpose c c'' {
\adjutantscall } \layout { } }
\score { \header { piece = "Retreat" } \transpose c c'' { \retreat }
\layout { } }
\score { \header { piece = "To The Color" } \transpose c c'' {
\tothecolor } \layout { } }
\score { \header { piece = "Tatoo" } \transpose c c'' { \tattoo }
\layout { } }
\score { \header { piece = "Call To Quarters" } \transpose c c'' {
\calltoquarters } \layout { } }
\score { \header { piece = "Taps" } \transpose c c'' { \taps } \layout
{ } }
\midi { \context { \Voice \remove Span_dynamic_performer } }
}
Stephen
- Original Message - From: "Mats Bengtsson"
<[EMAIL PROTECTED]>
To: "Stephen" <[EMAIL PROTECTED]>
Cc: "lilypond devel"
Sent: Friday, April 08, 2005 10:38 AM
Subject: Re: \midi in \book
How about:
\score{ s4 \midi {\tempo 4=60 }}
/Mats
Stephen wrote:
There is a need for a book scope \midi block that has a one second
silence inserted between scores analogous to beforetitlespace in
page layout.
Stephen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
--
=
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-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Build error using kpathsea-4
Jan Nieuwenhuizen writes: There was a problem with cygkpathsea-4.dll. Can you try the unreleased tetex-3.0.0-3 from lilypond.org/cygwin? That should work now. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Build error using kpathsea-4
Yeah! It builds and runs. Bert Jan Nieuwenhuizen írta: Jan Nieuwenhuizen writes: There was a problem with cygkpathsea-4.dll. Can you try the unreleased tetex-3.0.0-3 from lilypond.org/cygwin? That should work now. Jan. ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
lily 2.5.22 compiling
Hi all, Here's an error message I'm getting...any ideas? It appears to be something wrong with lily.scm in the Scheme code... --Phil Kirlin === [snip...] make[2]: Entering directory `/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/Documentation/user' cd ./out && /nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/lily/out/lilypond --verbose /nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/ly/generate-documentation GNU LilyPond 2.5.22 LILYPOND_DATADIR="/nfs/tungsten/users2/pkirlin/share/lilypond/2.5.22" LILYPONDPREFIX="/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22" LOCALEDIR="/nfs/tungsten/users2/pkirlin/share/locale" Effective prefix: "/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22" [/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/lily-library.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/file-cache.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/define-music-types.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/output-lib.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/c++.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/chord-ignatzek-names.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/chord-entry.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/chord-generic-names.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/stencil.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/markup.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/bass-figure.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/music-functions.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/part-combiner.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/define-music-properties.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/auto-beam.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/chord-name.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/ly-from-scheme.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/define-context-properties.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/translation-functions.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/script.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/midi.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/beam.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/clef.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/slur.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/font.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/encoding.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/fret-diagrams.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/define-markup-commands.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/define-grob-properties.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/define-grobs.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/define-grob-interfaces.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/page-layout.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/titling.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/paper.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/backend-library.scm][/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/x11-color.scmBacktrace: In /nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/lily.scm: 185: 0* [for-each # #] In /nfs/tungsten/users2/pkirlin/share/guile/1.6/srfi/srfi-1.scm: 661: 1 (if (null? rest) (letrec ((lp #)) (lp list1)) ...) ... 665: 2 (begin (f (car l)) (lp (cdr l))) 666: 3* [ly:load "x11-color.scm"] In /nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/lily.scm: 72: 4 (let (#) (if # #) (primitive-load file-name) ...) 75: 5* [primitive-load "/nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lil$ /nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/lily.scm:75:5: In procedure scm_lreadr in expression (primitive-load file-name): /nfs/tungsten/users2/pkirlin/src/lilypond-2.5.22/share/lilypond/2.5.22/scm/lily.scm:75:5: unknown # object make[2]: *** [out/lilypond-internals.texi] Error
Re: mensural notation
Hi Jürgen, What I do not understand, if you want neo-mensural noteheads, why not just doing "\override Voice.NoteHead #'style = #'neomensural"? As far as I can see, the main difference between neomensural and mensural notehead are (besides the different parameters) that mensural noteheads have diamond shape at their centerline, while neomensural heads have it at the outer boundary, and I just need this. Note that with my patch the mensural and neomensural noteheads still look different. My main point is to have bigger noteheads, almost two linespaces high; but it should not be so big that a notehead between two stafflines have those lines visible in the interior hole. p Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a FreeStarttol. Probald ki most! http://www.freestart.hu ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
RE: new title on multiple \score blocks in same file
The doc link isn't clear, but it implies that a second invocation of \header is still limited. I now get the desired result by using \markup and \tag. This works, but horizontal positioning is tedious. Feature request: add "\margin-align dir arg" to \markup commands, similar to \halign, but relative to page margins, not the associated note. If dir = -1, flush left, dir = +1, flush right, interpolate linearly in between. - Bruce -Original Message- From: Mats Bengtsson [mailto:[EMAIL PROTECTED] Sent: Thursday, April 28, 2005 3:31 AM To: Fairchild Cc: lilypond-user@gnu.org Subject: Re: new title on multiple \score blocks in same file In the development versions, it is now easy to redefine how the titling is done for each score, see the bottom of the page at http://lilypond.org/doc/v2.5/Documentation/user/out-www/lilypond/Creating-ti tles.html#Creating-titles For page breaks, see the section on page breaking. /Mats Fairchild wrote: > Mats - > > Looking for a neat way to insert complete \header information for > selected \score blocks in a sequence of \score blocks. > > Found the below message in the archives. > > Did the feature ever happen? > > - Bruce > > %%% > > From: Mats Bengtsson > Subject: Re: new title on multiple \score blocks in same file > Date: Sun, 26 Oct 2003 17:40:43 +0100 > > I send a copy of this to bug-lilypond since it's a feature request. > > As you have noted, you will only get a new indication of piece and > opus for each subsequent \score. I agree with you that it would be > great to have some option to automatically print a number of > individual parts from a single input file. However, then you would > also like a new page for each new \score. Also, the page numbers > should be reset and maybe the layout should be changed to typeset the > instrument name in the page heading. > > %%% > > > > > ___ > lilypond-user mailing list > lilypond-user@gnu.org > http://lists.gnu.org/mailman/listinfo/lilypond-user -- = 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-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: \midi in \book
Perhaps my suggestion was not clear enough, I am suggesting placing one midi
block outisde of the score blocks to effect every score block in the book.
This would allow multiple midi scores be automatically concatenated into a
single midi file. Otherwise, only the midi file in the last score is saved,
the previous ones being overwritten. But I suppose multiple midi files
overwriting each other instead of being saved as mid-1, mid-2, etc. is a
bug? and therefore this is fixing a problem that should not exist?
Stephen
- Original Message -
From: "Stephen" <[EMAIL PROTECTED]>
To: "Mats Bengtsson" <[EMAIL PROTECTED]>
Cc: "lilypond devel"
Sent: Saturday, April 09, 2005 8:53 AM
Subject: Re: \midi in \book
I am thinking more in terms of making this legal:
\book {
\score { \header { piece = "Adjutant's Call" } \transpose c c'' {
\adjutantscall } \layout { } }
\score { \header { piece = "Retreat" } \transpose c c'' { \retreat }
\layout { } }
\score { \header { piece = "To The Color" } \transpose c c'' {
\tothecolor } \layout { } }
\score { \header { piece = "Tatoo" } \transpose c c'' { \tattoo } \layout
{ } }
\score { \header { piece = "Call To Quarters" } \transpose c c'' {
\calltoquarters } \layout { } }
\score { \header { piece = "Taps" } \transpose c c'' { \taps } \layout
{ } }
\midi { \context { \Voice \remove Span_dynamic_performer } }
}
Stephen
- Original Message -
From: "Mats Bengtsson" <[EMAIL PROTECTED]>
To: "Stephen" <[EMAIL PROTECTED]>
Cc: "lilypond devel"
Sent: Friday, April 08, 2005 10:38 AM
Subject: Re: \midi in \book
How about:
\score{ s4 \midi {\tempo 4=60 }}
/Mats
Stephen wrote:
There is a need for a book scope \midi block that has a one second
silence inserted between scores analogous to beforetitlespace in page
layout.
Stephen
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.6 release. (Was: new manual chapter)
Han-Wen Nienhuys wrote:
(replying to list)
Graham Percival wrote:
Pressing: as of 2.5.20 (last version in fink),
- lilypond-book: \usepackage{graphics} is not automatically added
when creating
the .tex file.
Is that pressing? (I'm not sure whether to inlcude graphics, graphicx,
or another package.)
In my opinion, lilypond-book should include a line
\RequirePackage{graphicx}
just before \begin{document}. This means that you don't get an error
on documents where graphicx is already loaded.
Another question is graphicx versus graphics, but as far as I know, the
graphicx package is the newer and better of the two.
I have also recently reported other another lilypond-book, namely that
the linewidth of LaTeX documents isn't taken into account in the scores.
I could probably fix these two issues myself, but since I don't have a
good grasp of the overall structure of the program for the moment, it
might take me some time, so if someone else wants to do it, please go
ahead.
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
