I'm getting this error in the console output - no indication is given of
where in the source is causing the error. The PDF output is fine. I did
a google search for the error message but didn't find anything that
seemed relevant. There are tuplets all the way through this score, so
after showin
Dear All,
After reading the messages about "going back in midi time", I realized that
the main problem of my overture's midi output is not totally because of
articulate. Here's the small intro containing just 8 bars, and the problem is
at bar 7. Please run it, and you'll see these warnings. I
On Fri, Jul 09, 2010 at 05:58:54PM +0100, Phil Holmes wrote:
> If you look in the Reference, section 5.1.4,
BTW, the preferred term is "Notation", since that matches the section
name in the new website:
http://lilypond.org/website/notation.html
> If you go back a section to 5.1.3 you'll see an al
What has now happened is that I've added some more bars and the error is
no longer there. When I finish engraving the piece (a transcription of a
Schubert song for solo guitar) I'll see if I can reproduce it with the
truncated score and report it as a bug if I can get the error.
Nick
On 10/07
Dear Phil,
Thanks again for your help. It was a brackets 'n' braces problem all
along! Seeing your copied example helped me see that (why that didn't
work when actually looking at the documentation, I don't know...).
I understood what the code was supposed to do, but it wasn't doing it
— because
Dear Collective Wisdom,
I've almost got it! It was indeed an order of operations issue.
Despite reading the manual, I wasn't clear on this, so I made a
mini-primer:
*
\version "b.l.a.h"
\layout { blah }
\header { blah }
\new Score {
\relative c' {
% << tells the progr
OK, I'm still only learning LilyPond and its syntax, but I think what I say
is accurate and hope it will help.
If you look in the Reference, section 5.1.4, you'll see what the code I
quoted does - it changes the context default settings by putting them within
a \layout block. The settings we'
Dear Phil,
Thanks for your reply.
I used that exact code that you pasted, minus everything after the
comment because I copied and pasted it into my own document.
(aside: If this helps, I'm trying to put these eight parts into one
score: http://reloadsanear.com/composition/putrefaction.html)
Fir
Andrea,
I'm using 2.12.3. When I go to the page/section you've mentioned below, and
then copy and paste the code there into a file and run it, it runs perfectly
and produces the output of as shown on the page. Could you be more precise
in the code you are trying to use that produces the erro
Hi Andrea,
maybe the attached example can serve as a model for your purposes?
ole
bcl&perc.ly
Description: Binary data
Am 09.07.2010 um 16:24 schrieb Andrea La Rose:
> Dear Collective Wisdom,
>
> I am a lilypond noob using version 2.12.3.
>
> I am working on making a score for a pi
Dear Collective Wisdom,
I am a lilypond noob using version 2.12.3.
I am working on making a score for a piece where each part has its own
independent time signatures like this example ""Staves with different
time signatures, unequal bar lengths":
http://lilypond.org/doc/v2.12/Documentation/user/l
To get this reported as a bug and fixed, we'll need an example that shows
the bug. Is your music confidential? If not, how large is it?
--
Phil Holmes
- Original Message -
From: "Nick Payne"
To: "lilypond-user"
Sent: Friday, July 09, 2010 5:41 AM
Subject: programming error: Going
- Original Message -
From: "Xavier Scheuer"
To: "lilypond-user"
Sent: Thursday, July 08, 2010 10:11 PM
Subject: LSR: inconsistent search results
Hi !
I have been using the LSR for dozens of months and I really appreciate
it. Many thanks to the authors of this, and to every contribu
13 matches
Mail list logo
