On 27/07/18 13:30, Torsten Hämmerle wrote:
Wols Lists wrote
I'm more used to seeing what you describe in key signatures, […]
Yes, that's pretty much standard for key signature changes and LilyPond uses
cancellation naturals by default (this can be switched off).
Well, lilypond is about the
On 01/09/17 23:19, David Kastrup wrote:
Anthony Youngman <antli...@youngman.org.uk> writes:
On 01/09/17 22:14, David Kastrup wrote:
Change the memory for known good memory, and the kernel
compiled fine. No idea what Gcc does that memory test programs fail to
account for.
Have yo
On 01/09/17 22:14, David Kastrup wrote:
Change the memory for known good memory, and the kernel
compiled fine. No idea what Gcc does that memory test programs fail to
account for.
Have you come across the memory smashing exploit? I can't remember much
about it, but if you can hammer memory
On 01/09/17 21:11, Anthony Youngman wrote:
The big problem I can see is if sometimes it occurs at the start of a
line, in which case the rehearsal mark will naturally move left out of
the way, and letting lily move stuff around may move it to the middle of
the line where I get a collision
On 01/09/17 21:36, David Kastrup wrote:
I find the same thing with databases. So many people have their minds
stuck in the 2-D relational world, and just cannot grasp the concept
of a multi-dimensional database like Pick. Given that Pick is very
much list-based (unlike SQL which is set-based),
On 01/09/17 15:17, Kieren MacMillan wrote:
Hi Wol,
While it may sound weird. the reality is you probably didn't find it too hard
to learn Scheme, because you're a composer not a programmer.
Actually, I am a programmer: started with BASIC (and a little assembler
language) in the early
On 19/08/17 15:11, Kieren MacMillan wrote:
Hi Wol,
My usual moan about colliding markups :-)
Given how usual your moans are… ;)
Mind you, don't they say moaning customers are the best sort? They
*want* the product to succeed.
Can I ask why you don't just write a custom function to
My usual moan about colliding markups :-)
Anyways, I've almost got this bit how I want it ... the following code
has a rehearsal mark, tempo mark, and melody name all in "the same place".
s2.*3 s1*8 \bar "||" \mark \default % 111
\tempo "Languidly"
\once \override
On 26/06/17 22:56, Peter Gentry wrote:
dak@lola:/usr/local/tmp/lilypond$ lilypond scheme-sandbox GNU LilyPond 2.19.59
Processing `/usr/local/share/lilypond/2.19.59/ly/scheme-sandbox.ly'
Parsing...
guile> (apply - (map ly:pitch-tones (list #{ eis #} #{ fes #})))
1/2
guile>
--
David Kastrup
On 15/04/17 15:55, Malte Meyn wrote:
May I ask how much sheet music you have seen so far? All (!) classical
sheet music repeats key signature at every line. And many editions of
pop/jazz/… do that also.
And most of the music I see from the turn of last century does NOT.
However, imho, it
On 26/02/17 00:38, Simon Albrecht wrote:
Am 26.02.2017 um 00:47 schrieb Wols Lists:
I've stuck that definition
in its own .ily file, and I just %include that file at the start of my
\paper definition.
I think it would be slightly cleaner to write an entire \paper{} block
in the .ily file
On 26/02/17 13:55, Anthony Youngman wrote:
On 26/02/17 13:38, msk...@ansuz.sooke.bc.ca wrote:
On Sun, 26 Feb 2017, Anthony Youngman wrote:
EXCEPT.
This is *exactly* the scenario in which you will want my chord
transposition
code, and that doesn't make sense in a lyrics scenario
On 26/02/17 13:38, msk...@ansuz.sooke.bc.ca wrote:
On Sun, 26 Feb 2017, Anthony Youngman wrote:
EXCEPT.
This is *exactly* the scenario in which you will want my chord transposition
code, and that doesn't make sense in a lyrics scenario.
Then they can use the existing code.
In which case
On 26/02/17 11:32, Thomas Morley wrote:
2017-02-26 12:12 GMT+01:00 Anthony Youngman <antli...@youngman.org.uk>:
On 26/02/17 10:52, Thomas Morley wrote:
If the chordNameFunction (ignatzek-chord-names) does not do what we
want, we should improve it, but not drop a plethora o
On 26/02/17 12:24, msk...@ansuz.sooke.bc.ca wrote:
On Sun, 26 Feb 2017, Thomas Morley wrote:
If the chordNameFunction (ignatzek-chord-names) does not do what we
want, we should improve it, but not drop a plethora of
lily-functionality.
I'm not proposing to "drop a plethora of
On 26/02/17 10:52, Thomas Morley wrote:
2017-02-26 2:16 GMT+01:00 :
On Sun, 26 Feb 2017, David Kastrup wrote:
To me it would seem that the default mode of operation should be for
them to have matched rules where feasible, in order to have least
element of surprise.
The problem is the black lilyleaf looks like pacman. I notice that the
more the split in the leaf is rotated to point down, the less it looks
like a mouth (so the less it looks like pacman). The alternative - two
leaves - feels unnatural.
Cheers,
Wol
On 05/08/16 10:05, Malte Meyn wrote:
I like the first and last ones. The first is closer to the web graphic,
but I think I prefer the last one.
I still can't get pacman out of my mind ... you don't get that effect
with the colour graphic because the colours are wrong, but as soon as it
goes b ...
Cheers,
Wol
On 05/08/16
On 07/07/16 19:02, David Wright wrote:
BTW one of the odd "assumptions" made in LP is in that variable called
poet. What about compositions whose lyrics are prose?
Of which I guess there are very few :-) "Jerusalem" is a pretty classic
example - about the only one I can think of.
Anything
On 07/07/16 08:38, Christopher R. Maden wrote:
On 07/07/2016 02:23 AM, David Kastrup wrote:
Federico Bruni writes:
Who should be in your opinion the author of a LilyPond score PDF? The
composer or the typesetter?
Usefulness does not come into play here as long as there
On 19/03/14 18:13, Kieren MacMillan wrote:
there is no setting that says force everything onto one page, beauty be
damned
Does
\override Score.NonMusicalPaperColumn.line-break-permission = ##f
not work for you?
Cheers, Kieren.
m not met that.
My first reaction though, is
Following up on that, is there any way of altering which way round other marks
go? I certainly haven't hit the lyrics/dynamics problems (apart from
Pennsylvania I haven't used lyrics :-), but the problem I have is accents and
slurs. Lily seems to prefer to put accents above slurs, while most
Most music I've seen simply counts the number of physical bars on the
page, ignoring voltae (ie an 8-bar phrase with with two two-bar
alternatives is counted as 10 (6+2+2) bars long).
However, I have seen it counted as being 8 bars long (the second
alternate was ignored for bar-numbering
3. From what I can make out, lilypond's markup language can only handle WORDS,
not TEXT (as has been evidenced by people complaining that lilypond strips out
any attempts at spacing. It's all very well having to place each word
individually, but what do you then do if you want to change the
A point to bear in mind - and I had exactly this trouble when I first
started using lilypond ...
\transpose changes the pitch of the notes as internally represented
within lilypond. As such, I tend to think of it as a device for
inputting from and outputting to paper.
\transposition (as far as I
Can I just add a little comment (I'm not asking anybody to look at the
code, just saying if you do ... )
I regularly see repeated bars or percent bars without numbers and with
numbers. I see repeated bars followed by percent bars, with or without
numbers. Note that the numbers always count from
Sounds like a good idea for one of those all abouts. All About
Fonts. It would need a bit more digging, though, before it could be
documented in detail.
Cheers,
Wol
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Henrik Frisk
Sent: 17 August 2006
Actually, that bit about all instruments are tuned in a mathematical
way is just plain wrong :-)
Think about it ... apart from the open strings, how do you guarantee
that an a# is a b-flat on a violin? Or any other violin-like stringed
instrument, for that matter?
I play the trombone, and I
I thought the Ghostscript people were dropping the AFPL !!!
Anyways, if things haven't changed from the historic setup, they're not
actually parallel versions - the GPL is the old version.
It always used to be the case that the ghostscript writers released under the
AFPL, but that this licence
One I've met now and then
Tempo Primo - original tempo. Not sure whether that means starting
tempo, or the most recent marked tempo - I think I've met both
interpretations.
Cheers,
Wol
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Stewart Holmes
I'm guessing you're in America. What size is your output pdf? A4? If it
is and you tell the printer to print unscaled, then you're losing the
bottom 2/3 of the page.
First way round that is to tell acrobat to scale page to fit printer.
Second way is to look at the relevant section of the manual
PROTECTED]
Sent: 24 July 2006 08:57
To: Anthony Youngman
Cc: lilypond-user@gnu.org
Subject: Re: Can't set next-padding - it's ignoring me
Anthony Youngman [EMAIL PROTECTED] writes:
Okay, it's now doing what I want. Adding between-system-padding
fixed
it and reduced next-padding.
So I'm satisfied
Somethning else to look at ... a ?week? ago on the list, somebody had a
similar problem which turned out to be a bug in the call to gs. He set a
custom paper size, but when lily called gs it wasn't passing his custom
size, it was telling gs to produce an A4 pdf.
This *could* be the same bug.
Well it was ... then I copied the example in the manual and it blows up
on me ...
I'm trying to globally over-ride the next-padding property to squeeze
more systems on a page (ie get the entire piece on one page and not have
an orphan system on page 2). There's an example in the manual about
... and I think your answer to is it possible
is yes, just is it worth it?
Cheers,
Wol
-Original Message-
From: Erik Sandberg [mailto:[EMAIL PROTECTED]
Sent: 12 July 2006 19:08
To: lilypond-user@gnu.org
Cc: Anthony Youngman
Subject: Re: Evolutionary User Strategy - A Compromise
Something I thought of (having seen the comment about convert-ly using
grep ...)
I've got an on-off thing about writing a DATABASIC compiler (never mind)
and have come across a tool called Antlr. It is a compiler-compiler and
generates lexers, parsers and treeparsers.
IF someone wants to put the
on
it.
Cheers,
Wol
-Original Message-
From: Erik Sandberg [mailto:[EMAIL PROTECTED]
Sent: 12 July 2006 13:55
To: lilypond-user@gnu.org
Cc: Anthony Youngman
Subject: Re: Evolutionary User Strategy - A Compromise
On Wednesday 12 July 2006 12:59, Anthony Youngman wrote:
Something I thought
If your new system is powerful enough (and no, I haven't any experience
of this but I'm planning to do something like this myself :-)
Experiment with UML (User Mode Linux) and Gentoo. There's a good chance
that if you get a minimal gentoo system running, then tell it to install
the packages you
C below middle C is just c all by itself so the syntax should be
a, b, c= d e f g a b
(rising steadily up the bass clef :-)
I remember using this test recently, and it does work. The problem I had
(Han-Wen sent me a fix) was that I needed the facility to force an
octave change, but I didn't
things out, if you put everything in people can't see
the wood for the trees. What do you do?
Cheers,
Wol
-Original Message-
From: Graham Percival [mailto:[EMAIL PROTECTED]
Sent: 04 July 2006 16:37
To: Anthony Youngman
Cc: lilypond-user@gnu.org
Subject: Re: MultiMeasureRest - trying
I notice you're in the UK too ...
I don't know how it works, but a lot of the stuff I'm doing
may be licensable but not public domain. Especially stuff that's licenced with
the Performing Rights Society, we may be able to typeset it ourselves, then sell
(probably printed only :-( parts of
Read the documentation on rehearsal marks. One of the default styles is
to use the barnumber.
\set Score.markFormatter = #format-mark-barnumbers
Incidentally, this will also probably get round the problem of keeping
track - I guess the problem is the rehearsal mark counter isn't
automatically
That sort of works ... but if Ian wants what I want, then it's a lot
more work than just that ...
This would be a very good example for Fairchild's AllAbouts.
Certainly, until I clean it up, my version is a mess. I've got a
linebreak at the barline where my ossia starts ... with the result that
I've started writing something on noteheads. This seems to be where it
would fit in perfectly. (I probably ought to add stems and rests to it,
but that can wait :-)
I do feel something like this would be useful. As you say, we currently
have the User Manual (great for getting started) and the
investigation to follow - my current source attached ...
Cheers,
Wol
-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
Sent: 08 June 2006 12:43
To: Anthony Youngman
Cc: lilypond-user@gnu.org
Subject: Re: Lyrics problem ...
I got the same programming error but still the output
repeated in several places, so I can just drop it
into the music where it's needed ...
Cheers,
Wol
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Anthony Youngman
Sent: 12 June 2006 12:04
To: Mats Bengtsson
Cc: lilypond-devel@gnu.org; lilypond-user
...
Cheers,
Wol
-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
Sent: 12 June 2006 13:25
To: Anthony Youngman
Cc: lilypond-user@gnu.org; lilypond-devel@gnu.org
Subject: Re: Lyrics problem ... Bug? Feature? ???
Anthony Youngman wrote:
I've changed my approach - I felt all along
Just tried swapping your version for mine. No improvement :-(
And I'm still getting programming error: moving backwards in time in
the logs ...
Cheers,
Wol
-Original Message-
From: Mats Bengtsson [mailto:[EMAIL PROTECTED]
Sent: 08 June 2006 11:34
To: Anthony Youngman
Cc: lilypond-user
I'm now trying to add some words to a phrase ...
pennsylvania = {
{ \override NoteHead #'style = #'cross
r2_\markup{ shout } f8. f16 f8. f16 f4 f f8. f16 r4 }
% \addlyrics { Penn syl van ia six five thous and }
}
voiceTromboneI = \relative c' {
r2
][9][12][15][16]
Calculating page breaks...
Layout output to `partTromboneI.ps'...
Converting to `partTromboneI.pdf'...
-Original Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
.org] On Behalf Of Anthony Youngman
Sent: 07 June 2006 12:12
To: lilypond-user@gnu.org
Subject
50 matches
Mail list logo