Re: lilypond on FreeBSD?
On Friday 20 October 2006 16:02, Ian Stirling wrote: Some other error occurred trying to compile and install the 2.8 version. Was it by chance something like the following? It appears to be called in by ./mf/GNUMakefile on line 4. Anyone know if that line is important, old debris, or being brought in by a bad build stepon my part? gmake[1]: Entering directory `/mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/mf' /usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -d /usr/home/mirror176/tmp/lilypond/share/lilypond/2.8.7/fonts/source /usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -m 644 ./feta-accordion.mf ./feta-alphabet.mf ./feta-alphabet11.mf ./feta-alphabet13.mf ./feta-alphabet14.mf ./feta-alphabet16.mf ./feta-alphabet18.mf ./feta-alphabet20.mf ./feta-alphabet23.mf ./feta-alphabet26.mf ./feta-arrow.mf ./feta-autometric.mf ./feta-banier.mf ./feta-beugel.mf ./feta-beum.mf ./feta-bolletjes.mf ./feta-braces-a.mf ./feta-braces-b.mf ./feta-braces-c.mf ./feta-braces-d.mf ./feta-braces-e.mf ./feta-braces-f.mf ./feta-braces-g.mf ./feta-braces-h.mf ./feta-braces-i.mf ./feta-din-code.mf ./feta-eindelijk.mf ./feta-generic.mf ./feta-haak.mf ./feta-klef.mf ./feta-macros.mf ./feta-nummer-code.mf ./feta-params.mf ./feta-pendaal.mf ./feta-puntje.mf ./feta-schrift.mf ./feta-slag.mf ./feta-test-generic.mf ./feta-test11.mf ./feta-test13.mf ./feta-test16.mf ./feta-test20.mf ./feta-test23.mf ./feta-test26.mf ./feta-timesig.mf ./feta-toevallig.mf ./feta11.mf ./feta13.mf ./feta14.mf ./feta16.mf ./feta18.mf ./feta20.mf ./feta23.mf ./feta26.mf ./parmesan-accidentals.mf ./parmesan-clefs.mf ./parmesan-custodes.mf ./parmesan-flags.mf ./parmesan-generic.mf ./parmesan-heads.mf ./parmesan-rests.mf ./parmesan-scripts.mf ./parmesan-timesig.mf ./parmesan11.mf ./parmesan13.mf ./parmesan14.mf ./parmesan16.mf ./parmesan18.mf ./parmesan20.mf ./parmesan23.mf ./parmesan26.mf /usr/home/mirror176/tmp/lilypond/share/lilypond/2.8.7/fonts/source/ true (/usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -d /usr/home/mirror176/tmp/lilypond/share/lilypond/2.8.7/tex/ || true) /usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -c -m 644 ./out/feta11.tex ./out/feta13.tex ./out/feta14.tex ./out/feta16.tex ./out/feta18.tex ./out/feta20.tex ./out/feta23.tex ./out/feta26.tex ./out/feta-braces-a.tex ./out/feta-braces-b.tex ./out/feta-braces-c.tex ./out/feta-braces-d.tex ./out/feta-braces-e.tex ./out/feta-braces-f.tex ./out/feta-braces-g.tex ./out/feta-braces-h.tex ./out/feta-braces-i.tex ./out/feta-alphabet11.tex ./out/feta-alphabet13.tex ./out/feta-alphabet14.tex ./out/feta-alphabet16.tex ./out/feta-alphabet18.tex ./out/feta-alphabet20.tex ./out/feta-alphabet23.tex ./out/feta-alphabet26.tex ./out/parmesan11.tex ./out/parmesan13.tex ./out/parmesan14.tex ./out/parmesan16.tex ./out/parmesan18.tex ./out/parmesan20.tex ./out/parmesan23.tex ./out/parmesan26.tex /usr/home/mirror176/tmp/lilypond/share/lilypond/2.8.7/tex/ (/usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -d /usr/home/mirror176/tmp/lilypond/share/lilypond/2.8.7/fonts/otf/ || true) /usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -c -m 644 ./out/emmentaler-11.otf ./out/emmentaler-13.otf ./out/emmentaler-14.otf ./out/emmentaler-16.otf ./out/emmentaler-18.otf ./out/emmentaler-20.otf ./out/emmentaler-23.otf ./out/emmentaler-26.otf ./out/aybabtu.otf ./out/CenturySchL-Ital.otf ./out/CenturySchL-BoldItal.otf ./out/CenturySchL-Roma.otf ./out/CenturySchL-Bold.otf /usr/home/mirror176/tmp/lilypond/share/lilypond/2.8.7/fonts/otf/ (/usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -d /usr/home/mirror176/tmp/lilypond/share/lilypond/2.8.7/fonts/tfm/ || true) /usr/local/bin/python /mnt/ufs/mirror176/ports/print/lilypond/work/lilypond-2.8.7/stepmake/bin/install.py -c -c -m 644 ./out/feta11.tfm ./out/feta13.tfm ./out/feta14.tfm ./out/feta16.tfm ./out/feta18.tfm ./out/feta20.tfm ./out/feta23.tfm ./out/feta26.tfm ./out/feta-braces-a.tfm ./out/feta-braces-b.tfm ./out/feta-braces-c.tfm ./out/feta-braces-d.tfm ./out/feta-braces-e.tfm ./out/feta-braces-f.tfm ./out/feta-braces-g.tfm ./out/feta-braces-h.tfm ./out/feta-braces-i.tfm ./out/feta-alphabet11.tfm ./out/feta-alphabet13.tfm ./out/feta-alphabet14.tfm ./out/feta-alphabet16.tfm ./out/feta-alphabet18.tfm ./out/feta-alphabet20.tfm ./out/feta-alphabet23.tfm ./out/feta-alphabet26.tfm ./out/parmesan11.tfm ./out/parmesan13.tfm ./out/parmesan14.tfm ./out/parmesan16.tfm ./out/parmesan18.tfm ./out/parmesan20.tfm ./out/parmesan23.tfm ./out/parmesan26.tfm
Re: lilypond on FreeBSD?
On Saturday 21 October 2006 00:55, Jan Nieuwenhuizen wrote: We base the FreeBSD binaries on 4.10-RELEASE-p2. Would it make sense to support 6.x as well? If so, we need a binary of the c library to bootstrap the build Version 4 is about as far back as any updates go into FreeBSD right now. 5 is considered old and 6.1 is recommended to users. Look forward to 6.2 (estimated by mid November) as the new 'Release' version: Releases are intended as the most stable workplace for people who want to use something tha works, not as a place to try out the latest new code and bugtest. Months ago things improved in FreeBSD for the ports tree (a collection of makefiles and other files to help users get software installed) which should make porting a newer version of lilypond relatively easy. Libtool was one place I remember trouble in getting the port working right, even when I could compile otherwise. If the port can be made, then package creation should be little more than commands in the ports tree. I will have to take another stab at it again in the very near future. The current version in ports in 2.2.2 and the development version was removed a while back. Some work was done to update it by someone else, but I guess that did not go through with success. As for library versions, I know that multiple versions can coexist (and will do so until programs using old libraries are updated to the newer ones). I am not sure how using an older version is handled if it did not exist on the system already. As some of you out there likely know much better than I, care to clarify any library topics for me; I do accept pointing to documentation as help too. Ed Sutton ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
attemting to fix freebsd 2.5.32 port problems
The only use for output redirect I seem to have anymore is 21, but the configure does many more advanced things; still, what does mean with no numbers? I thought that changing my freebsd ports makefile to #GNU_CONFIGURE= yes USE_AUTOCONF_VER=259 might make a difference; That would force autoconf to be executed, which I thought should rebuild the configure file, and the previous line would get commented as it is implied by the next. Like I say, I do not understand redirects to understand this fix, nor have I been able to ever learn autoconf and other building tools to know where this problem originates from. You may need to manually patch this file; for some reason patch refuses to patch the file on my side and I have not yet found out why. diff -ru ./configure ../../working/configure --- ./configure Fri Jun 24 13:10:02 2005 +++ ../../working/configure Fri Jun 24 13:08:34 2005 @@ -6553,7 +6553,7 @@ EOF FLEXLEXER_PATH=`$CXX -E conftest.cc | \ sed 's!# 1 \(.*\)FlexLexer.h[EMAIL PROTECTED]@\1@@!g' | grep '@@' | \ - sed '[EMAIL PROTECTED]@\(.*\)@@.*$!\1!g' ` /dev/null + sed '[EMAIL PROTECTED]@\(.*\)@@.*$!\1!g' ` /dev/null rm conftest.cc echo $as_me:$LINENO: result: $FLEXLEXER_PATH 5 Is there a reason why the check in autogen.sh checks for autoconf2.50 when =2.50 work? freebsd has no 2.50 that I am aware of, but 2.53, and 2.59 are available in ports (I wonder where 2.57 went). on freebsd they are called autoconf253 and autoconf259 and are stored in /usr/local/bin by default. Line 24 of ./Documentation/pictures/GNUMakefile seems to get interpreted as if icotool is a command when attempting to build it with ports. I'll try to diagnose later, but it seems to go weird if when not manually configured because a manual autogen.sh seems to be all it needs. #convert +adjoin out/lilypond-48.png out/lilypond-32.png out/lilypond-16.png out/lilypond-48-8.png out/lilypond-32-8.png out/lilypond-16-8.png out/lilypond.ico icotool --output=out/lilypond.ico --create out/lilypond-48.png out/lilypond-32.png out/lilypond-16.png out/lilypond-48-8.png out/lilypond-32-8.png out/lilypond-16-8.png gmake[2]: icotool: Command not found gmake[2]: *** [out/lilypond.ico] Error 127 Am I having fun yet, Ed Sutton P.S. all this compile time is depriving seti =( ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 3.0
Lilypond 2.3 is marked as broken on freebsd. Now that I'we moved to freebsd, I notice a lot more when the luxury of an up to date lilypond doesn't exist. I will try to do what I can to help straighten it out before 3.0. Has anyone heard form Patrick Atamaniuk (the freebsd packager)? I have had no luck reaching him. Han-Wen Nienhuys wrote: Hi guys, 3.0 is almost ready. For the 3.0 release 1. I've put back TeX as the default backend. I welcome patches that will Do The Right thing for encodings and landscape options of \bookpaper. 2. I will have a another look at slurs across line-breaks I propose to release 3.0 once Item 2. is dealt with. I expect this to happen in 1 to 2 weeks. Of course, if there are any very pressing bugs reported on the mailing list, I will try to fix those as well. There is also some other good news: some of the dependencies for the LilyPond GNOME backend have been released or are almost ready to be released. This means that in a short while we will have native point-and-click, without requiring TeX or DVI. ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Uncommon feature: colors
On Thursday May 20 2004 05:36, Marco Gusy wrote: One feature I always looked for in a score program was colored notes (unsuccesfully, of course). It seems a stupid feature, but I think it could be very useful in fugues studying: with this technique you could highlight subject, answers, countersubjects. Do you think this is possible to implement? http://mail.gnu.org/archive/html/lilypond-user/2004-04/msg00039.html and http://mail.gnu.org/archive/html/lilypond-user/2004-04/msg00040.html should make for some quick reading material for you; its recent too. ___ lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Slur bugs
On Tuesday May 4 2004 10:57, Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: Hi, I have gotten the impression that the system that handles slurs (positioning, shape, collision, ..) is broken and will be completely rewritten sometime. IIRC I got this impression from some discussions during early 2.1 development. Am I right? And in that case, are there any plans of when this is going to be done (pre- or post-2.4)? You are right, but there is no time-frame for this replacement. We will be busy with the changes for 3.0 for a some time still. This information is very relevant for me since I should ignore bugreports about bad slurs (or, rather, consider them 'future' bugs) only if my impression was correct. yep. Would it be worth updating the manual to bring this out more? Perhaps a mention of it in the 'bugs' section of the slurs page. ___ lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Bug repository UPLOADED!
On Wednesday April 21 2004 14:58, Erik Sandberg wrote: I would however be the only one who actually removes the files from the repository; this because I think it's a good idea that someone always should double-check that the bug really was fixed. I hope that unverifiable bugs have a removal process when it is suspected that they don't/no longer exist. Good work, Ed ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Lily 2.2 on linuxfr !
On Tuesday April 13 2004 05:46, Mats Bengtsson wrote: Interesting to see such a long list of comments at linuxfr in just a few days. Too bad I don't understand French. http://babelfish.altavista.com/babelfish/tr?lp=fr_enurl=http% 3A//linuxfr.org/2004/04/08/15968.html /Mats Olivier Guery wrote: Hello, just here to say that our favourite music engraver is in the news on linuxfr, just see here : http://linuxfr.org/2004/04/08/15968.html Némo. -- Olivier [EMAIL PROTECTED] ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-deve l -- NOBODY EXPECTS THE SPANISH INQUISITION ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Lily 2.2 on linuxfr !
On Tuesday April 13 2004 14:40, Pedro Kroger wrote: * Nicolas Sceaux ([EMAIL PROTECTED]) wrote: Bonjour Mats! Tue, 13 Apr 2004 14:46:32 +0200, tu as dit : Interesting to see such a long list of comments at linuxfr in just a few days. Too bad I don't understand French. for some reason (firewall?) I can't access the page :-( Would some good soul send a copy to my personal email? I'd be very grateful. Just French, or a (rough) translation preferred. Pedro ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel -- All Finagle Laws may be bypassed by learning the simple art of doing without thinking. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Piano Pedal performace across a PianoStaff
On Tuesday April 6 2004 03:02, Han-Wen Nienhuys wrote:
[EMAIL PROTECTED] writes:
A pedal-event is currently performed by the staff context within
which it is declared. As a piano's pedal tends to affect the entire
output of the piano and not just one hand, it would be nice if
pedal-events could be automatically performed across the staves in a
PianoStaff. My instinct was to use the following:
\context {
\VoiceContext
\remove Piano_pedal_performer
}
\context {
\PianoStaffContext
\consists Piano_pedal_performer
}
but I can see that I was wrong. What would be necessary to make
something like this work? I am willing to code it, but I would
appreciate a push in the right direction.
It's probably the easiest to make a Piano_pedal_swallow_performer that
sits at the piano-staff level, and have that scoop up the events. Then
have Piano_pedal_performers at staff level. This is similar to
Repeat_engraver which cooperates with the Repeat_acknowledge_engraver.
Let me know if you have more questions!
I thought about this recently for both dynamic and pedal marks. I thought 4
tracks (RH, LH, dynamics, pedal) on one channel would distribute all the
changes. Either my midi knowledge is wrong or/and that couldn't work well
about how a mark would be handled if it applied to only one line. I don't
want to start hate mail and fired discussions, but better notational midi
knowledge is something I can always use so . . .
Thanks again,
Ed Sutton
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: metronome mark problems
On Monday March 29 2004 04:00, Mats Bengtsson wrote: You can do this with \markup today, see the mailing list archives, for example http://mail.gnu.org/archive/html/lilypond-user/2003-12/msg00013.html It isn't so much of wether or not I can, but rather that I have to if I want to place it right. I usually just use \tempo because it already goes where it should, is small enough to generally not cause collision problems for me, and I still have not been able to figure out what property the padding applies to (I know, it's waiting for me in the e-mail archives). In any case, tempo expressions are, in my experiences, very common; I can't seem to recall the manual explaining the right way to fully typeset these. Examples of some control are scattered about the manual, but most musicians I know would be completely clueless about what professionals do. The important thing right now is that LilyPond does have a way that I can make things look right (or however I desire) so thank you again. Since you are always so helpful Mats, do you have suggested readings to try to help me straighten out my sense of the various object types; I seem to mix them up horribly anymore. =( Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: rotated hairpins
On Sunday March 28 2004 13:58, Jan Nieuwenhuizen wrote: Btw, are you sure that mere rotation is enough? I seem to remember that the non-horizontal wing should be lengthened too. If you are talking about the opening having a vertical slope between the end of the bottom and top lines, I haven't studied this but have generally observed the resemblance of it, rather than the opening being perpendicular to the hairpin direction. I don't know wether it is intended or not though since it seems in most of those examples that one line or the other was usually made longer, even on horizontal ones (nobody's perfect). On Sunday March 28 2004 14:04, Werner LEMBERG wrote: Hairpins are not rotated if the vertical delta of start and end point is smaller than the threshold. I thought that the hairpins were angled to fit tighter spaces, such as between two crowded staves, rather than to follow the change in pitch. I don't have any old sources showing consistency with any ideas here. If it isn't a normal LilyPond option, I'd like to at least see how to tweak it to have the professional look; it's the LilyPond way and hopefully you guys know the right from wrong again. Thanks again, Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: metronome mark problems
On Sunday March 28 2004 14:40, Werner LEMBERG wrote: % . Assuming that the metronome mark affects the following input, it % shouldn't be located over the time signature. Where should it go? I've been manually moving tempo markings to be left-aligned with the time signature after people I've discussed typesetting with told me that they should be aligned like that. This is why markup text has been frustrating for me; I have been moving them to left align the time signature manually and just find it easier to use the metronome markings. Will there be text based metronome markings in the future that way something like 'Adante' could be placed consistent to other metronome marks? ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Documentation of Architecture / Design?
On Monday March 22 2004 06:53, Bertalan Fodor wrote: I think advanced users often use this reference, so what about calling it Advanced Reference or a similar name, which is from a user's point of view. I have also misinterpreted the name Program Reference as Programming Reference. I don't really have any better suggestion, though. A long name could be Full documentation of all contexts, objects, properties, ... but we need something shorter. Well, what about the program is described in the reference; is it about advanced useage, is it trying to be an entire syntax reference? A suitable name can probably describe what it is all about. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: minor slur problem
On Wednesday March 24 2004 16:20, Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: % % This file shows a problem with broken slurs in staves having different % sizes in lilypond CVS 2004-03-23 21:42 MET. % % . The starting point of the continuation of a broken slur is offset % too far to the left in the smaller staff. Why? where do you think it should start? I know some other things are restricted to an imaginary line that they cannot pass (or so I have heard), such as a resumed melisma should start at the end of the key signature. Does something like this apply to slurs? One starts before the end of the clef, and the other does not start until sometime after the right edge of the clef. If I (or these ideas) are wrong for typesetting, I'd like to know that too. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Dynamic questions
http://lilypond.org/doc/v2.1/input/regression/out-www/lily-1175767955.ly
mentions that something like /ff/ will appear on the same horizontal level.
Should other markings, such as cresc, do it too? My guess is that
\set crescendoText = \markup { \italic cresc. poco }
a'2\ a a a\!\mf
from the dynamics section of the manual works, but that something like
a\f\cresc a a\!\ff
would not follow that the same way.
Should a consistency between the space between the crescendoSpanner being
adjacent to the preceding crescendoTextand and the space between
crescendoSpanner and where it ends (particularly, for example, when ending
next to another dynamic). Sometimes it seems to work like
cresc.- - - f
and othertimes its like
cresc.- - -f
depending on spacing. In the manual, there is an example even showing the last
dash shrunk down; it almost seems to be a dot.
If the current working is preferred, or others are not implemented for some
reason, that works for me too; I didn't find any mailings I could notice to
be relevant, and the manual doesn't mention a word one way or the other which
lead me to assume that it either works as desired or hadn't been looked at
like this yet.
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Rectangle around the note head
On Sunday March 21 2004 10:31, Matevz Jekovec wrote: Edward Sanford Sutton, III wrote: On Friday March 19 2004 15:25, Matevz Jekovec wrote: I was searching the documentation a bit for a feature which draws a rectangle around the certain note head (or streched around 2 notes when punctuated over the bar). We use this kind of arrangement, to mark a note that is the highest in the line (the melody climax) in our contrapunkt class and I think this has become a standard for all the contrapunkt classes around. Can anyone help me out? I'm sure you're way too busy with other lilypond features, so if this marginal feature is not already possible or there is too much work to implement it, I really apologize for your time. The development version has balloon help: http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Balloon-h elp.html#Balloon% 20help which his sounds like what you wanted for a single notehead. I think that using this feature as it stands would require the two notes be marked separately if there are two of them that you want to mark. Otherwise, if using balloon help as it is, you could see if it is acceptable to just mark the first. Yes, that's exactly what I had in mind, thanks. Btw, are there any parameters to disable the line pointing out of the note at all (right now, the whole and half notes have a black dot inside them if the text is and coordinates are 0 . 0) and a way to change the rectangle size? I don't know if the balloon-padding interface changes the size of the box or tries to just shift it around on the page; I haven't played with the balloon feature myself. Perhaps some people would prefer the line connecting to the text to go away when there is no text and/or have an option for wether it is present or not. Some people might want just the box, and some people might want a line to blank space for writing on later. What does everyone else think? Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Rectangle around the note head
On Friday March 19 2004 15:25, Matevz Jekovec wrote: I was searching the documentation a bit for a feature which draws a rectangle around the certain note head (or streched around 2 notes when punctuated over the bar). We use this kind of arrangement, to mark a note that is the highest in the line (the melody climax) in our contrapunkt class and I think this has become a standard for all the contrapunkt classes around. Can anyone help me out? I'm sure you're way too busy with other lilypond features, so if this marginal feature is not already possible or there is too much work to implement it, I really apologize for your time. The development version has balloon help: http://lilypond.org/doc/v2.1/Documentation/user/out-www/lilypond/Balloon-help.html#Balloon% 20help which his sounds like what you wanted for a single notehead. I think that using this feature as it stands would require the two notes be marked separately if there are two of them that you want to mark. Otherwise, if using balloon help as it is, you could see if it is acceptable to just mark the first. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: CVS problems (savannah down?)
On Thursday March 18 2004 17:20, Matthias Kilian wrote: Hi, is it only me who can't access the CVS server at savannah.gnu.org for the last three days? Even ping or traceroute don't get a response. However, some recent mails on the LilyPond lists made me think that some people get connections to the server. That's really odd, and it's not a problem of my provider (a friend had the same problem from a t-online access). Ciao, Kili, suffering LilyPond-Junkie I've felt like it goes up and down... ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
reading material?
My main problem with attempting linux programming has been not knowing where to start. I find when I've tried to jump in on code in one project or another, I get headaches from errors about not being able to write to a 'variable' I defined because they got me to create what was really an object, which I only messed with a bit in c++ and not c like the current project was in. I've got a rather handy reference book for c/c++, but that was written to include borland's turbo c++ and requires a more powerful one for some projects in the book (it even ends with a touch at windows gui programming). I was wondering if anyone could suggest references they use for the gnu c++ and python (that'll be a new one for me) that can help get me up to speed for linux programming (and hopefully understanding the lines of LilyPond code more than just vaguely). If something like info docs are preferred, where should I start with those? I know there are coding guidelines mentioned on the site, but I don't know of any sort of getting started type of docs. =( Thanks for any feedback, Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: compilation error
On Monday March 8 2004 04:26, Mats Bengtsson wrote: I actually find that the depencies are well documented in INSTALL.txt, what information did you miss? Of course, it may sometimes be tricky to find out what RPM/.dpkg contains the necessary programs and files but that's hardly a LilyPond problem. My current stopper for building docs is a gs failure which I am guessing is due to my state of running font-deprived. I don't see any reason why they would actually state the requirements unless they're kinda odd; I think I've only got the basic of the basics in my available fonts now. Maybe I shouldn't have done that since I know so little about working with (/adding) fonts under linux. Maybe I'll figure it out if I have time this next week; It's my busy spring break... =) The deps I needed were otherwise mentioned so far and reading readme/install files of those or config output makes it easy to figure out what I needed for those too when necessary. LilyPond goes to the extent to leave dependencies trackable just by reading and for this I am once again thankful for how well LilyPond is developed. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: compilation error
On Tuesday March 2 2004 16:44, Jan Nieuwenhuizen wrote: You are right. Maybe we are sending conflicting messages: do not compile Lily! Help us (with the docs), send patches! I've still got a little bit of work ahead of me to make it so I can compile docs myself, but yet I still try to help with the docs the best I can. What to do? Maybe we should just change the 'do not compile' attitude a bit, and have 'supported' development platforms with a detailed recipe to compile lily. The contributers of binary releases should make sure that the recipe stays up to date. Would this work? I think a 'do not compile' attitude, as does a 'supported platforms' limitation, creates an atmosphere where the thought of 'open source' is not feeling so open to people. Compiling LilyPond has helped me reduce my linux ignorance and also become aware of some dependencies which are pretty cool programs themselves (thank you again). Of all the problems I've had trying to get programs to compile, I've had worse problems and spent longer trying to deal with packages. Just keep it 'workable' and I might just yet be able to build my lilydocs again. Still thankful... Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: compilation error
On Monday March 1 2004 10:36, Jan Nieuwenhuizen wrote: Same goes for SVG output and a number of FOO2ly import scripts. I personally wish the scripts were better. I don't know how I would find it good to implement them though. The midi2ly didn't seem to pay much attention to what I said about the key and was printing all notes as ?is rather than ?es. Finale did the ?es but without a key sig (and did other stuff I particularly hated). My private lessons instructor for trombone has interest in LilyPond since I've been showing its output off to him. He has a lot of music entered into encore, which is an old program he runs on his mac computers. He would probably switch to LilyPond if he could import those scores; I haven't found any word on encore anywhere besides from him though. It can spit out into midi and into another format that is used on some electric keyboard, synthesizer, or piano. Are you guys up for hire on helping him get the docs to be able to be imported. Since he has such a large archive, I could talk to him about perhapse hiring your services (as I heard was an option in the past through lilypond.org). If importing encore rather than midi would be preferred, maybe he might even consider allowing some hardware with software be 'borrowed'. Not being able to nicely port his archive to another program is one reason why he still keeps that stuff up and in use. ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
virus info/fix
The following link has virus details to what I suspect has been flooding lilypond email lists lately. I am only assuming since I have no up to date antivirus system to test them against right now. Confirmations appreciated. Reading the following page can help educate windows users about the virus. the section #removalinstructions explains how to remove it, but I think it requires norton antivirus in particular. If manual removal details are desired, email me and I will come up with what I can (win9x machines are my primary familiarity). ...now back to my doc correcting... http://securityresponse.symantec.com/avcenter/venc/data/ [EMAIL PROTECTED] ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: Separate release notes for each release?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tuesday February 24 2004 19:05, Reuben Thomas wrote: As well as the cumulative 2.0-2.1 release notes, it would be very helpful to have per-release release notes, so one can see what has changed between individual releases. Dates attached to the changes, or what version they were changed for would be two useful ways to doc that. Are new changes always added to the top? -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAPC4i+mws0jizTrwRAnSnAKDV3nfGlui5dJOPNsJtNIC+v1D90gCg5Eqq QK5BtHT+CdDhyPcjxkeD2Ig= =BMAW -END PGP SIGNATURE- ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: SF s during dynamic spanner.
Sorry, I noticed this at least a few days ago too (v2.1.23 here right now). If
I remember right, the template for pianodynamics has that problem. I thought
it just wasn't following dynamics in the dynamic line, perhaps to the 's'
notes. I think it has always printed as desired though for output. The
following change eliminated that error for me (if I remember right).
\translator {
\type Performer_group_performer
\name Dynamics
\consists Piano_pedal_performer
% \consists Span_dynamic_performer
\consists Dynamic_performer
}
I'll try to read postings, but will be quite busy until at least next Tuesday
evening.
On Thursday February 19 2004 03:32, Mats Bengtsson wrote:
This bug occurs also in 2.1.25. One workaround is to typeset the
\sf in another voice, for example by
c-\ d e \\ s-\sf f-\!
/Mats
Ralph Little wrote:
Hi,
I noticed this recently.
I'm not sure how to get around it
Lilypond 2.1.19 (2.1.2 as well I think).
---8---8--
-8--
\score {
\notes {
\relative c' {
c-\ d e-\sf f-\!
}
}
}
---8---8--
-8--
I get:
lilypond (GNU LilyPond) 2.1.19
Running usr...
Now processing: `test.ly'
Parsing...Interpreting music...
/home/ralph/music/test.ly:4:19: warning: can't find start of
(de)crescendo:
c-\ d e-\sf f-\
!
Regards,
Ralph
-
Tribal Data Solutions has moved, please visit our website for more
details http://www.tribaldata.co.uk. This e-mail and any attachments are
confidential and are sent on the basis of our copyright, e-mail and
security policy which can be inspected by visiting
http://www.tribaldata.co.uk/policies.asp. If you are not the intended
recipient, please notify the sender and delete this message. Thank you.
---
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: anther rest buglet
On Sunday February 15 2004 08:40, Werner LEMBERG wrote:
Well, maybe tweak isn't the right word; however, I am afraid that
having the position depend on the neighbors will open a can of
worms, and won't do the Right Thing in most cases anyway.
Hmm, my thinking was different. In the example I sent to you, I don't
want that the position of the left rest affects the position of the
right rest. I agree with you that this is quite difficult to manage.
Instead, the right rest should be shifted down because the whole note
in the other voice is still `active'. With other words, the duration
of a note should be a kind of spanner which influences the positioning
of rests in the other voice. Another useful application of a `spanner
duration' would be the length of lyrics extender lines. In the
attached example, the extender line shouldn't stop after the second
notehead but extend to the end of the bar. Finally, it could solve
the problem of the following input:
\score {
\notes
\relative c' \new Voice {
g1 |
}
\lyricsto \new Lyrics \lyrics {
foo __
}
}
Lilypond gives a lot of warnings and doesn't print the extender line.
Werner
Another idea of this could be wether or not to use this on dynamics; right
now if a \ is attached to the first note, and you wanted it to end at the
end of measure 2, the only way I am aware of to do that is to attach the end
to 's' notes in the second measure. As such, I usually attach the end to the
note in the next measure, since that is where I intend for the cresc to end,
but I don't know if that is the preferred way or not. It leads to hairpins
being broken over barlines becoming more likely. I only recall seeing this in
use from horrible layouts I did in finale, but I'm sure that some are
probably in publications too.
Ed Sutton
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
control of lyrical spacing from staff
I have a score with a piano and 2 voice staves. The lyrics for the first voice seem closer to the dynamics of the second voice than they do to the notes of the first voice (which doesn't go below middle c if I remember right). Even if it isn't quite right to do so, I wanted to move the lyrics closer to the staff since I think it could make it look better and it should be easy to get that last staffline off of page 3 when printing individual singer parts. Should I really just squeeze horizontal spacing instead to make it work out? It's a copy of a copyrighted publication that I put into lilypond to correct mistakes, print off individual parts to make it less confusing for the elementary school kids to read, and be able to put together midi recordings for accompaniment and so they can hear how the melody of their part goes based on pitch and rhythm. As such, I assume it wouldn't be the wisest idea to just post the whole thing up as an attachment to a publicly available list, but if snippets are OK, I'll do that. I could also write up equivalent short samples to express any issues I'm trying to sort out if those would help. Thanks again, Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Sangers Morgenlied
I haven't searched out my paper with my other notes yet, but here goes all things i can remember that were even worth commenting on. I am left wondering which would be correct, and which match the original still since I have yet to acquire an original score: Dynamics: The usual piano dynamic centering issue. Can measure 6 use the cresc. command (which may have further future midi output benefits)? Should 'Lieblich, etwas geschwind' (and other markings at the start of songs) line up with the time signature? Usually I hear that is what should be done when I hear rules on it. 16th note spacing at the end of measure 4: How close should they be allowed to get to each other and to the barline? Are they spaced closer than the previous four 16th notes because of lyric spacing demands? Should all 16th notes in that measure be spaced more equally? Measure 4 hairpin decresc.: Seems it was moved to make it look nice for when the score was more than 1 page. Now it specifically collides with a stem. Measure 8: fermata in piano right hand, on the rest, collides with the 16th note to its left when the score is compressed down to 1 page. I'm off for some well needed sleep now, Ed Sutton ___ Lilypond-devel mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/lilypond-devel
Re: grace slur and de/crescendi
I personally agree more with attaching centered or to the right of the
starting note over starting it on the note's left. As for the right, I've
seen both styles at barlines where it ends before and it ends at the note
after the barline, and usually prefer the appearance of it cutting off before
because of how it doesn't split as often across new lines.
The last dynamic does seem a little high to me. I'll do my research before
voicing more than my observed opinions; I've only technically learned that
piano dynamics should usually be centered.
As for slurs, maybe consider looking at http://lilypond.org/doc/v2.1/input/
regression/out-www/lily-1931220523.ly to understand the decisions being made
about attachment.
On Thursday February 5 2004 04:00, Olivier Guryry wrote:
Hello,
I'm tring to type the clarinet concerto of Mozart and here are two
small reflexions :
% The slur between grace notes and note shoud be attached to the head
% of the note, but here he's attached to the stem.
% I can change this with :
% \property Voice.Slur \override #'attachment = #'( head . head )
% But it should be the default, am I wrong ?
%
% In my printed scrores, the de/crescendi begin under
% the left side of the note and end under the head attachement of
% the stem, exept if there's a bar just after, in this last case
% (who occure very ofen) the de/crescendi end just before the bar.
% Here they begin center on the note head and stop on the left side.
%
% IMHO the first way is cleaner (maybe it's just an old habit).
\version 2.1.18
\include english.ly
\score {
\context Staff \notes \relative c'' {
e8.[\( \
\grace{f32[( e d e]} f16]) g8.[ \grace {a32[( g f g]} a16])
bf8-. e,-.\)
\! g4( \ f) \! r4
}
\paper { linewidth = -1 }
}
% EOF
I hope my explanations are clear (more than my english).
Olivier.
--
I can't complain, but sometimes I still do.
-- Joe Walsh
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
