I get segmentation faults with 2.17.14 on a medium to large set of files
which compile fine with 2.17.13. I have gotten these errors with some other
recent 2.17.xx versions. I don't believe I will get errors with a minimal
example.
What evidence can I provide that might help find the
Paul Scott wrote Wednesday, March 20, 2013 7:56 AM
I get segmentation faults with 2.17.14 on a medium to large set of files
which compile fine with 2.17.13. I have gotten these errors with some other
recent 2.17.xx versions. I don't believe I will get errors with a minimal
example.
Trevor Daniels t.dani...@treda.co.uk writes:
Paul Scott wrote Wednesday, March 20, 2013 7:56 AM
I get segmentation faults with 2.17.14 on a medium to large set of files
which compile fine with 2.17.13. I have gotten these errors with
some other
recent 2.17.xx versions. I don't believe I
Paul Scott waterho...@ultrasw.com writes:
I get segmentation faults with 2.17.14 on a medium to large set of files
which compile fine with 2.17.13. I have gotten these errors with some
other
recent 2.17.xx versions. I don't believe I will get errors with a
minimal example.
What evidence
On Wed, Mar 20, 2013 at 08:37:38AM -, Trevor Daniels wrote:
Paul Scott wrote Wednesday, March 20, 2013 7:56 AM
I get segmentation faults with 2.17.14 on a medium to large set of files
which compile fine with 2.17.13. I have gotten these errors with some
other
recent 2.17.xx
Paul Scott waterho...@ultrasw.com writes:
I appreciate that possibility. I have said the same thing to a number
of programming classes I have taught including the assembly language
class I was teaching tonight.
Sounds like you should be able to run lilypond in a debugger then and
get a
Hi,
Musicxml2ly is a nice tool, even if the output is quite often not perfect
and needs manual editing to - often easily - fix errors. (I have plans to
test a large collection of xml scores, and make a list of all strange
and/or bad results I'm encountering. But that's not what this message
Ok. False alarm but hopefully useful info:
The error was triggered by two instances of \times which should have been
\time . Now my code compiles with either 2.17.13 or 2.17.14.
If it helps I am using lilypond-2.17.14-1.linux-64
Maybe this difference between 2.17.14 and 2.17.13 could be
On Wed, Mar 20, 2013 at 10:27:27AM +0100, David Kastrup wrote:
Paul Scott waterho...@ultrasw.com writes:
I appreciate that possibility. I have said the same thing to a number
of programming classes I have taught including the assembly language
class I was teaching tonight.
Sounds like
Hi Evan,
FWIW the multimeasure rest syntax has been a bit of an annoyance with what
I've been working on recently (Mars).
First of all, could you please email me the note code for Mars when you're
done? I'm working on a wicked-cool Lilypond demo, and Mars was exactly the
piece I was
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Hi Evan,
FWIW the multimeasure rest syntax has been a bit of an annoyance
with what I've been working on recently (Mars).
First of all, could you please email me the note code for Mars when
you're done? I'm working on a wicked-cool
I'm unable to post the fingering chart from my professor's book because it's
owned by the publisher and not him... There goes that idea. My only other
suggestion that I have found for the current fingering chart is that on the
right hand on the back, where there are only four keys, the round key
Paul Scott waterho...@ultrasw.com writes:
Ok. False alarm but hopefully useful info:
The error was triggered by two instances of \times which should have
been \time . Now my code compiles with either 2.17.13 or 2.17.14.
That's no excuse for segfaulting, however.
--
David Kastrup
Hi David,
Whatever you mean by improve.
http://dictionary.reference.com/browse/improve
What is supposed to be the result of
{ \time 3/4 { R15 \time 2/4 R3 } \\ { R3 \time 4/4 R10 } }
One context consisting of a sequence of multi-measure rests totalling 51
quarter notes, simultaneously
I'm trying to create a function to display harmonics as shown in the
attached images.
harmonic1.png is in the alto clef with the sounded pitches written in the
treble clef
[image: Inline images 3]
harmonic4.png is an acciaccatura all in the alto clef
[image: Inline images 4]
This is where I
On 20 Mar 2013, at 14:32 , ryanmichaelmcclure wrote:
I'm unable to post the fingering chart from my professor's book
because it's
owned by the publisher and not him... There goes that idea.
No problem, I don't want you to violate any rights. If however you
find a suitable usable version on
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Hi David,
Whatever you mean by improve.
http://dictionary.reference.com/browse/improve
What is supposed to be the result of
{ \time 3/4 { R15 \time 2/4 R3 } \\ { R3 \time 4/4 R10 } }
One context consisting of a sequence of
I apologize for weighing in on the R shorthand thread by sending a new
message. I read the digest and normally reply to messages by gmane.
However, for some unknown reason, R shorthand seems to be missing
entirely from gmane. It exists in the archives on lists.gnu.org.
My opinion (as a
Hello,
While the basic output of barlines in grouped staves has improved in
2.17.14, there is still a problem if there is a dynamics staff included.
The following code produces the expected output in 2.16.1 but is broken in
2.17.14:
\score {
\new PianoStaff
\new Staff { c'1 }
\new
On 20 March 2013 16:04, James Worlton jworl...@gmail.com wrote:
Hello,
While the basic output of barlines in grouped staves has improved in
2.17.14, there is still a problem if there is a dynamics staff included. The
following code produces the expected output in 2.16.1 but is broken in
- Old: R2 == a full measure rest in 2/4 time
- New: R2 == *two* full measure rests in any time signature
Actually, I like this. This would also help in situations like
tacet al rehearsal number 54
|--|
That breaks backward compatibility.
On Wed, Mar 20, 2013 at 11:17 PM, Werner LEMBERG w...@gnu.org wrote:
- Old: R2 == a full measure rest in 2/4 time
- New: R2 == *two* full measure rests in any time signature
Actually, I like this. This would also help in situations like
tacet al rehearsal number 54
On Wed, Mar 20, 2013 at 10:16 AM, Xavier Scheuer x.sche...@gmail.comwrote:
On 20 March 2013 16:04, James Worlton jworl...@gmail.com wrote:
Hello,
While the basic output of barlines in grouped staves has improved in
2.17.14, there is still a problem if there is a dynamics staff included.
Am 20.03.2013 16:25, schrieb James Harkins:
On Wed, Mar 20, 2013 at 11:17 PM, Werner LEMBERG w...@gnu.org wrote:
- Old: R2 == a full measure rest in 2/4 time
- New: R2 == *two* full measure rests in any time signature
Actually, I like this. This would also help in situations like
Hi James,
All good points!
R2 (a full measure rest in 2/4 time)
R2*2 (two full measure rests in 2/4 time)
R*2 (two full measure rests in any meter)
Love it.
Cheers,
Kieren.
___
lilypond-user mailing list
lilypond-user@gnu.org
On 14 March 2013 11:36, Torsten Hämmerle torsten.haemme...@web.de wrote:
Hello all,
I've just noticed the my last mail didn't get through to the list for some
reason. Well, here it is again in a second attempt:
In the first place: I've attached a zip file containing the current (albeit
On Wed, Mar 20, 2013 at 11:48 AM, Kieren MacMillan
kieren_macmil...@sympatico.ca wrote:
Hi James,
All good points!
R2 (a full measure rest in 2/4 time)
R2*2 (two full measure rests in 2/4 time)
R*2 (two full measure rests in any meter)
Love it.
Cheers,
Kieren.
Nick Baskin amphio...@gmail.com writes:
I'm not sure this would work, actually. If I understand correctly, R
currently behaves like any other LilyPond music event when it comes to
duration, i.e. unless otherwise specified, it takes the value of the
preceding note/rest. So if you had something
Hi Nick,
I'm not sure this would work, actually. If I understand correctly, R
currently behaves like any other LilyPond music event when it comes to
duration, i.e. unless otherwise specified, it takes the value of the
preceding note/rest. So if you had something like
\time 2/4
R2 |
R
Hi David,
I gave the answer previously, including the rationale. Since it was
tactfully being ignored, it seemed to require more emphasis. Otherwise
I would likely have been blamed for ignoring users' wishes in spite of
them reaching perfect agreement.
So to be perfectly clear: You can see
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Hi David,
I gave the answer previously, including the rationale. Since it was
tactfully being ignored, it seemed to require more emphasis.
Otherwise I would likely have been blamed for ignoring users' wishes
in spite of them reaching
On 20 Mar 2013, at 17:03 , Nick Baskin wrote:
On Wed, Mar 20, 2013 at 11:48 AM, Kieren MacMillan kieren_macmil...@sympatico.ca
wrote:
Hi James,
All good points!
R2 (a full measure rest in 2/4 time)
R2*2 (two full measure rests in 2/4 time)
R*2 (two full measure rests in any meter)
+1
On Mar 19, 2013, at 9:45 PM, lilypond-user-requ...@gnu.org wrote:
Message: 5
Date: Tue, 19 Mar 2013 15:17:42 -0700 (PDT)
From: rem-d andrewree...@gmail.com
To: lilypond-user@gnu.org
Subject: Column of music and a column of graphics... or creating
invisible measures...
On Wed, 2013-03-20 at 22:54 +0800, James Harkins wrote:
I apologize for weighing in on the R shorthand thread by sending a new
message. I read the digest and normally reply to messages by gmane.
However, for some unknown reason, R shorthand seems to be missing
entirely from gmane. It exists in
Hi David,
See page 3, at the bottom, for two, three, and
four measure rests. (I'm obliged to cite and give
credit for the scans.} How can these be implemented
without R2, R3, and R4?
Assuming that staff is in 4/4 time (there is no time signature currently), then
R1*2, R1*3, and R1*4 should
Decimo tertio Kalendas Apriles MMXIII scripsit Thomas Morley :
in the code below you'll see increasing page-numbers throughout the
book as usual.
Ooh, now that I have had the time to read your code, I see what you
did, and I like it. The \on-the-fly side-effect is devious (and
un-Scheme-like,
Am 20.03.2013 19:11, schrieb David Raleigh Arnold:
A way of indicating the number of
measures rested by a number in the score
should of course remain, but R2, R3, and
R4 should be implemented as shown on page 3.
That is perfectly possible right now (and for a very long time):
R1*2 R1*3 R1*4
Am 20.03.2013 19:19, schrieb Jérôme Plût:
Decimo tertio Kalendas Apriles MMXIII scripsit Thomas Morley :
in the code below you'll see increasing page-numbers throughout the
book as usual.
Ooh, now that I have had the time to read your code, I see what you
did, and I like it. The \on-the-fly
Kieren MacMillan kieren_macmil...@sympatico.ca writes:
Hi David,
See page 3, at the bottom, for two, three, and
four measure rests. (I'm obliged to cite and give
credit for the scans.} How can these be implemented
without R2, R3, and R4?
Assuming that staff is in 4/4 time (there is no
[Snip possibly final comments.]
I've read all the emails on this, and personally agree that R*5 for 5 FMRs
of whatever time sig would be a step forward. Whether this is easy or
difficult to implement is irrelevant to the way we handle enhancement
requests.
Kieren - suggest you send an
Phil Holmes m...@philholmes.net writes:
[Snip possibly final comments.]
I've read all the emails on this, and personally agree that R*5 for 5
FMRs of whatever time sig would be a step forward. Whether this is
easy or difficult to implement is irrelevant to the way we handle
enhancement
2013/3/20 Marc Hohl m...@hohlart.de:
Am 20.03.2013 19:19, schrieb Jérôme Plût:
Decimo tertio Kalendas Apriles MMXIII scripsit Thomas Morley :
in the code below you'll see increasing page-numbers throughout the
book as usual.
Ooh, now that I have had the time to read your code, I see what
I recently upgraded to OSX Mountain Lion and suddenly encountered a technical
problem with lilypond-book. All of the invisible bar lines ( \bar ) in my
.lytex file are suddenly processing as full breaks. Has anyone heard of this
bug or of a way to correct it? Many thanks for any insight you can
43 matches
Mail list logo
