[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication
From: |
Paul Scott |
Subject: |
Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication causes segfault |
Date: |
Mon, 6 Sep 2010 14:57:38 -0700 |
User-agent: |
Mutt/1.5.20 (2009-06-14) |
On Mon, Sep 06, 2010 at 09:50:11PM +0100, Neil Puttock wrote:
> On 6 September 2010 20:03, Paul Scott <address@hidden> wrote:
>
> > Now I get mixed results with \tempo placement. (bug 684) Some start over
> > the
> > time signature and some start over the key signature. One of those placed
> > over the key signature precedes the occurrance of the above workaround.
> >
> > Is this reasonable since 684 has been fixed?
>
> I'm just waiting for a docs build to finish, then I'll be pushing the
> patch which fixes the segfault. It also corrects the alignment so
> you'll only get metronome marks over key signatures if you want them
> there.
Ok. I probably need to read more about \tempo. My main concern was alignment
over multi-measure rests. (Now I'm going to see about aligning any text the
same for over MMRs as it is over notes.)
> Try this tweak to prevent the marks from starting over key signatures:
>
> \override Score.MetronomeMark #'break-align-symbols = #'(time-signature)
Great!! (I probably could have figured that out from the docs.)
I just tried it and it works!
> This will be the new default once the patch is committed.
Great!
Thanks,
Paul
Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication causes segfault, lilypond, 2010/09/06
Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication causes segfault, lilypond, 2010/09/12
Re: Issue 1251 in lilypond: StaffGroup with pauses and tempo indication causes segfault, lilypond, 2010/09/12