2015-06-23 13:30 GMT+02:00 Amelie Zapf a...@ameliezapf.com:
Hi David,
Pop music in the U.S.A. may be the monetary epicentre of the musical
universe, but most of LilyPond's developer base are rather removed from
there.
I must disappoint you, I'm a Berlin jazz pianist that just happens to do
2015-06-23 23:08 GMT+02:00 Thomas Morley thomasmorle...@gmail.com:
2015-06-23 13:30 GMT+02:00 Amelie Zapf a...@ameliezapf.com:
Hi David,
Pop music in the U.S.A. may be the monetary epicentre of the musical
universe, but most of LilyPond's developer base are rather removed from
there.
I
Amelie Zapf a...@ameliezapf.com writes:
As long as you don't mind me asking questions, especially on
poorly-documented functions,
I have the utmost admiration for our documentation writers but they
still have to work with what the core developers (when still around)
hand them, and the core
Hi David,
Pop music in the U.S.A. may be the monetary epicentre of the musical
universe, but most of LilyPond's developer base are rather removed from
there.
I must disappoint you, I'm a Berlin jazz pianist that just happens to do
some studio work. Since, apart from the classical scene,
Hi all,
I hope I didn't scare everybody away with my last message containing the
rhythmic specification of the Nashville Number System. That was not my
intention. But I think it would be great if Lilypond could also support
this kind of notation, since it is a quasi-standard for studio musicians
Amelie Zapf a...@ameliezapf.com writes:
Hi all,
I hope I didn't scare everybody away with my last message containing the
rhythmic specification of the Nashville Number System. That was not my
intention. But I think it would be great if Lilypond could also support
this kind of notation,
Hi all, Harm, David,
as a roadmap for all else that would be required to make Lilypond
support Nashville-style lead sheets please find attached a PDF including
pretty much all Nashville notation-specific symbols. The list was
compiled using Jim Riley: Song Charting Made Easy – A Play-Along Guide
2015-06-19 6:48 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
2015-06-18 23:37 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
\version 2.18.2
#(define nashville-chord-engraver
(let ((root (ly:make-pitch 0 0
Thomas Morley thomasmorle...@gmail.com writes:
2015-06-19 6:48 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
2015-06-18 23:37 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
\version 2.18.2
#(define
2015-06-19 22:17 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
2015-06-19 6:48 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
2015-06-18 23:37 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley
Hi Thomas,
the cleanest way would be to redefine the chordNameFunction, currently
it's 'ignatzek-chord-names'
A lot of work though...
That said, I've tried the engraver-route.
Though, I've absolutely no clue about the nashville-system, thus have
a thorough look at the output:
On Jun 18, 2015, at 10:39 AM, David Kastrup d...@gnu.org wrote:
So basically issue 1375 is in no way related to improving the
documentation about Scheme engravers. It's just about letting them
blend in a bit better with C++ engravers.
Thanks for the clarification and info. And as always
Hi Amy,
On Jun 17, 2015, at 12:48 PM, Amelie Zapf a...@ameliezapf.com wrote:
OK. I need to define an engraver, that's a statement I can live with.
However, is there any documentation or definition of the make-engraver
function anywhere that is readable to the informed layperson that has
Paul Morris p...@paulwmorris.com writes:
Hi Amy,
I'm sorry I'm such a dunce, but with the amount of documentation
supplied, make-engraver is extremely hard to grasp.
I’d say you’re doing pretty well.
Quite better than par for the course I'd say. But then it takes some
tenacity to be
Thomas Morley thomasmorle...@gmail.com writes:
2015-06-18 23:37 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
\version 2.18.2
#(define nashville-chord-engraver
(let ((root (ly:make-pitch 0 0 0)))
That should rather be
#(define
2015-06-15 9:26 GMT+02:00 Amelie Zapf a...@ameliezapf.com:
Hi Stan, Klaus,
the following snippet does Nashville numbers correctly for the key of C
(except for the rhythmical symbols). In order to adapt this to other
keys we'd need to hand the routine two pitches, the chord root and the
2015-06-18 23:37 GMT+02:00 David Kastrup d...@gnu.org:
Thomas Morley thomasmorle...@gmail.com writes:
\version 2.18.2
#(define nashville-chord-engraver
(let ((root (ly:make-pitch 0 0 0)))
That should rather be
#(define (nashville-chord-engraver context)
(let ((root (ly:make-pitch
Thomas Morley thomasmorle...@gmail.com writes:
That said, I've tried the engraver-route.
Though, I've absolutely no clue about the nashville-system, thus have
a thorough look at the output:
\version 2.18.2
#(define nashville-chord-engraver
(let ((root (ly:make-pitch 0 0 0)))
That
One more thing...
This one, however, requires a translator object as input. In
the documentation, I haven't found a proper explanation what exactly
constitutes a translator object.
A translator is either an engraver or a performer (dealing with MIDI
output).
David
Hi Amelie,
On Wed, Jun 17, 2015 at 4:52 AM, Amelie Zapf a...@ameliezapf.com wrote:
Hi all,
What's left now is to isolate this function and put it into the other
code we already have.
Rather, you need to put your code into an engraver. You then consist the
engraver to a context. You
Hi all,
What's left now is to isolate this function and put it into the other
code we already have.
I just had a go at it and am running into problems left and right. If I
call (myrootpitch (ly:context-property somecontext 'tonic)) I need a
context as input. The usual context names (like
Dear Paul, all,
thanks for your great contribution of passing the tonic as an argument.
It’s possible to create a custom engraver (with scheme) that can access this
property and do something with it. (There’s not all that much documentation
on this, but maybe look in the LSR for examples?
Hi David, everybody,
Rather, you need to put your code into an engraver. You then consist
the engraver to a context. You can't get at it within your function.
OK. I need to define an engraver, that's a statement I can live with.
However, is there any documentation or definition of the
}
}
% -
Cheers,
Klaus
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Re-Nashville-notation-as-chord-symbols-tp177872p177874.html
Sent from the User mailing list archive at Nabble.com
Dear Klaus, Stan,
the following code moves the transposition into the
#note-name-international-markup routine, thereby eliminating MIDI
playback problems. Downside: we still cannot pass the tonic to the
routine directly, but have to state it there anew.
And, of course, the rhythmic elements of
Hi all,
the remaining problem of the Scheme function is: how to access the
current root of the key signature in the function definition. For even
if we explicitly state the root again in the definition, it would be
immensely problematic if the piece contained a key change. Since
Lilypond does
Amelie Zapf a...@ameliezapf.com writes:
Dear David,
You can move MIDI playback by using \transposition
This is well-known, but reintroduces the problem of double transposition.
What is that supposed to mean?
(which only works on MIDI).
I'm sorry it doesn't. It prints a clef, key and
Hi Amy,
On Jun 15, 2015, at 9:34 AM, Amelie Zapf a...@ameliezapf.com wrote:
the remaining problem of the Scheme function is: how to access the
current root of the key signature in the function definition. For even
if we explicitly state the root again in the definition, it would be
Amelie Zapf a...@ameliezapf.com writes:
Dear Klaus, Stan,
the following code moves the transposition into the
#note-name-international-markup routine, thereby eliminating MIDI
playback problems.
You can move MIDI playback by using \transposition (which only works on
MIDI).
--
David
Dear David,
You can move MIDI playback by using \transposition
This is well-known, but reintroduces the problem of double transposition.
(which only works on MIDI).
I'm sorry it doesn't. It prints a clef, key and time signature, IIRC.
Not what you need in a row of chord symbols.
Given that
Paul Morris p...@paulwmorris.com writes:
Hi Amy,
On Jun 15, 2015, at 9:34 AM, Amelie Zapf a...@ameliezapf.com wrote:
the remaining problem of the Scheme function is: how to access the
current root of the key signature in the function definition. For even
if we explicitly state the root
Hi Stan, Klaus,
the following snippet does Nashville numbers correctly for the key of C
(except for the rhythmical symbols). In order to adapt this to other
keys we'd need to hand the routine two pitches, the chord root and the
current key, and have it compute the difference between the two,
Hello Stan, all,
I second the motion to introduce the (incredibly practical
key-independent) Nashville Number System to Lilypond.
♭7⁷ or 7♭⁷.
♭7⁷ is the official notation. Plus the NNS has a number of other
symbols for denoting breaks (long and short), anticipations, key and
meter changes,
Hi Stan,
there once was an interesting thread in the German forum:
http://www.lilypondforum.de/index.php?topic=824.0
This might be a point to start, even if it works only in C major:
%
---
\version 2.18.2
%
34 matches
Mail list logo
