Re: Bug report: initial grace note causes redundant clefs and time signatures

Am 30.04.2009 um 02:26 schrieb Fred Lunnon: I'm not top posting. %{ Lilypad v2.12.2 running on Mac G4 Powerbook under OSX v3.9 A grace note at the start of the first bar causes redundant and default clefs and time signatures to be printed, splitting the grace note from its companion note. A

Re: New fonts for chords

On Tue, Apr 28, 2009 at 5:39 AM, Valentin Villenave wrote: > 2009/4/28 Andrew Hawryluk : >> Valentin, is this worth logging an enhancement in the issues list? >> Perhaps as part of the whole question of high-quality typesetting? > > I am willing to open as many requests as needed, but we need to k

Re: Is there a better way of automating pitch changes of repeated phrases

What I am forced to do is set a different transposition command after each variable. I get the result, but wondered if there a more elegant manner. I don't know if it is a more elegant solution but here is a quick solution if you have a lot of practice exercices to do. %%

Re: Hiding accidental for tied note after line break

Hi Thomas, I don't know why LilyPond actually does this, I find it annoying too. You can remove the accidental at the line break by setting the break-visibility property: \once \override Accidental #'break-visibility = #all-invisible You can read more about this property in 'NR 5.4.6 Visibilit

Hiding accidental for tied note after line break

Hi, I do not want to display an accidental for a tied note after a line break (lilyponds default is to diplay one [why?]). \once \override Accidental #'stencil = ##f or \once \override Accidental #'transparent = ##t works, but the tie at the beginning of the line gets shortened to reserve sp

Re: adding to the LSR

