Re: what do you use ragged-bottom for?

On Sun, 17 Nov 2013 04:42:14 -0800, Jean-Charles Malahieude wrote: Le 17/11/2013 06:52, Werner LEMBERG disait : [...] – and lilypond should also emit the corresponding page number in the warning message. Finding the ideal number of pages... Fitting music on 61 or 62 pages... Drawing syste

Re: what do you use ragged-bottom for?

On Sat, 16 Nov 2013 09:38:20 -0800, Mark Stephen Mrotek wrote: My use of the ragged bottom is very particular. I use Lilypond to set piano scores for viewing on a tablet (easy page turning!). In a set of variations, some (if not all) of the variations might not be long enough to fill the page,

what do you use ragged-bottom for?

I'm fixing a bug involving the ragged-bottom setting (issue 3281). By default, ragged-last-bottom=##t so the last page can have blank space at the bottom. Currently, "ragged-bottom" is implemented to *always* under-fill the page, *never* compressing to fit one more system. As a default, that

Re: review of a Mutopia file (why TabStaff gives error here?)

Federico Bruni gmail.com> writes: I've updated to 2.16 the following piece of Mutopia: http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636 Can anyone review it? I made one pass through, and made potential-corrections as I went. (attached) Hopefully you can use a 'diff' program to see

Re: review of a Mutopia file (why TabStaff gives error here?)

Federico Bruni gmail.com> writes: I've updated to 2.16 the following piece of Mutopia: http://www.mutopiaproject.org/cgibin/piece-info.cgi?id=636 Can anyone review it? I made one pass through, and made potential-corrections as I went. (attached) Hopefully you can use a 'diff' program to see

Three new microtonal snippets in the LSR

These snippets are for people not want to program. They are not yet checked-in and search-able, but you can see them through the links in this message. Arrow notation and transposition for quarter tones shows a simple way to keep natural-up-arrow distin

Re: extra staves - help required

On Fri, 12 Nov 2010 19:10:06 -0800, Bill Mooney wrote: \version "2.13.36" [ . . . ] \override StaffGroup.SystemStartBracket #'collapse-height = #4 %** \override Score.SystemStartBar #'collapse-height = #4 %** \new Staff \with { \remo

Re: extra staves - help required

On Tue, 09 Nov 2010 12:58:31 -0800, wrote: The .ly file was made using aspects of the 'Adding an extra staff (2)' snippet in the Snippet Repository, as well as other bits from the learning and notation manuals. My 'client' asked for the reduced size bracket at the beginning of the single staff.

Re: Padding behaviour

On Wed, 10 Nov 2010 14:03:53 -0800, James Lowe wrote: -Original Message- There is a similar example in the notation reference manual (section 4.6.2) but... --- I think this is the example you are referring to That was it. Your new version works great and makes a lot more sense. -K

Re: alpha test, spacing ajusments

On Wed, 03 Nov 2010 12:35:23 -0700, Jan Warchoł wrote: Maybe our scores differ so much that there are no settings good for all of them. Time to finish this up. I think the attached very short set of overrides are a good compromise, which we can all use until the final stages of tweaking. I

Re: rests in polyphonic music - 'stems down, rests up'

On Wed, 03 Nov 2010 09:01:03 -0700, wrote: "K" == Keith E OHara writes: K> It is less clear if the use of Stem 'direction to place rests, in K> the notes-plus-rests case, was intentional. Shouldn't the rests by default be placed where the voice goes in t

Re: alpha test, spacing ajusments

On Wed, 03 Nov 2010 12:35:23 -0700, Jan Warchoł wrote: 2010/11/3 Keith E OHara I don't fully understand... Are you refering to the lyricsStaff.png picture? Yes. You understood correctly. (I confused th order of the pictures) [ . . . ] In this case they should be centered (because

Re: alpha test, spacing ajusments

On Tue, 02 Nov 2010 09:19:32 -0700, Jan Warchoł wrote: As for me the attached settings work quite well. In particular your Lyric spacing settings didn't produce good results when lyrics were centered between two staves, so I changed them. Good. I was expecting that you would increase the '

Re: rests in polyphonic music - 'stems down, rests up'

On Tue, 02 Nov 2010 09:19:53 -0700, wrote: Yes, thanks. The problem is getting at the automatic behaviour which is already available. I beleive its a bug, that \stemDown obstructs explicit coming later. \override Rest #'direction = #UP Anders, LilyPond does obey a simultaneous \stemDow

Re: rests in polyphonic music - 'stems down, rests up'

On Mon, 01 Nov 2010 12:25:12 -0700, wrote: Q: How Can i separate handling of rests from stem-directions in polyphonic voice-handling? Hello Anders, I would also have expected Rest 'direction to do what you asked. It does change the placement of rests in columns with only rests, but wh

Re: extra spacing between staves and verses

Hi, Bill. On Sat, 30 Oct 2010 21:30:17 -0700, Bill wrote: And it will require a fairly complex explanation in the docs to make it really clear, particularly to those users such as myself who need a good bit of hand-holding! I wouldn't say that. If not for the unfortunate timing, "Oops, shoul

