Re: configure and guile
> "JN" == Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes:
>> So I've removed /etc/alternatives/gs and linked it to
>> /usr/bin/gs-afpl, and we'll see what happens now.
JN> Ok.
Here's what happened. Now what? It isn't at all clear that this has
anything to do with the gs version.
error: failed files: "lily-1752692436 lily-2007587447 lily-61073460
lily-1198059970 lily-1114596008"
../../scripts/lilypond-book.py: warning: `lilypond' failed (status 1) (ignored)
../../scripts/lilypond-book.py: error: Process lilypond --backend eps
--formats=ps,png --header=texidoc -I ./input/test -e '(ly:set-option (quote
internal-type-checking) #t)' -I
/home/lconrad/src/lilypond/lilypond-2.5.19/Documentation/user -I
/home/lconrad/src/lilypond/lilypond-2.5.19/Documentation/user -I
/home/lconrad/src/lilypond/lilypond-2.5.19/Documentation/user/out -I
/home/lconrad/src/lilypond/lilypond-2.5.19/input -I
/home/lconrad/src/lilypond/lilypond-2.5.19/input/regression -I
/home/lconrad/src/lilypond/lilypond-2.5.19/input/test -I
/home/lconrad/src/lilypond/lilypond-2.5.19/input/tutorial -I
/home/lconrad/src/lilypond/lilypond-2.5.19/mf/out -I
/home/lconrad/src/lilypond/lilypond-2.5.19/mf/out snippet-map.ly lily-847424724
lily-264939913 lily-1329178150 lily-2120973390 lily-1114596008 lily-1973004
lily-629058035 lily-1198059970 lily-180913092 lily-162465394 lily-427681081
lily-1104566637 lily-1882589384 lily-749487413 lily-115977479 lily-61073460
lily-1137913684 lily-893847993 lily-1560049904 lily-44452797 lily-924703020
lily-1908804818 lily-563222144 lily-973787798 lily-1491402092 lily-139894
lily-1294662994 lily-448158694 lily-615545092 lily-498509906 lily-1893664695
lily-170876723 lily-710917742 lily-1921093934 lily-1307325768 lily-1783479488
lily-1308155637 lily-2007587447 lily-893995012 lily-742411752 lily-1575408674
lily-1805001633 lily-515043545 lily-1113001510 lily-668792565 lily-248349599
lily-1248899084 lily-218442940 lily-1284836469 lily-1876128456 lily-1596632048
lily-1792076568 lily-2064136277 lily-479681207 lily-1558077935 lily-2113483397
lily-1803558402 lily-218114627 lily-2076963983 lily-1150221627 lily-1229217213
lily-408683045 lily-1958253955 lily-806690227 lily-275916528 lily-1012193216
lily-920503384 lily-1907188693 lily-1752692436 lily-149988334 lily-1159672687
lily-1684419166 lily-120670767 lily-797724505 exited unsuccessfully.
Removing `music-glossary.texi'
Traceback (most recent call last):
File "../../scripts/lilypond-book.py", line 1558, in ?
main ()
File "../../scripts/lilypond-book.py", line 1554, in main
ly.exit (1)
File
"/home/lconrad/src/lilypond/lilypond-2.5.19/share/lilypond/2.5.19/python/lilylib.py",
line 132, in exit
raise _ ('Exiting (%d)...') % i
Exiting (1)...
make[3]: *** [out/music-glossary.texi] Error 1
make[3]: Leaving directory
`/home/lconrad/src/lilypond/lilypond-2.5.19/Documentation/user'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/home/lconrad/src/lilypond/lilypond-2.5.19/Documentation'
make[1]: *** [all] Error 2
make[1]: Leaving directory `/home/lconrad/src/lilypond/lilypond-2.5.19'
make: *** [build-stamp] Error 2
debuild: fatal error at line 764:
dpkg-buildpackage failed!
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
Op vr, 15-04-2005 te 11:22 +0100, schreef Bernard Hurley: > > When called from lilypond-book, LilyPond does _not_ take care of > formatting the pages. This is precisely the reason I started using it. > So that I can have a multi-movement score with fancy headers, table of > contents, etc. What it does is to break a long score up into several > snippets each of which is included individually. It would be extremely > useful to have a macro that added something between these snippets. > This is not quite correct. Lily will do page formatting if you put your music into a \book block. The .eps files then output represent a full page, and with appropriate latex trickery, they could be put on a single page each. I don't see why you're so keen on doing everything in LaTeX. If every system is dumped as a separate .EPS, then it will not be possible to determine neat vertical spacing and sensible pagebreaks in the final document. Conversely, it should not be that hard to make lilypond put barnumbers or rehearsal marks in page headers or footers. The code is all in scm/page-layout.scm, and can be changed at runtime. -- Han-Wen Nienhuys - [EMAIL PROTECTED] LilyPond Software Design - http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
Laura Conrad wrote:
> Getting latex to not render a footnote marker is pretty easy. You
> just say:
>
> \footnotetext[1]{Here's the first footnote.}
Of course, I've been away from LaTeX for too long!
The sort of thing I had in mind was to get lilypond-book to (optionally)
produce a LaTeX file that contained information about things like bar
numbers and footnotes in eps snippets this could be input near the top
of the LaTeX source and then macros could be used to control things like
bar numbers in page headers. It looks entirely possible to me but it
would take some time to get right! But it would also mean you would be
able to say things like "see bar 16 of Fred Blogg's Symphony Op. 11
(page 6)". This sort of thing would be very useful if you were (say)
writing a book on orchestration.
I doubt that this sort of thing would be of top priority for core
developers so I will look and see what I can come up with myself.
/Bernard
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
> > \includegraphics. > > Yes, I agree. Go forth and provide a patch! > > > Werner Will do -as soon as I have convinced myself I havn't broken anything! /Bernard ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: configure and guile
Laura Conrad writes: > [adieu]# ls -l /etc/alternatives/gs > lrwxrwxrwx 1 root root 15 Apr 15 10:03 /etc/alternatives/gs -> > /usr/bin/gs-esp > I don't know how this is supposed to work, but it seems unlikely that > what's happening is what I want. See man update-alternatives > chugging. Mostly on gs, so I should probably fix the gs problem and > do it again. > > So I've removed /etc/alternatives/gs and linked it to > /usr/bin/gs-afpl, and we'll see what happens now. Ok. -- 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: configure and guile
> "JN" == Jan Nieuwenhuizen <[EMAIL PROTECTED]> writes: JN> Laura Conrad writes: >> 7.07.1 is not actually true -- when I "apt-get install gs" I get: >> >> [lilypond-2.5.19]# dpkg -l gs >> ii gs 8.01-5 Transitional package JN> Are you sure you don't have gs-esp or gs-gpl installed? It looks like I have all kinds of things installed, only some of which are because of fiddling this morning. JN> Try gs --version and/or dpkg -l | grep ' gs'. [adieu]# gs --version 7.07.1 [adieu]# dpkg -l | grep ' gs' ii gs 8.01-5 Transitional package ii gs-afpl8.14-3 The AFPL Ghostscript PostScript interpreter ii gs-aladdin 8.14-3.1 Transitional package ii gs-common 0.3.6-0.1 Common files for different Ghostscript relea ii gs-esp 7.07.1-9 The Ghostscript PostScript interpreter - ESP ii gs-gpl 8.01-5 The GPL Ghostscript PostScript interpreter ii gscanbus 0.7.1-5scan IEEE1394 (firewire/i.link) bus ii gsfonts8.14+v8.11-0.1 Fonts for the Ghostscript interpreter(s) ii gsfonts-x110.17 Make Ghostscript fonts available to X11 ii gsm-utils 1.10-5 GSM mobile phone access applications Also: [adieu]# ls -l /usr/bin/gs lrwxrwxrwx 1 root root 20 Oct 3 2004 /usr/bin/gs -> /etc/alternatives/gs [adieu]# ls -l /etc/alternatives/gs lrwxrwxrwx 1 root root 15 Apr 15 10:03 /etc/alternatives/gs -> /usr/bin/gs-esp [adieu]# ls /usr/bin/gs* /usr/bin/gs /usr/bin/gscanbus /usr/bin/gslp/usr/bin/gsmsiexfer /usr/bin/gs-afpl /usr/bin/gsdj /usr/bin/gsmctl /usr/bin/gsmsmsd /usr/bin/gs-esp /usr/bin/gsdj500 /usr/bin/gsmpb /usr/bin/gsmsmsstore /usr/bin/gs-gpl /usr/bin/gsftopk /usr/bin/gsmsendsms /usr/bin/gsnd /usr/bin/gsbj /usr/bin/gslj /usr/bin/gsmsiectl I don't know how this is supposed to work, but it seems unlikely that what's happening is what I want. JN> Does 8.01 work for you, if you trick configure? It's only a warning that configure gives, so I don't have to trick it. I did a "make all" successfully this morning, but then decided to build a debian package before playing with it, and that's still chugging. Mostly on gs, so I should probably fix the gs problem and do it again. So I've removed /etc/alternatives/gs and linked it to /usr/bin/gs-afpl, and we'll see what happens now. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: configure and guile
Laura Conrad writes: > 7.07.1 is not actually true -- when I "apt-get install gs" I get: > > [lilypond-2.5.19]# dpkg -l gs > ii gs 8.01-5 Transitional package Are you sure you don't have gs-esp or gs-gpl installed? Try gs --version and/or dpkg -l | grep ' gs'. Does 8.01 work for you, if you trick configure? 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: lilypond book issues version 2.5.19
> "BH" == Bernard Hurley <[EMAIL PROTECTED]> writes:
BH> To do it now you would have to get LaTeX to associate a
BH> footnote with a particular eps file but stop it rendering the
BH> footnote marker. If no one else wants to I will look into
BH> this!
Getting latex to not render a footnote marker is pretty easy. You
just say:
\footnotetext[1]{Here's the first footnote.}
If you leave out the number in brackets, Latex will pick a number for
you. So all you have to do is have your .lytex file be in sync with
your .ly files about what the numbers of the footnotes are.
--
Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ )
(617) 661-8097 fax: (501) 641-5011
233 Broadway, Cambridge, MA 02139
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
> I would appreciate if I in latex could get the first and last \piece, > \mark number, and bar number on a page to be able to put it in page > headers/footers, or add some footnotes from within the music, > as some editors do. > These are things I would like to be able to do(especially the footnotes!), but I think they would be rather difficult to implement. Interestingly in one of the older versions (I can't remember which and I can't remember when it stopped working. At the time I was not particularly interested in it and just tried it out of curiosity) it was possible to put a footnote in markup and it would be rendered correctly by lilypond-book. To do it now you would have to get LaTeX to associate a footnote with a particular eps file but stop it rendering the footnote marker. If no one else wants to I will look into this! /Bernard ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: removing unwanted accidentals
> On Friday 15 April 2005 10.56, Karl Hammar wrote:
> > [EMAIL PROTECTED]:
> > > It also changes the numbering of all subsequent bars. I don't know the
> > > author's intent in this case (I didn't write that snippet), but I guess
> > > it could be something like an attaca movement.
> >
> > Yes. The bigger picture is H. Purcells opera "Dido & Æneas":
> >
> > http://aspodata.se/motett/noter/act*
>
> nice! (will this end up on mutopia?)
Anyone is welcome to use it (it is still being worked on).
The code is gpl (cc-sa if you insist) and Purcells music is public
domain.
>
> > I did not like idea of big bar number, like 543.
> > I think it is better with aria/movement 23, bar 25.
>
> You could use something like this (based on print-circled-text-callback in
> scm/output-lib.scm) to achieve what you want more cleanly. It works with
> 2.5.19, but not with 2.4 for some reason.
>
> \version "2.4.0"
>
> #(define-public (print-+100-text-callback grob)
> (let* ( ;(text (ly:grob-property grob 'text))
> (text (number->string (+ 100 (string->number (ly:grob-property grob
> 'text)
> (layout (ly:grob-layout grob))
> (defs (ly:output-def-lookup layout 'text-font-defaults))
> (props (ly:grob-alist-chain grob defs))
> (text-stencil (Text_interface::interpret_markup layout props text)))
> (ly:stencil-add (centered-stencil text-stencil
>
>
> \new Staff {
> \set Score.barNumberVisibility = #(every-nth-bar-number-visible 1)
> \override Score.BarNumber #'print-function =
> #print-+100-text-callback
>
> \repeat unfold 9 { c1 \break } \bar "|."
> }
>
> HTH,
> Erik
I think you misunderstand me, I wanted smallish bar numbers since that
is easier
to say at a rehersal, not something that is +100.
Regards
/Karl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
... > > Its not a matter circumventing any limitations of Lilypond, but of being > > able to use the full power of LaTeX. It would not be practical to add > > anything to LilyPond itself to get this functionality as using it would > > involve (at least) two calls to lilypond. Actually I already have this > > functionality (and more) as I call Lilypond from LyX, using a LyX > > converter that I am developing and this can do some post-processing on > > the file produced by lilypond-book. The code for the converter at the > > moment is a bit of a mess and is really only usable by me. I will > > release it sometime, but I will probably wait till the next version of > > LyX is released as that will change the way converters are handled. > > However life would be easier if it could be done with a macro. > > I'm just trying to help the LilyPond hackers to judge if your request > is of sufficiently general interest to be worth to implement and > support. So far, I have to say that your request looks fairly exotic > to me and I can't see that there would be a large group of users that > would use it. > If you prove me wrong, I'd be happy to change my mind (can't promise > about the main developers, though). > > /Mats I would appreciate if I in latex could get the first and last \piece, \mark number, and bar number on a page to be able to put it in page headers/footers, or add some footnotes from within the music, as some editors do. Regards /Karl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: removing unwanted accidentals
> >*No*, the forget does not work for: > act 1, aria 13, bar 6 Violin II: the b is shown with natural > act 1, aria 13, bar 11 Violin I: the f is shown with natural > Elsewhere yes, but not for theese two notes.> > > When I print out Score13, neither of these errors are present, even if I add > the line: No one of the ScoreXX has theese problems. I used them to speed up proofreading. The problem appears when I put all the movements together and resets the bar number, as in act1.ly. > > #(set-accidental-style 'forget), which should suppress it in context of the > total score. Don't forget you can set that anywhere in the score and reverse > it with: > > #(set-accidental-style 'default). > > Stephen > Regards /Karl ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: removing unwanted accidentals
*No*, the forget does not work for: act 1, aria 13, bar 6 Violin II: the b is shown with natural act 1, aria 13, bar 11 Violin I: the f is shown with natural Elsewhere yes, but not for theese two notes.> When I print out Score13, neither of these errors are present, even if I add the line: #(set-accidental-style 'forget), which should suppress it in context of the total score. Don't forget you can set that anywhere in the score and reverse it with: #(set-accidental-style 'default). Stephen ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: removing unwanted accidentals
I think we want Lilypond to continue to follow standard practive. If we give
users the ability to violate those rules then total novices will start
making mistakes.
I think you know that in the example you gave, a person reading the score
would just play an f sharp where you want an f natural if you suppressed the
natural. Why supply a way to suppress that natural if we also have to say
never actually do if you do not want them to play f sharp? Another way of
putting it is that you could suppress the natural in that case, just by
writing fis instead of f, that is what someone reading it would play anyway,
so what's the point?
I am saying here that automatic control of accidentals is better, given the
number of choices we already have. In this case 'forget' solved the problem.
Stephen
- Original Message -
From: "Erik Sandberg" <[EMAIL PROTECTED]>
To: "Stephen" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>;
Sent: Thursday, April 14, 2005 3:49 PM
Subject: Re: removing unwanted accidentals
On Thursday 14 April 2005 21.31, Stephen wrote:
Given all the options for automatic accidentals: voice, modern,
modern-voice, piano, no-reset, forget, and default, one of them must
answer
every situation if you take the time to learn them. I find it confusing
when there are multiple ways to do the same thing. I'd look carefully at
the current options before I wrote a new option.
In the example, '\set Score.currentBarNumber = #1' creates the problem. I
don't see why the numbering is reset there other than to remove the
number
from that bar because it collides with the mark "D". There must be
another
way to suppress the bar number at that bar.
It also changes the numbering of all subsequent bars. I don't know the
author's intent in this case (I didn't write that snippet), but I guess it
could be something like an attaca movement.
However, I fixed it by setting the accidental style to 'forget'. See?
there
is already a way to do it.
There are situations where this doesn't work. E.g., in
{ \key d\major fis f }
I can see no way to avoid displaying the natural.
(this example I gave is not realistic, but the below example suggests that
it
may happen that you want to tweak accidentals in unexpected ways, e.g. due
to
other bugs)
Erik
- Original Message -
From: "Erik Sandberg" <[EMAIL PROTECTED]>
To:
Sent: Monday, April 11, 2005 3:53 PM
Subject: removing unwanted accidentals
> Hi,
>
> There seems to be a need for a way to notate that a single note should
> _not_
> have an accidental displayed, something like a 'force-no-accidental'
> property.
>
> I think there was a discussion about this over a year ago, without a
> conclusion. Now there have been 2 or 3 (implicit) requests for it in a
> short
> time, and IMHO it's a reasonable feature.
>
> Also it looks pretty trivial to implement; may I give it a try?
>
> Erik
>
> On Sunday 10 April 2005 14.32, Karl Hammar wrote:
>> How do I remove the unwanted explicit flats in the next to last
>> measure in:
>>
>> \version "2.4.2"
>>
>> \relative c'' {
>> \override Score.BarNumber #'break-visibility =
>> #end-of-line-invisible
>> \mark #03
>> \clef treble
>> \key c \minor
>> a2 b |
>> d1 |
>> \mark #04
>> \set Score.currentBarNumber = #1
>> d2 es8. as,16 bes8 c |
>> % ^ ^ unwanted explicit flats here
>> d1
>> }
>>
>> Regards
>> /Karl
>>
>>
>>
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> http://lists.gnu.org/mailman/listinfo/lilypond-user
>
> ___
> 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
configure and guile
I'm attempting to build 2.5.19 on debian unstable. Configure seems to be reasonably happy now, but is still complaining about gs: WARNING: Please consider installing optional programs: /usr/bin/gs >= 8.15 (installed: 7.07.1) 7.07.1 is not actually true -- when I "apt-get install gs" I get: [lilypond-2.5.19]# dpkg -l gs Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii gs 8.01-5 Transitional package but of course that's still not >= 8.15. When I do "apt-cache search gs", I see that in addition to vanilla gs (gs-gpl), there is also gs-aladdin and gs-afpl, both of which are 8.14. Does anyone know a source for a debian package of >= 8.15? The ghostscript.com site has afpl versions of 8.14 and 8.5 as tarballs. I would guess that 8.5 isn't in the normal Debian Unstable feeds for a reason. -- Laura (mailto:[EMAIL PROTECTED] , http://www.laymusic.org/ ) (617) 661-8097 fax: (501) 641-5011 233 Broadway, Cambridge, MA 02139 ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
> > > Isn't his what \makeatother is for?
> >
> > This isn't defined for plain TeX.
> >
>
> But lilypond-book produces a LaTeX document, not a TeX document.
Right. Sorry. IMHO this line should be deleted from lilypond-book.
> For example in 2.5.19 the code:
>
> \input lily-1105931465-systems.tex
>
> In Text.tex was generated from the _single_ call:
>
> \lilypondfile[indent=1.2\cm]{prelude-d.ly}
>
> It does not result in one postscript snippet being included but six
> as can be seen by looking at the contents of
> lily-1105931465-systems.tex:
>
> \includegraphics{lily-365734716-1.eps}
> \includegraphics{lily-365734716-2.eps}
> \includegraphics{lily-365734716-3.eps}
> \includegraphics{lily-365734716-4.eps}
> \includegraphics{lily-365734716-5.eps}
> \includegraphics{lily-365734716-6.eps}
> % eof - 'eof' is Makefile marker; do not remove.
Aah, I wasn't aware that lilypond already does that (admittedly, I
have never used the TeX backend in the 2.5 series due to lack of
time).
> It has to do something like this because Lilypond cannot possibly
> know where one page ends and the next starts. It would be very
> useful indeed to be able to put a macro between these calls to
> \includegraphics.
Yes, I agree. Go forth and provide a patch!
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
Bernard Hurley wrote:
Mats Bengtsson wrote:
I don't realize what you would want to add between the staff lines.
Is it to circumvent some limitations in LilyPond? Otherwise you could
just as well tell LilyPond to add the information.
I think both me, Werner and others on the mailing list would find it
easier to realize why you find it useful if you are a bit more specific.
First, I'm not sure what you mean by "between the staff lines". In the
example I gave, prelude-d.ly is for clarinet and piano. I did not want
to add anything between the clarinet and piano staffs or inside the
piano grandstaff.
Sorry, I means score lines (or systems if you prefer that nomenclature).
Lilypond-book renders the first three bars (clarinet
and piano together) in the first eps file, the next three in the next
etc.. If I render the final LaTeX file, the fourth of these eps files is
included at the top of page 2. Although I might guess that this will
happen, neither I, LaTeX or LilyPond can know this in advance note also
that changes both to the LilyPond score _and_ to my original LaTeX file
can change this. Suppose I want to do something specific under the first
system on each page (e.g. in a set of children's piano pieces I might
want a picture of a dog) then I could do it easily if I could insert an
appropriate LaTeX macro _between_ the \includegraphics calls. I could
also include things like cross-references to other pages, bibliographic
references etc.
That would be a fairly advanced macro if it's able to determine that
it's the first line of each page. Why not simply redefine
\includegraphics if you want to do some extra processing for each
included .eps file? If you want the original definition of
\includegraphics in the rest of the document and a special definition
only for the lilypond scores, then you could do the redefinition within
{pre,post}LilyPondExample. Another simple alternative is to write a
sed script that modifies the generated *-systems.tex file and inserts
whatever.
Its not a matter circumventing any limitations of Lilypond, but of being
able to use the full power of LaTeX. It would not be practical to add
anything to LilyPond itself to get this functionality as using it would
involve (at least) two calls to lilypond. Actually I already have this
functionality (and more) as I call Lilypond from LyX, using a LyX
converter that I am developing and this can do some post-processing on
the file produced by lilypond-book. The code for the converter at the
moment is a bit of a mess and is really only usable by me. I will
release it sometime, but I will probably wait till the next version of
LyX is released as that will change the way converters are handled.
However life would be easier if it could be done with a macro.
I'm just trying to help the LilyPond hackers to judge if your request
is of sufficiently general interest to be worth to implement and
support. So far, I have to say that your request looks fairly exotic
to me and I can't see that there would be a large group of users that
would use it.
If you prove me wrong, I'd be happy to change my mind (can't promise
about the main developers, though).
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
Mats Bengtsson wrote: > I don't realize what you would want to add between the staff lines. > Is it to circumvent some limitations in LilyPond? Otherwise you could > just as well tell LilyPond to add the information. > I think both me, Werner and others on the mailing list would find it > easier to realize why you find it useful if you are a bit more specific. > First, I'm not sure what you mean by "between the staff lines". In the example I gave, prelude-d.ly is for clarinet and piano. I did not want to add anything between the clarinet and piano staffs or inside the piano grandstaff. Lilypond-book renders the first three bars (clarinet and piano together) in the first eps file, the next three in the next etc.. If I render the final LaTeX file, the fourth of these eps files is included at the top of page 2. Although I might guess that this will happen, neither I, LaTeX or LilyPond can know this in advance note also that changes both to the LilyPond score _and_ to my original LaTeX file can change this. Suppose I want to do something specific under the first system on each page (e.g. in a set of children's piano pieces I might want a picture of a dog) then I could do it easily if I could insert an appropriate LaTeX macro _between_ the \includegraphics calls. I could also include things like cross-references to other pages, bibliographic references etc. Its not a matter circumventing any limitations of Lilypond, but of being able to use the full power of LaTeX. It would not be practical to add anything to LilyPond itself to get this functionality as using it would involve (at least) two calls to lilypond. Actually I already have this functionality (and more) as I call Lilypond from LyX, using a LyX converter that I am developing and this can do some post-processing on the file produced by lilypond-book. The code for the converter at the moment is a bit of a mess and is really only usable by me. I will release it sometime, but I will probably wait till the next version of LyX is released as that will change the way converters are handled. However life would be easier if it could be done with a macro. /Bernard ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: LAC2005
On Fri, 2005-04-15 at 11:36 +0200, Juergen Reuter wrote: > Hi! > > Just wondering: is there anyone else from this list except me going to the > Linux Audio Conference in Karlsruhe/Germany? > Jan & I will be there from friday noon to sunday morning. -- Han-Wen Nienhuys - [EMAIL PROTECTED] LilyPond Software Design - http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond book issues version 2.5.19
Bernard Hurley wrote:
When called from lilypond-book, LilyPond does _not_ take care of
formatting the pages. This is precisely the reason I started using it.
So that I can have a multi-movement score with fancy headers, table of
contents, etc. What it does is to break a long score up into several
snippets each of which is included individually. It would be extremely
useful to have a macro that added something between these snippets.
For example in 2.5.19 the code:
\input lily-1105931465-systems.tex
In Text.tex was generated from the _single_ call:
\lilypondfile[indent=1.2\cm]{prelude-d.ly}
It does not result in one postscript snippet being included but six as
can be seen by looking at the contents of lily-1105931465-systems.tex:
\includegraphics{lily-365734716-1.eps}
\includegraphics{lily-365734716-2.eps}
\includegraphics{lily-365734716-3.eps}
\includegraphics{lily-365734716-4.eps}
\includegraphics{lily-365734716-5.eps}
\includegraphics{lily-365734716-6.eps}
% eof - 'eof' is Makefile marker; do not remove.
It has to do something like this because Lilypond cannot possibly know
where one page ends and the next starts. It would be very useful indeed
to be able to put a macro between these calls to \includegraphics.
I don't realize what you would want to add between the staff lines.
Is it to circumvent some limitations in LilyPond? Otherwise you could
just as well tell LilyPond to add the information.
I think both me, Werner and others on the mailing list would find it
easier to realize why you find it useful if you are a bit more specific.
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: removing unwanted accidentals
On Friday 15 April 2005 10.56, Karl Hammar wrote:
> [EMAIL PROTECTED]:
> > It also changes the numbering of all subsequent bars. I don't know the
> > author's intent in this case (I didn't write that snippet), but I guess
> > it could be something like an attaca movement.
>
> Yes. The bigger picture is H. Purcells opera "Dido & Æneas":
>
> http://aspodata.se/motett/noter/act*
nice! (will this end up on mutopia?)
> I did not like idea of big bar number, like 543.
> I think it is better with aria/movement 23, bar 25.
You could use something like this (based on print-circled-text-callback in
scm/output-lib.scm) to achieve what you want more cleanly. It works with
2.5.19, but not with 2.4 for some reason.
\version "2.4.0"
#(define-public (print-+100-text-callback grob)
(let* ( ;(text (ly:grob-property grob 'text))
(text (number->string (+ 100 (string->number (ly:grob-property grob
'text)
(layout (ly:grob-layout grob))
(defs (ly:output-def-lookup layout 'text-font-defaults))
(props (ly:grob-alist-chain grob defs))
(text-stencil (Text_interface::interpret_markup layout props text)))
(ly:stencil-add (centered-stencil text-stencil
\new Staff {
\set Score.barNumberVisibility = #(every-nth-bar-number-visible 1)
\override Score.BarNumber #'print-function =
#print-+100-text-callback
\repeat unfold 9 { c1 \break } \bar "|."
}
HTH,
Erik
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
LAC2005
Hi! Just wondering: is there anyone else from this list except me going to the Linux Audio Conference in Karlsruhe/Germany? Greetings, Jürgen Citation from Linux Audio Developers List: -- From: Frank Neumann <[EMAIL PROTECTED]> Date: Tue Apr 12 2005 - 04:21:38 EEST Hi all, the 3rd International Linux Audio Conference(*) or "LAC2005" for short is nearing (21-24 April), and if you have not registered for it yet, now would be a good time to do so. It's free, we are not selling your email addresses (honestly!), and it gives you a real bonus: After a short negotiation with ZKM, we agreed that registered participants have free admission to the ZKM Media Museum and the currently running exhibition "Making Things Public". The Media Museum is quite interesting, especially since you can see a real computer monster in live and stunning action there: Recently, they have acquired a fully working Zuse Z22 from a local college. This lady is really worth being seen. Well, I digress. We hope to see many of you next week at the ZKM in Karlsruhe! The LAC2005 Organization Team: Götz Dipper (ZKM) Frank Neumann (*) http://lac.zkm.de___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Span_dynamic_performer
IIRC, volume is controlled on per-note basis (attack and release; passed
as value parameter to each note on/off command), such that this approach
would not impose any problems. However, almost all other parameters, such
as pitch bend (important for tuning of micro tones), are channel messages,
such that restrictions apply when putting multiple voices into a single track.
Greetings,
Jürgen
On Fri, 15 Apr 2005, Mats Bengtsson wrote:
Stephen wrote:
Note also that these bugs have low priority among developers, since there
are
plans to rewrite the midi system from scratch.>
My comments can be taken two ways, as suggestions for a rewrite of
span-dynamic-performer.cc or as a wish-list for the new implementation. If
I where to contribute to the new implementation, I would need to start by
analysing the drawbacks of the current implementation of midi in Lilypond.
When it comes to things like this, I fail to see the distinction. We learn
from each other, hopefully.
One thing I want to do in midi is to say:
\remove Voice.Span_dynamic_performer
\consists PianoStaff.Span_dynamic_performer
to controll the scope of the dynamic changes, whether they only affect the
voice, the staff, the piano part, of the entire score. I don't know if that
is possible yet.
That will give technical problem, since each Staff context in the .ly
file will translate into one MIDI track (I hope I remember the correct
terminology here) and as far as I know, the dynamics are set per track
in MIDI. One solution is to redefine the MIDI contexts so that the
full PianoStaff is typeset in the same track. Technically, this means
that the PianoStaff context should be changed to be of type
"Staff_performer" and that the ordinary Staff context should have type
"Performer_group_performer". This is done with the following lines
in your .ly file:
\midi {
\tempo 4=60
\context {
\type "Staff_performer"
\name "PianoStaff"
\accepts Staff
\accepts DrumStaff
}
\context {
\type "Performer_group_performer"
\name Staff
\accepts Voice
\consists "Key_performer"
\consists "Tempo_performer"
\consists "Time_signature_performer"
}
Once you have done that, there's no need to move the Dynamic_performer
or Span_dynamic_performer, since any dynamic setting that will appear
within the same track will affect all the remaining notes in the track.
To see the original context definitions for the MIDI processing, see
the file ly/performer-init.ly
/Mats
___
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: lilypond book issues version 2.5.19
> > > It `normalises' the `@' character, so it no longer is of type
> > > `letter'. I also wonder why it's here. Additionally, it should
> > > be
> > >
> > > [EMAIL PROTECTED]
> > >
> > > to make TeX stop parsing after the `2'.
> > >
> >
> > Isn't his what \makeatother is for?
>
> This isn't defined for plain TeX.
>
But lilypond-book produces a LaTeX document, not a TeX document.
> > In any case, it looks like it should _not_ be here, after all
> > someone might "@" in \preLilyPondExample and then get surprised at
> > the result!
>
> I disagree. `@' should *always* be of category `other' for the user.
> If she wants to change that she should explicitly change the catcode.
> This is standard LaTeX practise.
Sorry, I agree, I was confusing \makeatletter and \makeatother! The code
really does nothing here because `@' will already have category `other'
in a normal LaTeX file.
>
> > I should have thought if that since my wife is Chinese! I still
> > think that being able to put a macro between the systems would be
> > useful.
>
> Since LilyPond completely takes care of formatting pages, this isn't
> really useful. Think of LilyPond returning an `image' of a piece of
> music which is accidentally in TeX format. If you want something
> between the systems, make LilyPond do that. Otherwise use two or more
> LilyPond snippets.
When called from lilypond-book, LilyPond does _not_ take care of
formatting the pages. This is precisely the reason I started using it.
So that I can have a multi-movement score with fancy headers, table of
contents, etc. What it does is to break a long score up into several
snippets each of which is included individually. It would be extremely
useful to have a macro that added something between these snippets.
For example in 2.5.19 the code:
\input lily-1105931465-systems.tex
In Text.tex was generated from the _single_ call:
\lilypondfile[indent=1.2\cm]{prelude-d.ly}
It does not result in one postscript snippet being included but six as
can be seen by looking at the contents of lily-1105931465-systems.tex:
\includegraphics{lily-365734716-1.eps}
\includegraphics{lily-365734716-2.eps}
\includegraphics{lily-365734716-3.eps}
\includegraphics{lily-365734716-4.eps}
\includegraphics{lily-365734716-5.eps}
\includegraphics{lily-365734716-6.eps}
% eof - 'eof' is Makefile marker; do not remove.
It has to do something like this because Lilypond cannot possibly know
where one page ends and the next starts. It would be very useful indeed
to be able to put a macro between these calls to \includegraphics.
/Bernard
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Reminder: Some chord symbols still broken in 2.5.19
On Fri, 2005-04-15 at 00:55 -0700, Matthias Neeracher wrote:
> [Since we seem to be moving towards a release candidate, I thought
> I'd repost this bug report. This is the one issue that currently
> keeps my on 2.4.x for my personal needs.]
>
> On MacOS X, it seems that the symbols for x:maj7 and x:m7.5- still
> don't work properly in 2.5.19 (The former is omitted, the latter
> printed as a long box).
> Is this a known bug or is it a platform specific problem?
>
This is font related problem. Lily uses Unicode codepoints, and lets
pango decide which symbol to use. At the moment, Greek Capital Delta is
used for the white triangle, from chord-modifier-init.ly:
whiteTriangleMarkup = \markup {
%% 394 capital delta
#(ly:export (ly:wide-char->utf-8 #x0394))
%% need to have symbol; can't deal with TTF yet.
%\override #'(font-name . "Symbol")
%% 2206 : delta from the symbol font.
% #(ly:export (ly:wide-char->utf-8 #x2206))
%% up pointing triangle
% #(ly:export (ly:wide-char->utf-8 #x25B3))
%% \override #'(font-encoding . TeX-math) \char #77
}
blackTriangleMarkup = \markup {
%% black up pointing triangle
#(ly:export (ly:wide-char->utf-8 #x25B2))
}
Pango should select a font that contains these glyphs. Can you verify
that the standard Mac fonts do not cover these codepoints? Over here,
the i386 version uses LucidaGrande (which actually comes from my Mac, I
believe) for the Delta, but sadly it's not available on Mac due to it
being a .dfont. Nevertheless, there should be many more (free) fonts
with these glyphs.
I see two options:
- draw a triangle by hand (robust)
- making sure that a font with appropriate glyphs is installed.
I guess the first one is better, though.
--
Han-Wen Nienhuys - [EMAIL PROTECTED]
LilyPond Software Design - http://www.lilypond-design.com
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Span_dynamic_performer
Stephen wrote:
Note also that these bugs have low priority among developers, since
there are
plans to rewrite the midi system from scratch.>
My comments can be taken two ways, as suggestions for a rewrite of
span-dynamic-performer.cc or as a wish-list for the new implementation.
If I where to contribute to the new implementation, I would need to
start by analysing the drawbacks of the current implementation of midi
in Lilypond. When it comes to things like this, I fail to see the
distinction. We learn from each other, hopefully.
One thing I want to do in midi is to say:
\remove Voice.Span_dynamic_performer
\consists PianoStaff.Span_dynamic_performer
to controll the scope of the dynamic changes, whether they only affect
the voice, the staff, the piano part, of the entire score. I don't know
if that is possible yet.
That will give technical problem, since each Staff context in the .ly
file will translate into one MIDI track (I hope I remember the correct
terminology here) and as far as I know, the dynamics are set per track
in MIDI. One solution is to redefine the MIDI contexts so that the
full PianoStaff is typeset in the same track. Technically, this means
that the PianoStaff context should be changed to be of type
"Staff_performer" and that the ordinary Staff context should have type
"Performer_group_performer". This is done with the following lines
in your .ly file:
\midi {
\tempo 4=60
\context {
\type "Staff_performer"
\name "PianoStaff"
\accepts Staff
\accepts DrumStaff
}
\context {
\type "Performer_group_performer"
\name Staff
\accepts Voice
\consists "Key_performer"
\consists "Tempo_performer"
\consists "Time_signature_performer"
}
Once you have done that, there's no need to move the Dynamic_performer
or Span_dynamic_performer, since any dynamic setting that will appear
within the same track will affect all the remaining notes in the track.
To see the original context definitions for the MIDI processing, see
the file ly/performer-init.ly
/Mats
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: removing unwanted accidentals
[EMAIL PROTECTED]:
> On Thursday 14 April 2005 21.31, Stephen wrote:
...
> > In the example, '\set Score.currentBarNumber = #1' creates the problem. I
Correct.
> > don't see why the numbering is reset there other than to remove the number
> > from that bar because it collides with the mark "D". There must be another
> > way to suppress the bar number at that bar.
>
> It also changes the numbering of all subsequent bars. I don't know the
> author's intent in this case (I didn't write that snippet), but I guess it
> could be something like an attaca movement.
Yes. The bigger picture is H. Purcells opera "Dido & Æneas":
http://aspodata.se/motett/noter/act*
I did not like idea of big bar number, like 543.
I think it is better with aria/movement 23, bar 25.
>
> > However, I fixed it by setting the accidental style to 'forget'. See? there
> > is already a way to do it.
*No*, the forget does not work for:
act 1, aria 13, bar 6 Violin II: the b is shown with natural
act 1, aria 13, bar 11 Violin I: the f is shown with natural
Elsewhere yes, but not for theese two notes.
I don't know how to solv theese.
If I put another f before bar 11 for V1, that f gets the natural.
It seems that the first f, in this case, gets the natural, and I
tried to insert a \hideNote f \unHideNote, but it was still visible.
Btw, I solved the issue for the other places by starting each aria like:
\set Score.explicitKeySignatureVisibility = #begin-of-line-visible
\set Score.printKeyCancellation = ##f
\key c \minor
when the previous part already was in c minor.
It would be nice if I could write:
\key c \minor \music02
\key c \minor \music03
\key c \minor \music04
\key c \minor \music05
and the key-engraver only shows the key signature when it *changes*.
I tried hack around in lily/key-engraver.cc and doing things like
if (scm_is_eq (last, key)) return, found no solution.
...
>
> Erik
>
> > - Original Message -
> > From: "Erik Sandberg" <[EMAIL PROTECTED]>
> > To:
> > Sent: Monday, April 11, 2005 3:53 PM
> > Subject: removing unwanted accidentals
> >
> > > Hi,
> > >
> > > There seems to be a need for a way to notate that a single note should
> > > _not_
> > > have an accidental displayed, something like a 'force-no-accidental'
> > > property.
Possible, but for this case I would prefer:
1, fixing the bug
2, make key-engraver only show changes
The reason for 2, is that I prefer to put the workaround in one place,
instead of littering down the .ly with bug-corrections, that must be
refound when the bug is removed.
> > >
> > > I think there was a discussion about this over a year ago, without a
> > > conclusion. Now there have been 2 or 3 (implicit) requests for it in a
> > > short
> > > time, and IMHO it's a reasonable feature.
> > >
> > > Also it looks pretty trivial to implement; may I give it a try?
> > >
> > > Erik
> > >
> > > On Sunday 10 April 2005 14.32, Karl Hammar wrote:
> > >> How do I remove the unwanted explicit flats in the next to last
> > >> measure in:
> > >>
> > >> \version "2.4.2"
> > >>
> > >> \relative c'' {
> > >> \override Score.BarNumber #'break-visibility = #end-of-line-invisible
> > >> \mark #03
> > >> \clef treble
> > >> \key c \minor
> > >> a2 b |
> > >> d1 |
> > >> \mark #04
> > >> \set Score.currentBarNumber = #1
> > >> d2 es8. as,16 bes8 c |
> > >> % ^ ^ unwanted explicit flats here
> > >> d1
> > >> }
> > >>
> > >> Regards
> > >> /Karl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Span_dynamic_performer
I forgot to say: The way LilyPond is designed today, you can only have
one MIDI instrument within each MIDI track, which means that the
solution I propose below will work for a PianoStaff but if you try the
same trick on a GrandStaff containing several staves with different
instruments, then your MIDI output will use the same instrument for
all of them.
/Mats
Mats Bengtsson wrote:
Stephen wrote:
Note also that these bugs have low priority among developers, since
there are
plans to rewrite the midi system from scratch.>
My comments can be taken two ways, as suggestions for a rewrite of
span-dynamic-performer.cc or as a wish-list for the new
implementation. If I where to contribute to the new implementation, I
would need to start by analysing the drawbacks of the current
implementation of midi in Lilypond. When it comes to things like this,
I fail to see the distinction. We learn from each other, hopefully.
One thing I want to do in midi is to say:
\remove Voice.Span_dynamic_performer
\consists PianoStaff.Span_dynamic_performer
to controll the scope of the dynamic changes, whether they only affect
the voice, the staff, the piano part, of the entire score. I don't
know if that is possible yet.
That will give technical problem, since each Staff context in the .ly
file will translate into one MIDI track (I hope I remember the correct
terminology here) and as far as I know, the dynamics are set per track
in MIDI. One solution is to redefine the MIDI contexts so that the
full PianoStaff is typeset in the same track. Technically, this means
that the PianoStaff context should be changed to be of type
"Staff_performer" and that the ordinary Staff context should have type
"Performer_group_performer". This is done with the following lines
in your .ly file:
\midi {
\tempo 4=60
\context {
\type "Staff_performer"
\name "PianoStaff"
\accepts Staff
\accepts DrumStaff
}
\context {
\type "Performer_group_performer"
\name Staff
\accepts Voice
\consists "Key_performer"
\consists "Tempo_performer"
\consists "Time_signature_performer"
}
Once you have done that, there's no need to move the Dynamic_performer
or Span_dynamic_performer, since any dynamic setting that will appear
within the same track will affect all the remaining notes in the track.
To see the original context definitions for the MIDI processing, see
the file ly/performer-init.ly
/Mats
--
=
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
Reminder: Some chord symbols still broken in 2.5.19
[Since we seem to be moving towards a release candidate, I thought I'd repost this bug report. This is the one issue that currently keeps my on 2.4.x for my personal needs.] On MacOS X, it seems that the symbols for x:maj7 and x:m7.5- still don't work properly in 2.5.19 (The former is omitted, the latter printed as a long box). Is this a known bug or is it a platform specific problem? Matthias chord-2_5_16.pdf Description: Adobe PDF document chord.ly Description: Binary data ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