Jonathan Kulp wrote: Carl D. Sorensen wrote: Cool! I still think that you ought to put it all (including the grep part) into a single script and store it in the source tree. And it ought to be added to the CG so that we have it tracked for the next time we release a stable version (I assume

Re: More issues with vertical dynamics placement (to conserve vertical space)

On Mittwoch, 29. April 2009 18:55:13 Reinhold Kainhofer wrote: > Thanks to the nice solution by Neil, I was able to move the dynamic signs > inside the staff, but I'm still running into several problems, mainly in > connection with hairpins... Attached is a sample file with all the issues > and som

Re: adding to the LSR

Carl D. Sorensen wrote: This was a very simple script. I learned a good bit of scripting with the help of Patrick Horgan a while back when I was writing my lily2image script. Here's the script for any interested folks (first I did "convert-ly -e *.ly" on the whole directory): #!/bin/bash #***

Re: memory problem?

Valentin Villenave wrote: 2009/4/29 David Bobroff : Cannot allocate memory How much RAM and swapfile amount do you have? 2Gb physical RAM. On the coLinux side there is a swap file that claims to be 524,288kb (512Mb?) and on the Windows side the paging file for virtual memory is 2,046Mb.

Re: adding to the LSR

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mittwoch, 29. April 2009 15:57:18 Valentin Villenave wrote: > 2009/4/29 Graham Percival : > > 2009/4/29 Graham Percival : > > Yes and no. It would be a great strategy, if we had any clue what > > the status of LSR was. Until we have some kind of i

Re: memory problem?

2009/4/29 David Bobroff : > Cannot allocate memory How much RAM and swapfile amount do you have? Regards, Valentin ___ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user

Re: adding to the LSR

2009/4/29 Graham Percival : 2009/4/29 Graham Percival : > Yes and no. It would be a great strategy, if we had any clue what > the status of LSR was. Until we have some kind of indication as > to when the change can happen, and how it should happen, I > question whether any of this work is worthw

Re: adding to the LSR

On Wed, Apr 29, 2009 at 03:17:46PM +0200, Mats Bengtsson wrote: > > Graham Percival wrote: >> >> I'm not certain this is necessary. OK, it might be good to use >> word-matching for "\octave " rather than string matching >> "\octave*", but that's no unique to this occurrance. >> (no, I don't know t

Re: adding to the LSR

Graham Percival wrote: Yes, I was thinking the same thing but I don't know how to change the convert-ly rules. It was easier for me just to change \octaves to \makeOctaves. Any Frog willing to take on this convert-ly rule fix? You have a file that you can use to see if you have fixe

Re: alignment of slurs and articulations

2009/4/27 Matt Huber : > Hello~ > > In the following code snippet, the slur marks are placed below (outside?) > some of the articulation marks (marcato/portato[-^/-_]) but are above > (inside) all the other articulation marks. How do I correct this so slurs > interact with marcato the same as they

Re: How to create 'Trumpet' fingerings (vertical) above notes

pkx166h wrote: Just for other users if they search the forum as it isn't obvious from the documentation and there is a TBC section too. I figured it out by trial and error - simply concatenate multiple ^ statements i.e c^1^2^3 which gives you a note with 3 2 1 (top to bottom) above the note

Re: end bar for all staves?

Patrick Braun пишет: Hi aĺl, I just wrote a choirstaff (4 voice, 2 staves) that looks like (see below) I now want to give the whole thing an end bar for both staves (and not only per staff). I've perused the manual and the snippets and can't find a single suit. They all use grandstaff which dr

Re: end bar for all staves?

Hi, could this snippet be help for you? -- Marek Klein http://gregoriana.sk 2009/4/27 Patrick Braun : > Hi aĺl, > > I just wrote a choirstaff (4 voice, 2 staves) that looks like (see below) > I now want to give the whole thing an end bar for both staves

How to create 'Trumpet' fingerings (vertical) above notes

Just for other users if they search the forum as it isn't obvious from the documentation and there is a TBC section too. I figured it out by trial and error - simply concatenate multiple ^ statements i.e c^1^2^3 which gives you a note with 3 2 1 (top to bottom) above the note vertically. Thanks

alignment of slurs and articulations

Hello~ In the following code snippet, the slur marks are placed below (outside?) some of the articulation marks (marcato/portato[-^/-_]) but are above (inside) all the other articulation marks. How do I correct this so slurs interact with marcato the same as they do with standard accents? \versio

end bar for all staves?

Hi aĺl, I just wrote a choirstaff (4 voice, 2 staves) that looks like (see below) I now want to give the whole thing an end bar for both staves (and not only per staff). I've perused the manual and the snippets and can't find a single suit. They all use grandstaff which draws all the bar lines rig

memory problem?

I'm having a problem that I don't understand. I have a file which makes a book of etudes. I'm using a series of \bookpart{} blocks inside a \book{} block. When I try to run the whole thing I get this at the end of the terminal output: Layout output to `ten.ps'... Converting to `./ten.pdf'.

Re: tablature.ly

On 4/29/09 3:12 AM, "Marc Hohl" wrote: > Neil Puttock schrieb: >> 2009/4/27 Carl D. Sorensen : >> >>> Neil, >>> >>> Thanks for your input. I think it's all really good. >>> >>> >>> On 4/26/09 1:49 PM, "Neil Puttock" wrote: >>> >>> 2009/4/25 Marc Hohl : >>> Marc, the

Re: adding to the LSR

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mittwoch, 29. April 2009 12:16:52 Graham Percival wrote: > On Wed, Apr 29, 2009 at 11:37:12AM +0200, Reinhold Kainhofer wrote: > > I think the solution is to simply check that no letter follows after > > \octave, This can be easiest done by a negati

Re: adding to the LSR

On Wed, Apr 29, 2009 at 11:37:12AM +0200, Reinhold Kainhofer wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > > This probably also indicates a need to change the convert-ly rule for > > \octave. If it doesn't work for \octaves, it also wouldn't work for > > \octaveAdjustFunction, or s

Re: tablature.ly

Marc Hohl schrieb: Marc Hohl schrieb: Neil Puttock schrieb: 2009/4/27 Carl D. Sorensen : Neil, Thanks for your input. I think it's all really good. On 4/26/09 1:49 PM, "Neil Puttock" wrote: 2009/4/25 Marc Hohl : Hello tablature users*, Like Carl, I'm not a tablature

Re: adding to the LSR

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Dienstag, 28. April 2009 23:58:49 Carl D. Sorensen wrote: > On 4/28/09 10:24 AM, "Jonathan Kulp" wrote: > > of my own files before. The convert-ly script took the \octaves command > > as if it were an octave check instead of a user-defined macro.

Re: adding to the LSR

On Tue, Apr 28, 2009 at 09:24:36PM -0600, Carl D. Sorensen wrote: > > On 4/28/09 4:42 PM, "Jonathan Kulp" wrote: > > > After running the script on the directory with all the snippets in it, I > > run this command to find snippets that didn't compile: > > Cool! I still think that you ought to p

Re: tablature.ly

Marc Hohl schrieb: Neil Puttock schrieb: 2009/4/27 Carl D. Sorensen : Neil, Thanks for your input. I think it's all really good. On 4/26/09 1:49 PM, "Neil Puttock" wrote: 2009/4/25 Marc Hohl : Hello tablature users*, Like Carl, I'm not a tablature user, so I can onl

Re: tablature.ly

Neil Puttock schrieb: 2009/4/27 Carl D. Sorensen : Neil, Thanks for your input. I think it's all really good. On 4/26/09 1:49 PM, "Neil Puttock" wrote: 2009/4/25 Marc Hohl : Hello tablature users*, Like Carl, I'm not a tablature user, so I can only comment on mat

Re: tablature.ly

Neil Puttock schrieb: 2009/4/27 Marc Hohl : Thank you for your suggestions! As I am no expert in scheme, some things can surely be done more elegant. I corrected my file as you suggested above. Glad to help. :) You're doing fine with Scheme so far. Ok, #:column changed to #:cent

Re: adding to the LSR

Carl D. Sorensen wrote: On 4/28/09 4:42 PM, "Jonathan Kulp" wrote: Carl D. Sorensen wrote: Thanks for the offer, Chip. I've just finished a preliminary run through all of the snippets. I downloaded the tarball of the entire repo and ran them through the convert-ly script, then did