Re: Controlling between-system-padding for specific systems

On Fri, 29 Oct 2010 06:33:30 -0700, wrote: I know it is possible to control the between-system-padding of an entire score, but I want to know if it is possible to do that for specific systems instead? For practical purposes, Richie, I would so 'no'. There is a snippet

Re: extra spacing between staves and verses

On Sat, 30 Oct 2010 13:04:58 -0700, Fr Gilmary wrote: As it is, the suggestion the other day from Patrick Karl works,i.e., to use:\markup { " " } in between the scores to spread them out more or less ... only it seems like a temporary type fix, no? Father Michael, I would consider Patrick's

Re: alpha test, spacing ajusments

On Thu, 28 Oct 2010 23:25:31 -0700, Nick Payne wrote: ... However, I don't like the resulting look of the output, as the space between the bottom stave on each page and the foot of the page varies too much for my taste. The simplest way to ask LilyPond to stretch big orchestral systems a lit

Re: alpha test, spacing ajusments

On Thu, 28 Oct 2010 09:01:26 -0700, Nick wrote: Actually, the vertical layout problem I reported a few weeks ago (http://code.google.com/p/lilypond/issues/detail?id=1252) still exists with 2.13.37. The information in the bug tracker indicates that, when LilyPond plans how many systems to put

Re: alpha test, spacing ajusments

On Wed, 27 Oct 2010 21:48:06 -0700, Keith E OHara wrote: 1) The systems (that is, the sets of staffs that are being played at the same time)are stretched too much compared to the space between the systems. If there is only one system on the page, it is stretched to fill the page

alpha test, spacing ajusments

Friends of the forthcoming Lilypond 2.14, The third alpha version, 2.13.37, has resolved the obvious problems in the spacing mechanism. The default spacing, though, could use some adjustment. Now is our opportunity to recommend good defaults. I have been having fun testing the alpha version

Re: Parallel dynamics, markup, sponsor, etc.

On Tue, 26 Oct 2010 14:20:27 -0700, Valentin Villenave wrote: You're right. I think I'm gonna suggest a patch for our 2.14 Documentation. (attached) No, Wait! Trevor and I already worked out a revision . . . Ah. Very funny. Where were you when I was defending the need for doc changes?

Re: Parallel dynamics, markup, sponsor, etc.

