On Tue, Dec 28, 2010 at 11:46:16PM -0700, Jay Carr wrote:
> On Dec 28, 2010, at 3:54 PM, Graham Percival music.ca> wrote:
>
> >On Tue, Dec 28, 2010 at 07:01:58PM +0100, James Bailey wrote:
> >>
> >>On Dec 23, 2010, at 8:20 AM, jayc...@gmail.com wrote:
> >>
> >>>I'm trying to use midi2ly on my Mac
Updates:
Labels: fixed_2_13_25
Comment #25 on issue 884 by pnorcks: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
(No comment was entered for this change.)
___
bug-lilypond mailing list
bug-lilypo
Updates:
Status: Fixed
Comment #24 on issue 884 by ColinPKCampbell: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
Created issue 1465 "\pageBreak breaks \page-ref"
___
bug-lilypond mailing list
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1465 by ColinPKCampbell: \pageBreak breaks \page-ref
http://code.google.com/p/lilypond/issues/detail?id=1465
In version 2.12.3 the code below behaves as expected: the \page-ref for
mark A is page 2. Under 2
On Wed, 2010-12-29 at 00:49 +, Neil Puttock wrote:
> On 27 December 2010 17:58, Jean-Charles Malahieude wrote:
>
> > May I guess that it is due to \mark falling before the first note event
> > is generated?
>
> No. It's a consequence of the way label-page-table is generated;
> since 2.13.5
On 27 December 2010 17:58, Jean-Charles Malahieude wrote:
> May I guess that it is due to \mark falling before the first note event
> is generated?
No. It's a consequence of the way label-page-table is generated;
since 2.13.5 the order is consistently reversed, leading to \page-ref
accessing th
On Wed, 2010-12-29 at 00:33 +, lilyp...@googlecode.com wrote:
> Comment #23 on issue 884 by percival.music.ca: pageBreak resets page-count
> property
> http://code.google.com/p/lilypond/issues/detail?id=884
>
> ok, let's move Colin's example into a new issue number, then mark this one
> as
Comment #23 on issue 884 by percival.music.ca: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
ok, let's move Colin's example into a new issue number, then mark this one
as fixed again (and add back the tag for the version number in which it was
Comment #22 on issue 884 by n.puttock: pageBreak resets page-count property
http://code.google.com/p/lilypond/issues/detail?id=884
I've checked this with the versions of Lily that I have, and the
behaviour is incorrect from 13.31 onwards.
The original snippet correctly produces two pages on
On Tue, Dec 28, 2010 at 1:28 PM, Michael Ellis
wrote:
> The Dover Edition of the Beethoven Sonatas, a reproduction of the 1923
> Universal Edition (H. Schenker, ed.) has the attached in opus 27, no 2,
> second movement (Presto Agitato) mm 54,55.
>
> In the left hand of mm 54, the clef changes 4 ti
On Tue, Dec 28, 2010 at 07:01:58PM +0100, James Bailey wrote:
>
> On Dec 23, 2010, at 8:20 AM, jayc...@gmail.com wrote:
>
> > I'm trying to use midi2ly on my MacBook Pro running OSX 10.6.5.
> > It seems that midi2ly was not compiled properly, as it's saying that
> > I have the wrong architectur
Am Dienstag, 28. Dezember 2010, um 15:14:05 schrieb David Kastrup:
> Reinhold Kainhofer writes:
> > I would be great, though, if anyone can find a published example of such
> > a situation (most likely in e.g. cello/bassoon parts/scores, which
> > frequently switch between bass and tenor clef).
>
I don't know about this one. Certainly, the accidental should be (and is)
printed. It's the naturals that aren't printed. Not even when changing octaves:
\new Staff \relative c' {
\time 6/4
\clef treble
cis dis fis
\clef tenor
c d f
\clef bass
cis dis fis
\clef treb
On Dec 23, 2010, at 8:20 AM, jayc...@gmail.com wrote:
> I'm trying to use midi2ly on my MacBook Pro running OSX 10.6.5.
> It seems that midi2ly was not compiled properly, as it's saying that
> I have the wrong architecture. This despite the fact that I can run
> Lilypad just fine (I have the r
On Dec 27, 2010, at 6:49 PM, Chris Snyder wrote:
> We've run into a segfault in all versions of LilyPond after 2.13.32,
> including 2.13.44. I've narrowed it down to occur when a tempo marking is
> placed over a multimeasure rest when the Metronome_mark_engraver has been
> added to the staff c
Status: Accepted
Owner:
Labels: Type-Defect Priority-Critical Regression
New issue 1464 by jameseli...@googlemail.com: Segfault with multimeasure
rests and metronome markings
http://code.google.com/p/lilypond/issues/detail?id=1464
A segfault will occur when a tempo marking is placed over
Hello,
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[bug-lilypond-bounces+james.lowe=datacore@gnu.org] on behalf of Trevor
Daniels [t.dani...@treda.co.uk]
Sent: 28 December 2010 16:37
To: Janek Warchoł
Cc: lilypond-de...@gnu.org; Lilypond Bugrep
Janek Warchoł wrote Tuesday, December 28, 2010 3:28 PM
2010/12/27 Trevor Daniels
I know next to nothing about ancient notation, but whoever wrote
gregorian.ly clearly intended this behaviour as the file contains
the override
\override SpacingSpanner #'packed-spacing = ##t
on line 258, whi
2010/12/27 Trevor Daniels
>
> If you want to use normal spacing simply revert this setting:
> \revert Score.SpacingSpanner #'packed-spacing
Thanks for this!
> I know next to nothing about ancient notation, but whoever wrote
> gregorian.ly clearly intended this behaviour as the file contains
> th
"Phil Holmes" writes:
> "David Kastrup" wrote in message
> news:87aajqowbn@lola.goethe.zz...
>> "Phil Holmes" writes:
>>
>>>
>>> Apologies. As you're probably aware, I'm a Windows man, and some
>>> postings don't quote properly using my mailreader.
>>
>> I am sure that there are sensible co
"David Kastrup" wrote in message
news:87aajqowbn@lola.goethe.zz...
"Phil Holmes" writes:
"David Kastrup" wrote in message
news:87ei92oxo3@lola.goethe.zz...
"Phil Holmes" writes:
\relative c' {
\clef bass cis2 c
\clef tenor cis2 \clef bass c % natural is not printed!!
\clef ba
Reinhold Kainhofer writes:
> Am Dienstag, 28. Dezember 2010, um 14:23:14 schrieb Phil Holmes:
>> "David Kastrup" wrote in message
>> > I don't think it is correct. If you set the above with \key g\major,
>> > you will notice that the key signature is _not_ repeated with a clef
>> > change. So
Am Dienstag, 28. Dezember 2010, um 14:23:14 schrieb Phil Holmes:
> "David Kastrup" wrote in message
> > I don't think it is correct. If you set the above with \key g\major,
> > you will notice that the key signature is _not_ repeated with a clef
> > change. So there is no visual or logical reaso
"Phil Holmes" writes:
> "David Kastrup" wrote in message
> news:87ei92oxo3@lola.goethe.zz...
>> "Phil Holmes" writes:
>>
>>> \relative c' {
>>> \clef bass cis2 c
>>> \clef tenor cis2 \clef bass c % natural is not printed!!
>>> \clef bass cis2 \clef tenor c
>>> }
>>
>>
>> Could you _plea
"David Kastrup" wrote in message
news:87ei92oxo3@lola.goethe.zz...
"Phil Holmes" writes:
\relative c' {
\clef bass cis2 c
\clef tenor cis2 \clef bass c % natural is not printed!!
\clef bass cis2 \clef tenor c
}
Could you _please_ _never_ write an answer or comment in the _signature
"Phil Holmes" writes:
> \relative c' {
> \clef bass cis2 c
> \clef tenor cis2 \clef bass c % natural is not printed!!
> \clef bass cis2 \clef tenor c
> }
Could you _please_ _never_ write an answer or comment in the _signature_
of the original posting? Sensible mailreaders don't quote the s
Hello,
- Original Message -
From: "Xavier Scheuer"
To: "bug-lilypond" ; "lilypond-user"
Cc: "Philhar"
Sent: Tuesday, December 28, 2010 10:53 AM
Subject: Accidental and clef change issue
Hi!
This has been reported on the French user mailing list.
In the following code the c-natur
Hi!
This has been reported on the French user mailing list.
In the following code the c-natural is not printed if there is a clef
change in the middle of the measure.
\relative c' {
\clef bass cis2 c
\clef tenor cis2 \clef bass c % natural is not printed!!
\clef bass cis2 \clef tenor c
}
28 matches
Mail list logo
