Time Signatures separate staff - LSR 272

I'm creating a separate staff for time signatures using the method described in LSR272 [1]. It works well, except for the case where any voice has a clef change at a barline. Then the time signature centre aligns itself with the left edge of the clef instead of the barline. This can be fixed by set

Re: Vertical stretching of groups

Am Sonntag, 22. Juni 2008 schrieben Sie: > So, maybe I'm too naive about the LP internals to discuss this one, > but it seems like the current LP structure is close to providing what > Reinhold describes, at least within systems of music. Currently, the > keep-fixed-while-stretching property can be

Vertical Collision

Hopefully someone can help me with this. I'm pretty new at using LilyPond, but I'm trying to engrave some of my marching band music using it. I have a tuplet with a marcato marking underneath, and I cannot figure out how to keep the marcato marking from colliding with the tuplet. I've included a

Re: Vertical Collision

Hi Jeffrey, 2008/6/22 Jeffrey Vos: > I'm pretty new at using LilyPond, but I'm trying to engrave some of my > marching band music using it. I have a tuplet with a marcato marking > underneath, and I cannot figure out how to keep the marcato marking from > colliding with the tuplet. I've included

Re: Lilypond on OSX

Hallo Steve, I can totally live without the gui. If the only thing is I have to run the command line PPC version, I can live with the long load time. You might want to try one of the alternatives on (there's a link to this page on the LP downloa

Lilypond-LaTeX on Mac OS X (TeXShop & Lilypond 2.11.x)

Hello all, Has anyone been able to get Lilypond-LaTeX to work on Mac OS X since '--psfonts' was deprecated (2.11.xx)? I'd appreciate hints on how to get it going again... Thanks, Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://

Re: Lilypond-LaTeX on Mac OS X (TeXShop & Lilypond 2.11.x)

Hi all, I've almost got it going, but I keep getting the error global name 'set' is not defined Any hints would be appreciated. Kieren. ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Is my approach sane?)

I've long wanted the mutopia O Magnum Mysterium transcribed by Jeff Covey with apparently much help from jcn to build with any current version of lilypond. With the help of the excellent new documentation and several of the people here I have it working fairly well. I want it to print the cho

Re: Is my approach sane?)

Hi Patrick Yes, a new \score is the easiest way to introduce a different staff arrangement. Trevor - Original Message - From: "Patrick Horgan" <[EMAIL PROTECTED]> To: "Mailinglist lilypond-user" Sent: Monday, June 23, 2008 10:45 PM Subject: Is my approach sane?) I've long wanted

Re: Lilypond-LaTeX on Mac OS X (TeXShop & Lilypond 2.11.x)

See http://lists.gnu.org/archive/html/lilypond-devel/2008-03/msg00216.html Cheers, - Graham On Mon, 23 Jun 2008 15:58:34 -0400 Kieren MacMillan <[EMAIL PROTECTED]> wrote: > Hi all, > > I've almost got it going, but I keep getting the error > > global name 'set' is not defined > > Any hin

Re: The LilyPond Report: a new weekly opinion column about Lily's world

Greetings everybody, A new issue is out: http://valentin.villenave.info/The-LilyPond-Report-13 This week we'll talk a bit more about how Free Software, and particularly LilyPond, is developed, evolves, and ends up having a life of its own. We'll also talk 3D gaming, spectacular visualizations, b

Re: Lilypond-LaTeX on Mac OS X (TeXShop & Lilypond 2.11.x)

Graham: See http://lists.gnu.org/archive/html/lilypond-devel/2008-03/msg00216.html Thanks! Changing lilypond-book to start with #!/usr/bin/env python seems to fix the problem when lilypond-book is called (manually) from the command line... But I still get the same problem (as seen in

Re: Lilypond-LaTeX on Mac OS X (TeXShop & Lilypond 2.11.x)

On Mon, 23 Jun 2008 22:31:06 -0400 Kieren MacMillan <[EMAIL PROTECTED]> wrote: > Graham: > > > See > > http://lists.gnu.org/archive/html/lilypond-devel/2008-03/msg00216.html > > Thanks! Changing lilypond-book to start with > > #!/usr/bin/env python > > seems to fix the problem when lilypo