On Tue, 26 Oct 2010 13:14:42 -0700, Werner LEMBERG wrote: it looks like `dynamic-gap.png' (attached), and the huge gap between the crescendo and decrescendo hairpin is not what I expect. Additionally, I get a nasty warning programming error: Improbable offset for stencil: -nan staff space

Re: Parallel dynamics, markup, sponsor, etc.

On Tue, 26 Oct 2010 02:13:49 -0700, Valentin Villenave wrote: the goal would be to improve LilyPond's *default* behaviour, not to require users to change the syntax they use. Now, if power-users happen to want to modify the new behavior (and even possibly disable it), they should *also* have be

Re: Parallel dynamics, markup, sponsor, etc.

On Fri, 22 Oct 2010 00:17:05 -0700, Valentin Villenave wrote: I could imagine a way of making LilyPond aware of nearly-adjacent dynamics. Something like a 'neighborhood property, that would take a ly:moment as argument... If anyone else wants to help write a feature request, I'll add it to the t

Re: Colliding whole notes in a default 4 voices (2x2) piece. Files attached

On Mon, 25 Oct 2010 12:04:01 -0700, Nils Gey wrote: The notes are misaligned verticaly, lilypond does know this and informs me of this while making the pdf. [...]Why does this happen? The .ly file is very long and appears to be automatically-generated code, so let's ignore that. The image

Re: Levelling sustain-pedal indications

On Mon, 25 Oct 2010 00:51:11 -0700, wrote: In a piano page chock full of bracket-style pedalling for chords at widely different pitch levels, I've managed to align the horizontal pedalling lines vertically, via a zillion little paragraphs like Pete, You can put the pedal indications in t

Re: MIDI playback lacks polyphony

On Thu, 21 Oct 2010 08:42:09 -0700, Jan wrote: 2010/10/21 Javier Ruiz-Alma Hello Dear Gurus, Lilypond is correctly engraving this score in .pdf, which has some sections of single-staff polyphony. However, the MIDI playback on my PC plays one voice only. I'm ignorant to where the problem is

how-to break lines before grace notes

I hesitate to admit this, but when I noticed that explicit line-breaks before grace notes were failing with "should you be using bar checks?", I searched the mailing list archives more thoroughly than I searched the manual. The archives had nothing helpful, so I made up a solution . . . which

Re: Beam slope

On Wed, 20 Oct 2010 18:08:51 -0700, Ralph wrote: I'm currently using version 2.12.3. I've noticed that sometimes Lilypond uses sloped beams, and sometimes uses level beams, in places that appear to be almost identical. Specifically, see the snippet in the Learning Manual, Section 1.1 Background

Re: negative distance between systems

On Tue, 19 Oct 2010 02:01:22 -0700, zbigb wrote: I tried modifying all of the vertical spacing snippets I could find, but didn't get any closer, The link in your message was to the manual for the development version 2.13, and the vertical spacing system is changing in that version. Instead,

Re: Parallel dynamics, markup, sponsor, etc.

LilyPond where one could add a tag to certain dynamics to make them parallel: e.g. a'\p?var1 c' d' b'\mf?var1 f'\markup{asdf}?var1 d''2\?var2 b'\! James wrote: If I understand correctly, is this similar to the (rather hackish, imo) lsr snippet? http://lsr.dsi.unimi.it/LSR/Item?id=450 I do

Re: orchestral template, please comment

On Tue, 19 Oct 2010 09:00:55 -0700, wrote: While all these suggestions are perfectly reasonable, let's not forget after all this is a *template*. Yep. If any clear need comes to light from this discussion of the new spacing, let's make it an enhancement request to adjust the defaults. My

Re: orchestral template, please comment

On Mon, 18 Oct 2010 10:18:52 +0100 "Trevor Daniels" wrote: Shouldn't the music for the Horn in F be printed in D major? I will add a comment "% Key signature is often omitted for horns". As a user, I can easily insert it if I want it. The previous version omitted this key sig (showing off a

Re: Re:orchestral template, please comment

On Fri, 01 Oct 2010 13:15:21 -0700, Keith E OHara wrote: On Fri, 01 Oct 2010 03:20:48 -0700, wrote: All, How about the other proposed changes? Do they help to give new users a starting point for the types of scores you write? Do they steer new users away from issues and traps? 2) Change

Re: anybody understand the instrumentCueName docs?

On Tue, 05 Oct 2010 02:05:00 -0700, Trevor Daniels wrote: Moving the \set instrumentCueName into the Voice context, as you suggest, will change the time when the CueVoice context is created and this may be why it then works. But that is not the root cause of the problem, so I would not want

Re: anybody understand the instrumentCueName docs?

On Tue, 05 Oct 2010 02:05:00 -0700, Trevor Daniels wrote: Keith E OHara wrote Tuesday, October 05, 2010 7:18 AM \new CueVoice \with { instrumentCueName = "ob." } \new Voice { [ . . . ] this example does not create a new Voice _within_ the CueVoice - it creates it in par

anybody understand the instrumentCueName docs?

Hello, I cannot find a way to use the documentation examples for cueDuring with instrumentCueName in a real score. I'm thinking of writing up and submitting replacement examples, based on a snippet from the LSR. First I'd like to see if I just missed the point of the existing examples. 1)

Re:orchestral template, please comment

On Fri, 01 Oct 2010 03:20:48 -0700, wrote: 1) Remove the outermost \GrandStaff{} Someone had already made this change in an unapproved snippet. I've nowapproved it Thank you, Phil. Someone was me; I didn't want to let that one problem be forgotten if I got distracted. All, How about

Re: Beaming to rests over system breaks

Mike, My plan A was to specify the beam positions. However, the beam insists on staying horizontal regardless of the position override (probably for the same reason that it didn't work to simply giving the rest a pitch). Plan B would be to use hidden notes. If we put them a bit earlier in

Re: orchestral template, please comment

On Tue, 28 Sep 2010 18:54:23 -0700, Mark Polesky wrote: Have you looked at Reinhold's OrchestralLily package? The documentation, yes, but I have not used the package. I was a bit curious to compare the plain .ly score that Reinhold's package would create to the template in A.5.1. However, h

orchestral template, please comment

Dear orchestral writers, I don't use LilyPond for orchestral scores very often, which means that I need to refer to the template in Appendix 5.1 of the Learning Manual. There is one bug with the template, and five other changes that I suggest to help it meet the goals set in its introductio

alpha test autobeaming

In "First impressions of alpha test" I wrote: The auto-beaming seems to beam a little less often than the old system. My old scores had two situations with missing beams, neither one is a simple regression: 1) swung triplets in 2/8 are not beamed. Both 2.12 and 2.13 are missing beams, but

Re: First impressions of alpha test

On Fri, 24 Sep 2010 10:41:24 -0700, Joe Neeman wrote: On Thu, Sep 23, 2010 at 11:41 PM, Keith E OHara wrote: The horizontal spacing now quite aggressively tucks notes under/over the accidentals of the following notes. Do you consider this desirable? There are a couple bug reports about

Re: visual problem on two triplets in 4/4 time

My mother found a problem when I write continuous triplets. For example, \time 4/4 c'4 c' \times 2/3 { c'8 d' e' } \times 2/3 { f' g' a' } The two triplets are grouped like one sextupplet, but with two 3's. What's the problem? Is it a wrong practice in notation convention? Is it controlled by

First impressions of alpha test

What are everyone's first impressions of 2.13.34, the alpha test? I remembered to run convert-ly (which worked for me, but I don't have MacOS 10.4, where James W ran into trouble) but it made very few changes to scores written for 2.12. The change that jumped out at me was the spacing, both of