Carl Sorensen schrieb:
On 8/8/09 2:20 PM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
[...]
For the music-function you can do this:
% you can also do:
% mybool = ##f
#(define mybool #f)
Why not just change this to
#(define-public mybool #f)
Kieren MacMillan Sunday, August 09, 2009 4:47 AM
From my point of view the main use for smallStaff (or whatever it
gets called) is for ossia staves.
Except IIRC ossia staves and solo/cue staves are usually of
different sizes, yes?
In scores for a capella vocal music a piano
On Sat, Aug 8, 2009 at 4:00 PM, Mike
Blackstockblackstock.m...@gmail.com wrote:
Just an idea on typesetting popular music that people would recognize but
that have copyright issues: quite a number of these songs are, as suggested
in another thread, older non-copyrighted songs with new lyrics
Trevor Daniels schrieb:
[...]
From what I see on the console output, the calls of \myMusicFunc
are evaluated first, so myBool is #t and the callbacks come in action
afterwards (the first slur claims #t, every other slur reads #f), so
apparently they don't influence each other the way I
Le 9 août 09 à 13:21, Marc Hohl a écrit :
#(define-public (slur::boolean grob)
;; just a test function to try and switch boolean values
(display \nWithin callback\n)
(display myBool: )(display myBool)(newline)
(if myBool
(set! myBool #f)
(set! myBool #t))
this can be
On 8/9/09 5:21 AM, Marc Hohl m...@hohlart.de wrote:
Trevor Daniels schrieb:
[...]
From what I see on the console output, the calls of \myMusicFunc
are evaluated first, so myBool is #t and the callbacks come in action
afterwards (the first slur claims #t, every other slur reads #f),
Running a search for roman numeral on the one big page of the lilypond
documentation doesn't give any results. Section 1.7.2 had the correct kind
of brackets used in analyzing modulation and pivot chords, but the brackets
are horizontal, not vertical, like they should be. Is there a way to get
2009/8/8 Mike Blackstock blackstock.m...@gmail.com:
Just an idea on typesetting popular music that people would recognize but
that have copyright issues: quite a number of these songs are, as suggested
in another thread, older non-copyrighted songs with new lyrics added and
typesetting the
Hope this helps to clarity things for you...
I have been looking at ways to tidy up my lilypond scripts. So, I've
made an attempt to follow the good supply of examples in the various
lilypond documents.
One adapted suggestion I've sourced from the Lilypond Learning Manual
(5.1.3) runs as
On 09.08.2009, at 14:51, lelangir wrote:
Running a search for roman numeral on the one big page of the
lilypond documentation doesn't give any results. Section 1.7.2 had
the correct kind of brackets used in analyzing modulation and pivot
chords, but the brackets are horizontal, not
Nicolas Sceaux schrieb:
Le 9 août 09 à 13:21, Marc Hohl a écrit :
#(define-public (slur::boolean grob)
;; just a test function to try and switch boolean values
(display \nWithin callback\n)
(display myBool: )(display myBool)(newline)
(if myBool
(set! myBool #f)
(set! myBool
Carl Sorensen schrieb:
On 8/9/09 1:20 AM, Marc Hohl m...@hohlart.de wrote:
Was there something else you were trying to do?
Yes, I have to change the value of myBool within a
stencil callback.
Like this:
\version 2.13.3
#(define myBool #f)
myMusicFunc =
#(define-music-function
On Aug 9, 2009, at 9:05 AM, Simon Mackenzie wrote:
So again my question is, how can I assign a new value to a variable
so I can make all this happen and keep my global declarations /
assignments to an absolute minimum and meet my goal of ensuring
good clarity in my lilypond code for
Samuel Hartmann wrote:
In the OOoLilyPond templates I have include #(define dump-extents
#t) like it is produced by lilypond-book output. What is the effect
of this line? I haven't found anything about it in the LilyPond
documentation.
I would like to leave it away, if it does not have
2009/8/7 Joe Neeman joenee...@gmail.com:
On Thu, 2009-08-06 at 23:03 +0100, Neil Puttock wrote:
2009/8/6 Joe Neeman joenee...@gmail.com:
You probably made the same mistake that I made initially: if you prune a
breakable column then you've pruned it's broken pieces (ie. the
line-ending and
lelangir wrote:
Running a search for roman numeral on the one big page
If you don't find things in the documentation,
try searching this mailing list and the snippet repository too.
Have a look at this (the example from Matthew Durell):
I think this was sent only to me and not to the list.
Begin forwarded message:
From: Hugo Leonardo Ribeiro hugole...@gmail.com
Date: 9. August 2009 21:06:06 MESZ
To: James E. Bailey derhindem...@googlemail.com
Subject: Re: roman numeral chord notation below staff with pivot
chord brackets?
Mark Polesky wrote Saturday, August 08, 2009 6:30 PM
Kieren MacMillan wrote:
p.s. Valentin (and/or other Doc-tors): Shouldn't we mention in
this section that
ragged-right is true for single-system scores? If not, where is
this default
mentioned?
If you look up ragged-right in the NR
-- Forwarded message --
From: Olli Niemi ollin...@gmail.com
Date: Sun, Aug 9, 2009 at 10:45 AM
Subject: Decrescendo
To: han...@xs4all.nl
Hi,
I've read the notational guide for \ marking for decrescendo.
To my understanding it is possible to mark it for a note.
However, if I want
I'd like to make the decrescendo to start after the treble clef's c
e, c4., so that it starts from the bass line's c g e8.
So it actually should not start from the d,,16( but instead one
chord before it for the bass clef.
The starting position for it should be bass clef's chord c g e8.
How do
Hi, you can attach the hairpin to the bass part, and use a ^ to have it above
the staff. Using spacer rests (not with \\ ) you can define places for the
hairpin to start or end (as in this example:).
\version 2.13.1
upper = \relative c''' {
c e, c4. d,,16( dis16)
}
lower = \relative c' {
Below is a simple E major scale. I don't want lilypond to stretch the stems of
the lower notes up to the B staff line. I want all the note-stems to be the
same length for both stemUp and stemDown notes. Is there an option to turn off
the stem stretching?
\version 2.13.3
\include english.ly
On 8/9/09 9:12 AM, Marc Hohl m...@hohlart.de wrote:
Carl Sorensen schrieb:
So that is why the first value in the callback was #t -- it was left over
from the last call of \myMusicFunc. Then the remaining values were #f,
because all of the calls to \myMusicFunc had already been
Peter Buhr wrote:
Below is a simple E major scale. I don't want lilypond to
stretch the stems of the lower notes up to the B staff line. I
want all the note-stems to be the same length for both stemUp
and stemDown notes. Is there an option to turn off the stem
stretching?
I think it looks
2009/8/9 Mark Polesky markpole...@yahoo.com:
I think it looks very odd to do this, but here you go:
\override Stem #'no-stem-extend = ##t
A small refinement:
\override Stem #'(details stem-shorten) = ##f
Regards,
Neil
___
lilypond-user mailing
Neil Puttock wrote:
\override Stem #'no-stem-extend = ##t
A small refinement:
\override Stem #'(details stem-shorten) = ##f
Neil,
can you explain why that is preferable? Also, using this
for Peter's scale produced something completely weird:
\override Stem #'length = #3.5
Is that the
2009/8/9 Mark Polesky markpole...@yahoo.com:
can you explain why that is preferable?
It's what Peter requested:
I want all the note-stems to be the same length for both stemUp and
stemDown notes.
\override Stem #'length = #3.5
Is that the expected behavior of that override?
It's overridden
On Sun, Aug 09, 2009 at 09:05:41PM +0700, Simon Mackenzie wrote:
One adapted suggestion I've sourced from the Lilypond Learning Manual (5.1.3)
runs as follows...
MUSICBOOK.ly contains the list of all music sheets for the music book.
I don't think that was suggested in LM 5.1.3. This isn't a
I don't want lilypond to stretch the stems of the lower notes up to the B
staff line. ...
I think it looks very odd to do this, but here you go:
\override Stem #'no-stem-extend = ##t
Thanks, that's doing what I want. In general, I agree it looks very odd.
However, I'm decorating
On Sun, 2009-08-09 at 18:45 +0100, Neil Puttock wrote:
2009/8/7 Joe Neeman joenee...@gmail.com:
How about just checking for an empty extent, like in the attached patch?
That's probably the best option, since it should allow users to take
advantage of setting X-extent for other barline
I've read the notational guide for \ marking for decrescendo.
To my understanding it is possible to mark it for a note.
However, if I want to start it for a note in the bass clef, is this possible?
I have the following in treble clef (in 2/4 time):
c e, c4. d,,16( dis16)
And this in the
31 matches
Mail list logo
