On Thursday 28 October 2004 03:46 am, Matthias Neeracher wrote:
>
> On Oct 28, 2004, at 12:27 AM, David Bobroff wrote:
>
> > I'm not a developer, but this looks right to me. In your example
you
> > have a chord which is a diminished step above the tonic of the key.
> > When you transpose this d
You may want to look at the example called smart-transpose.ly
in the Tips and Tricks document of the user documentation.
/Mats
David Bobroff wrote:
On Thu, 2004-10-28 at 07:46, Matthias Neeracher wrote:
On Oct 28, 2004, at 12:27 AM, David Bobroff wrote:
I'm not a developer, but this looks right
On Thu, 2004-10-28 at 07:46, Matthias Neeracher wrote:
> On Oct 28, 2004, at 12:27 AM, David Bobroff wrote:
>
> > I'm not a developer, but this looks right to me. In your example you
> > have a chord which is a diminished step above the tonic of the key.
> > When you transpose this down one whole
On Oct 28, 2004, at 12:27 AM, David Bobroff wrote:
I'm not a developer, but this looks right to me. In your example you
have a chord which is a diminished step above the tonic of the key.
When you transpose this down one whole step it remains the same
relative
to the key.
Thanks for explaining th
I'm not a developer, but this looks right to me. In your example you
have a chord which is a diminished step above the tonic of the key.
When you transpose this down one whole step it remains the same relative
to the key.
f ges
es fes
If you were to do:
\transpose f' dis'
You would likely ge
In all version of lilypond I tried (including CVS), the following
program prints an "F flat" chord. Is this a bug, or intentional
behavior? I would have thought this should print E instead. Same
behavior with "C flat" vs. B.
Matthias
\version "2.3.23"
melody = \relative c' {
\key f \ma
