Hello,
-Original Message-
From: Carl Sorensen
Date: Fri, 4 Mar 2011 17:33:07 -0700
To: Phil Holmes , bug-lilypond
Subject: Re: Spacing problems
>On 3/4/11 11:25 AM, "Phil Holmes" wrote:
>
>> James Lowe reported too late last night that he couldn't space
- Original Message -
From: "Neil Puttock"
To: "Phil Holmes"
Cc:
Sent: Saturday, March 05, 2011 3:47 PM
Subject: Re: Spacing problems
Hmm, I can only get the ossia lyrics below the main stave (probably
due to the nesting of the alignAboveContext settings).
I&
On 5 March 2011 15:01, Phil Holmes wrote:
> Ah. Didn't realise you meant for them to be outside all staff definitions.
> I've now changed this to read:
>
> \relative c''{
> <<
> \context Staff = "MainStaff"
> \new Voice = "MainVoice" {
>
> which is the only way I can see to put the lyrics so t
Original Message -
From: "Neil Puttock"
To: "Phil Holmes"
Cc:
Sent: Saturday, March 05, 2011 2:18 PM
Subject: Re: Spacing problems
On 5 March 2011 12:23, Phil Holmes wrote:
> So I think I've got brackets << >> including the simultaneous
On Sun, Mar 6, 2011 at 1:07 AM, Neil Puttock wrote:
> On 5 March 2011 13:38, Joe Neeman wrote:
>
> > This seems like a bad idea: ossia staves should be spaced like staves,
> not
> > like loose lines, right? If so, I have a patch ready...
>
> Yep, that's a much better idea (I wish I'd thought of
On 5 March 2011 12:23, Phil Holmes wrote:
> I did give the full detail in a previous mail, but a skeleton looks like
> this:
>
> \new Staff = "MainStaff" <<
> \new Voice = "MainVoice" { SomeMusic
> << {
> OtherMusic
> }
> \new Staff = "Ossia" \with {
> \remove "Time_signatu
On 5 March 2011 13:38, Joe Neeman wrote:
> This seems like a bad idea: ossia staves should be spaced like staves, not
> like loose lines, right? If so, I have a patch ready...
Yep, that's a much better idea (I wish I'd thought of it when I added
those staff-affinity settings. :)
Cheers,
Neil
_
On Sat, Mar 5, 2011 at 11:23 PM, Phil Holmes wrote:
> - Original Message - From: "Neil Puttock"
> On 4 March 2011 18:25, Phil Holmes wrote:
>
> > So - to me this is a regression and I'm gonna make a bug report to that
>> > effect tomorrow unless anyone can explain what's going on and h
- Original Message -
From: "Neil Puttock"
To: "Phil Holmes"
Cc:
Sent: Friday, March 04, 2011 8:10 PM
Subject: Re: Spacing problems
On 4 March 2011 18:25, Phil Holmes wrote:
> I reported on .user some problems I had with trying to get Ossia staves
>
On 3/4/11 11:25 AM, "Phil Holmes" wrote:
> James Lowe reported too late last night that he couldn't space scores apart
> from one another.
> (http://www.mail-archive.com/lilypond-user@gnu.org/msg62149.html). I tried
> and failed, and concluded that score-system-spacing appears to have no
> effec
On 4 March 2011 18:25, Phil Holmes wrote:
> I reported on .user some problems I had with trying to get Ossia staves
> properly spaced.
> (http://www.mail-archive.com/lilypond-user@gnu.org/msg62140.html) Didn't get
> a response, except from another user on .bugs who reported a problem with
> alignB
I reported on .user some problems I had with trying to get Ossia staves
properly spaced.
(http://www.mail-archive.com/lilypond-user@gnu.org/msg62140.html) Didn't get
a response, except from another user on .bugs who reported a problem with
alignBelowContext. I've now taken out all of the .13 s
2009/7/21 hernan gonzalez :
> Any news with this issue? I guess my scenario (staff + chords+ tabstaff) is
> not unusual, and the problem degrades badly the lilypond output.
> Some workaround ? Won't it be even considered as a bug to be fixed?
Thanks for the reminder; since no one else seems to ha
33 AM, Valentin
Villenave wrote:
> 2009/7/16 hernan :
>> In certain cases, the combination of tabstaff with chords-mode seems to cause
>> serious spacing problems. Look at this example
>> http://hjg.com.ar/varios/lilypondb1/test2.png
>>
>> (extra spacing above am6 chor
2009/7/16 hernan :
> In certain cases, the combination of tabstaff with chords-mode seems to cause
> serious spacing problems. Look at this example
> http://hjg.com.ar/varios/lilypondb1/test2.png
>
> (extra spacing above am6 chord in third measure, and above the last chord in
In certain cases, the combination of tabstaff with chords-mode seems to cause
serious spacing problems. Look at this example
http://hjg.com.ar/varios/lilypondb1/test2.png
(extra spacing above am6 chord in third measure, and above the last chord in
last measure)
The source code is here:
http
Please always tell what LilyPond version you are using. The spacing
functions have changed significantly in the latest development release,
for example.
/Mats
Quoting Marian <[EMAIL PROTECTED]>:
I want to begin a new page for the second system, now the layout in
the page (
which is "befor
I want to begin a new page for the second system, now the layout in the page (
which is "before" the pageBreak ) looks very strange.
\book
{ \score
{<< \context Voice = "mel"
{ \clef treble
a4 a a a \break
g g
Joe Neeman wrote:
On Sat, 2006-10-14 at 01:46 -0400, Marcus Macauley wrote:
Han-Wen Nienhuys wrote:
> Marcus Macauley schreef:
>
>> So, Joe, whatever it is that you fixed, there still seems to be a
>> problem [with vertical spacing] in 2.9.22.
>> I can try to send an example if necessary.
>
>
On Sat, 2006-10-14 at 01:46 -0400, Marcus Macauley wrote:
> Han-Wen Nienhuys wrote:
>
> > Marcus Macauley schreef:
> >
> >> So, Joe, whatever it is that you fixed, there still seems to be a
> >> problem [with vertical spacing] in 2.9.22.
> >> I can try to send an example if necessary.
> >
> > I
On Thu, 2006-10-12 at 02:37 -0400, Marcus Macauley wrote:
> Joe Neeman <[EMAIL PROTECTED]> wrote (earlier):
> > You can enable the old page breaker by
> > putting #(define page-breaking optimal-page-breaks) in the \paper block.
>
> I tried this command, and it seemed to work for vertical spacing
On Sat, 2006-10-14 at 20:48 +0200, Joe Neeman wrote:
> On Sat, 2006-10-14 at 01:46 -0400, Marcus Macauley wrote:
> > At least judging from one score I'm working on, 2.9.17 was fine, 2.9.22
> > was way too spread out (vertically and horizontally), and 2.9.23-1 is way
> > too squished together (v
his case, but still involving a staff pushed off the page.
>
> And setting #(define page-breaking optimal-page-breaks) in the \paper
> block, to disable the new page-breaking, seems to fix the vertical spacing
> problems, but it still leaves the horizontal spacing somewhat more spre
less
severe in this case, but still involving a staff pushed off the page.
And setting #(define page-breaking optimal-page-breaks) in the \paper
block, to disable the new page-breaking, seems to fix the vertical spacing
problems, but it still leaves the horizontal spacing somewhat more spread
Joe Neeman schreef:
Then we know for what release it was fixed.
Sure, does that include this bug or just future ones?
future ones.
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
LilyPond Software Design
-- Code for Music Notation
http://www.lilypond-design.com
On Thu, 2006-10-12 at 14:49 +0200, Han-Wen Nienhuys wrote:
> Marcus Macauley schreef:
>
> > So, Joe, whatever it is that you fixed, there still seems to be a
> > problem in 2.9.22.
> >
> > I can try to send an example if necessary.
>
> I think this went in for 2.9.23
>
> Joe,
>
> can you regi
Marcus Macauley schreef:
So, Joe, whatever it is that you fixed, there still seems to be a
problem in 2.9.22.
I can try to send an example if necessary.
I think this went in for 2.9.23
Joe,
can you register all issues in the tracker, and add a "fixed2923" tag to
it when you fix it? A sim
Marcus Macauley riseup.net> writes:
> So, Joe, whatever it is that you fixed, there still seems to be a problem
> in 2.9.22.
I think this was fixed *after* 2.9.22, so that makes sense. ;-)
--
Arvid,
waiting for 2.9.23 (and 2.10)
___
bug-lily
I wrote:
When I upgraded from 2.9.17 to 2.9.22, the page layout of one of my
scores got messed up. That's only my opinion, of course, but it changed
pretty drastically from five systems per page, spaced adequately, to
three systems per page, with lots of blank space.
Joe Neeman <[EMAIL PRO
Joe Neeman <[EMAIL PROTECTED]> wrote:
On Sun, 2006-10-08 at 10:27 +, Arvid Grøtting wrote:
Arvid Grøtting gmail.com> writes:
> For some reasons, 2.9.21 has three systems per page on all pages,
> while 2.8.1 has three on the first page and four thereafter, but I
> don't know if that's a sy
On Sun, 2006-10-08 at 10:27 +, Arvid Grøtting wrote:
> Arvid Grøtting gmail.com> writes:
>
> > For some reasons, 2.9.21 has three systems per page on all pages,
> > while 2.8.1 has three on the first page and four thereafter, but I
> > don't know if that's a symptom or the problem.
>
> Loo
ercival" <[EMAIL PROTECTED]>
> Cc: "lily-devel" ;
> Sent: Monday, October 09, 2006 8:02 AM
> Subject: Re: Spacing problems with 2.9.21 (as opposed to 2.8)
>
>
> > On Sun, 2006-10-08 at 09:33 -0700, Graham Percival wrote:
> >> Thanks, this should be
t;Graham Percival" <[EMAIL PROTECTED]>
Cc: "lily-devel" ;
Sent: Monday, October 09, 2006 8:02 AM
Subject: Re: Spacing problems with 2.9.21 (as opposed to 2.8)
On Sun, 2006-10-08 at 09:33 -0700, Graham Percival wrote:
Thanks, this should be helpful. Joe, I'll just leave
On Sun, 2006-10-08 at 09:33 -0700, Graham Percival wrote:
> Thanks, this should be helpful. Joe, I'll just leave this bug with you,
> instead of filing it on the issue tracker. That ok?
Sure. I'll try to look at this soonish but I'm about to start traveling
so I can't promise anything...
>
>
Thanks, this should be helpful. Joe, I'll just leave this bug with you,
instead of filing it on the issue tracker. That ok?
- Graham
Arvid Grøtting wrote:
Arvid Grøtting gmail.com> writes:
For some reasons, 2.9.21 has three systems per page on all pages,
while 2.8.1 has three on the firs
Arvid Grøtting gmail.com> writes:
> For some reasons, 2.9.21 has three systems per page on all pages,
> while 2.8.1 has three on the first page and four thereafter, but I
> don't know if that's a symptom or the problem.
Looks like it's related to the problem. Here's a small (close enough to
m
Hi!
I'm completing a score that I think shows a bit of regression with
newer 2.9 versions as opposed to 2.8. The problem is that the spacing
gets a bit weird, giving 7 pages with 2.9.21 when only 5 is needed
with 2.8.
The .ly file (and two include files) and resulting output can be
viewed at
Paul Scott wrote:
The attached example run on Debian sid with Lily 2.7.3 shows these
horizontal problems:
1. First note in staff touches time signature or key signature.
2. Key cancellation occurs at correct place but new key signature
doesn't appear until beginning of next line.
Sent ag
[EMAIL PROTECTED] writes:
>
> Just thought I'd post this again. I didn't get any response to the
> first posting, and it's really bugging me. I've tried all I can. Please
> help me!
>
> > With the attached fragment, the chord names bump into each other; I'm
> > using lily 2.0.0 (but it happens
Just thought I'd post this again. I didn't get any response to the
first posting, and it's really bugging me. I've tried all I can. Please
help me!
> With the attached fragment, the chord names bump into each other; I'm
> using lily 2.0.0 (but it happens with lily 2.1.0 as well). In prior
> versi
On Fri, 28 Nov 2003, Dave Symonds wrote:
Just thought I'd post this again. I didn't get any response to the
previous posting, and it's really bugging me. I've tried all I can. Please
help me!
> With the attached fragment, the chord names bump into each other; I'm
> using lily 2.0.0 (but it happen
Hi,
With the attached fragment, the chord names bump into each other; I'm
using lily 2.0.0 (but it happens with lily 2.1.0 as well). In prior
versions (think lily 1.4.0), I could get around this by using
ChordName \override #'word-space = #2
in the ChordNamesContext translator. However, t
42 matches
Mail list logo
