Help wanted: editor web-page!
Hi, I thought it would be neat if we could help aspiring LilyPond users select the best environment for them to work in. I think that newbie users would be helped a lot if there were a webpage that lists * all text-editors with LilyPond support (emacs, vim, jedit, ... ? ) * all (MIDI) keyboard entry utilities (rumor, lyqi, ? ) * all GUIs with LilyPond support (rosegarden, denemo, noteedit, .. ?) * all formats where we have conversion utilites (abc, etf, .. ?) such a page would briefly discuss each solution, show a couple of nice screenshots, and explain what platforms it runs, where to get more information and where to download the stuff. Are there anyone who would like to create such an overview? -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Markup in lyrics
One possible solution is to use a separate Staff context, where you have
peeled off most normal engravers and reduced the font size.
However, the idea of allowing for general text markups in lyrics would
certainly be useful in several occasions. I send a copy of this feature
request to the lilypond-devel list.
/Mats
Bertalan Fodor wrote:
Hello,
is there any possibility to use markup in lyrics (2.2.5), I mean sg like
this:
\new Lyrics \lyrics { interesting^\markup{\tiny \note #"4" #0.7 = 160}
lyrics }
Actually I need the following effect:
This is stan -- dard rythm.
|| |--|||
This is nonstan -- dard rythm.
That is, printing ryhtm above the second line of lyrics. Could it be
done with embeddedps or something?
Thank you much,
Bert
___
lilypond-user mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
> As of CVS ChangeLog 1.2763 I get a 'make all' failure: Fixed. I forgot to remove the @loggingall statement. Werner ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
Herman Grootaers writes: > Thanks, Jan, for the info, but then configure should have given an error. Yes, either that, or we should refrain from using @ifdocbook. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
On Thursday 28 October 2004 10:52, you wrote: > The log says > > > ./out/macros.texi:98: Onbekend commando `ifdocbook'. > > which means build depends should require makeinfo 4.7. > Thanks, Jan, for the info, but then configure should have given an error. I will get the makeinfo rpm to get it working again. Thanks again. -- Herman Grootaers ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: lilypond-snapshot ps2png
There is a ps2png program included in the LilyPond source code, so it's probably a packaging error that it's not included in the debian package. However, if there's a risk for name collisions with other packages, it's maybe not a good idea that the script is called exactly ps2png. /Mats Karl Hammar wrote: D Josiah Boothby <[EMAIL PROTECTED]> wrote: ... do i need to install another package to get ps2png, or do i need to download the source from somewhere? (the lazy debian user doesn't want do do that :) ... The lazy debian user would install tth: $ grep ps2png /var/lib/dpkg/info/*.list /var/lib/dpkg/info/tth.list:/usr/bin/ps2png /var/lib/dpkg/info/tth.list:/usr/share/man/man1/ps2png.1.gz --- [EMAIL PROTECTED] 10:31:36 --- ~/most/music/musixtex/jo_ct_kyriew --- $ apt-cache show tth Package: tth Priority: optional Section: non-free/tex Installed-Size: 852 Maintainer: Ian Maclaine-cross <[EMAIL PROTECTED]> Architecture: i386 Version: 3.60-1 Depends: libc6 (>= 2.3.2.ds1-4) Recommends: tetex-base, tetex-bin, gs, netpbm Filename: pool/non-free/t/tth/tth_3.60-1_i386.deb Size: 296014 MD5sum: da37bd52a95a93c64775f585694832af Description: TeX/LaTeX to HTML converter LaTeX is popular for specifying complex printed documents. TtH translates Plain TeX or LaTeX documents into HTML. It quickly produces web documents that are compact, editable and fast viewing. TtH translates most equations instead of converting them into images. This HTML preserves much format when imported by MS Word. . TtH needs teTeX to generate auxiliary files for cross references and content tables. Complex equations and graphics require gs and netpbm to convert PostScript output from teTeX to images. Regards /Karl ___ lilypond-user mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-user -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Transposed Chord name "F flat"
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 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 this logic. My music theory is not overly sound, so I'm perfectly willing to accept that there is a sound theoretical justification for this. Nevertheless, I'd still argue that on a practical level, "E" might be preferable here. It may indeed be more convenient to read 'e' than 'fes', but LilyPond is simply maintaining an internal consistency. f ges es fes If you were to do: \transpose f' dis' You would likely get 'e' instead of 'fes' and this would be consistent with the above logic. Sure, but Jazz pianists tend to take a dim view of singers showing up with a lead sheet transposed into D sharp major :-) I'm sure they do, and I'm certainly not suggesting that you do this. However, I could (and probably will) transpose the song into D or E instead. Likewise, if you had written a fis chord, it would have come out as an e chord after your transposition. Yes, but it seems somewhat counterintuitive that in order to avoid "weird" chord names in chords with flats, I have to transpose into a key with sharps, and vice versa. It could be argued that a ges chord in f major is already a "weird" chord for the key. Yes, I do understand that jazz uses a lot of altered chords. As a further example, I recently did a transposition of an orchestral part. It was written in bass clef and transposing, sounding a whole step lower than written. This is a somewhat archaic German/Austrian practice. The part needed to be written a step lower. I did it using LilyPond. I entered the part as written and then used \transpose. At one point there was a 'fes' in the original. In the transposition it came out as 'ees'. In a hand-written copy of the transposed part this had been rendered as 'd'. I eventually found my copy of an engraved transposed part and it was rendered as 'ees' --- the same as LilyPond. The developers of LilyPond strive to recreate the look of European engraving of the 19th century. This pre-dates jazz notation. To deal with things like your 'ges' chord in 'f' becoming a 'fes' chord in 'es', you will probably have to call it 'fis' in your input file to get what you want (i.e. 'e' in 'es'). I see this not as a shortcoming of LilyPond, but a difference between the two practices. -David ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel -- = Mats Bengtsson Signal Processing Signals, Sensors and Systems Royal Institute of Technology SE-100 44 STOCKHOLM Sweden Phone: (+46) 8 790 8463 Fax: (+46) 8 790 7260 Email: [EMAIL PROTECTED] WWW: http://www.s3.kth.se/~mabe = ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
Herman Grootaers writes: The log says > ./out/macros.texi:98: Onbekend commando `ifdocbook'. which means build depends should require makeinfo 4.7. Jan. -- Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPond - The music typesetter http://www.xs4all.nl/~jantien | http://www.lilypond.org ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 'make all' fails
On Thursday 28 October 2004 08:40, David Bobroff wrote: > As of CVS ChangeLog 1.2763 I get a 'make all' failure: > > Compiling ./out/music-glossary.texi... > Processing include: macros.itexi > Reading macros.itexi... > Dissecting... > Writing snippets... > All snippets are up to date... > Compiling ./out/macros.texi... > mv ./out/music-glossary.texinfo out/music-glossary.nexi 2>/dev/null || > mv ./out/music-glossary.texi out/music-glossary.nexi > if [ 4007000 -le 4006000 ]; then \ > (cd ./out && \ > ls -1 lily-*.ly | sed 's/.ly$/.txt/' | xargs touch) || true; \ > fi > LANG= makeinfo --enable-encoding -I ./out > --output=./out/music-glossary.info out/music-glossary.nexi > out/music-glossary.nexi:5707: Unknown command `loggingall'. > makeinfo: Removing output file `./out/music-glossary.info' due to > errors; use --force to preserve. > make[2]: *** [out/music-glossary.info] Error 1 > rm out/music-glossary.nexi > make[2]: Leaving directory `/usr/src/lilypond/Documentation/user' > make[1]: *** [all] Error 2 > make[1]: Leaving directory `/usr/src/lilypond/Documentation' > make: *** [all] Error 2 > On my mandrake 10.0 box, fully patched, I got a seg-fault on the documentation when I tried to make all on the tar-ball of 2.3.24. Make install dumped its core on the same place it looks like, but I forgot to append the output to the logfile. The coredump was not alas saved. What I did notice was that 2.3.23 seems to have the same problem on the same place, but it did not give no error messages, and it did do a successfull make install. The original log file: [EMAIL PROTECTED] dev]$ lla make.log -rw-r--r-- 1 herman herman 4549063 okt 27 09:28 make.log [EMAIL PROTECTED] dev]$ wc make.log 97084 738441 4549063 make.log ** make.log # total of 9621 lines snipped make[1]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation' /home/herman/lily/dev/stepmake/stepmake/generic-targets.make:143: out/dummy.dep: No such file or directory please ignore innocent warning about dummy.dep mkdir -p ./out touch ./out/dummy.dep make[1]: Leaving directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation' make[1]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation' make PACKAGE=LILYPOND package=lilypond -C user all && make PACKAGE=LILYPOND package=lilypond -C bibliography all && make PACKAGE=LILYPOND package=lilypond -C pictures all && make PACKAGE=LILYPOND package=lilypond -C topdocs all && make PACKAGE=LILYPOND package=lilypond -C misc all && true make[2]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation/user' /home/herman/lily/dev/stepmake/stepmake/generic-targets.make:143: out/dummy.dep: No such file or directory please ignore innocent warning about dummy.dep mkdir -p ./out touch ./out/dummy.dep make[2]: Leaving directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation/user' make[2]: Entering directory `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/Documentation/user' cd ./out && /home/herman/lily/dev/lily/out/lilypond --verbose /home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/ly/generate-documentation LILYPOND_DATADIR="/usr/local/share/lilypond" LOCAL_LILYPOND_DATADIR=/usr/local/share/lilypond/2.3.24" LOCALEDIR="/usr/local/share/locale" LILYPONDPREFIX="/home/herman/lily/dev/share/lilypond" Nu wordt verwerkt `/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/ly/generate-documentation.ly' Ontleden... [/home/herman/lily/dev/share/lilypond/ly/init.ly[/home/herman/lily/dev/share/lilypond/ly/declarations-init.ly[/home/herman/lily/dev/share/lilypond/ly/music-functions-init.ly] [/home/herman/lily/dev/share/lilypond/ly/nederlands.ly] [/home/herman/lily/dev/share/lilypond/ly/drumpitch-init.ly] [/home/herman/lily/dev/share/lilypond/ly/chord-modifiers-init.ly] [/home/herman/lily/dev/share/lilypond/ly/script-init.ly] [/home/herman/lily/dev/share/lilypond/ly/scale-definitions-init.ly] [/home/herman/lily/dev/share/lilypond/ly/grace-init.ly] [/home/herman/lily/dev/share/lilypond/ly/midi-init.ly[/home/herman/lily/dev/share/lilypond/ly/performer-init.ly]] [/home/herman/lily/dev/share/lilypond/ly/paper-defaults.ly] [/home/herman/lily/dev/share/lilypond/ly/engraver-init.ly] [/home/herman/lily/dev/share/lilypond/ly/dynamic-scripts-init.ly] [/home/herman/lily/dev/share/lilypond/ly/spanners-init.ly] [/home/herman/lily/dev/share/lilypond/ly/property-init.ly]] [/home/herman/Documents/Lilypond/Lilypond/lilypond-2.3.24/ly/generate-documentation.ly]] [/home/herman/lily/dev/share/lilypond/scm/define-music-types.scm] [/home/herman/lily/dev/share/lilypond/scm/output-lib.scm] [/home/herman/lily/dev/share/lilypond/scm/c++.scm] [/home/herman/lily/dev/share/lilypond/scm/chord-ignatzek-names.scm] [/home/herman/lily/dev/share/lilypond/scm/chord-entry.scm] [/home/herman/lily/dev/share/lilypond/scm/chord-generic-names.scm] [/home/herma
Re: Transposed Chord name "F flat"
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 step it remains the same > > relative > > to the key. > > Thanks for explaining this logic. My music theory is not overly sound, > so I'm perfectly willing to accept that there is a sound theoretical > justification for this. Nevertheless, I'd still argue that on a > practical level, "E" might be preferable here. It may indeed be more convenient to read 'e' than 'fes', but LilyPond is simply maintaining an internal consistency. > > > f ges > > > > es fes > > > > If you were to do: > > > > \transpose f' dis' > > > > You would likely get 'e' instead of 'fes' and this would be consistent > > with the above logic. > > Sure, but Jazz pianists tend to take a dim view of singers showing up > with a lead sheet transposed into D sharp major :-) > I'm sure they do, and I'm certainly not suggesting that you do this. > However, I could (and probably will) transpose the song into D or E > instead. > > > Likewise, if you had written a fis chord, it would have come out as an > > e > > chord after your transposition. > > Yes, but it seems somewhat counterintuitive that in order to avoid > "weird" chord names in chords with flats, I have to transpose into a > key with sharps, and vice versa. > It could be argued that a ges chord in f major is already a "weird" chord for the key. Yes, I do understand that jazz uses a lot of altered chords. As a further example, I recently did a transposition of an orchestral part. It was written in bass clef and transposing, sounding a whole step lower than written. This is a somewhat archaic German/Austrian practice. The part needed to be written a step lower. I did it using LilyPond. I entered the part as written and then used \transpose. At one point there was a 'fes' in the original. In the transposition it came out as 'ees'. In a hand-written copy of the transposed part this had been rendered as 'd'. I eventually found my copy of an engraved transposed part and it was rendered as 'ees' --- the same as LilyPond. The developers of LilyPond strive to recreate the look of European engraving of the 19th century. This pre-dates jazz notation. To deal with things like your 'ges' chord in 'f' becoming a 'fes' chord in 'es', you will probably have to call it 'fis' in your input file to get what you want (i.e. 'e' in 'es'). I see this not as a shortcoming of LilyPond, but a difference between the two practices. -David ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: box widths
[EMAIL PROTECTED] writes: > On Wed, 2004-10-27 at 08:36, Werner LEMBERG wrote: > > I have a fundamental problem with the width of lilypond output, and > > which should be fixed before releasing 2.4. Currently, I use > > > > (interval-start (ly:stencil-extent page X)) > > > > but this isn't the right value. Reason: Contrary to TeX boxes, > > lilypond's horizontal reference point is not always the left edge of > > the output box: > > > > ^ > > | > > ++--+ > > || | > > || | > > ++--+---> AO B > > || | > > ++--+ > > | > > | > > > > We have `height' and `depth' as with TeX boxes, and we have `width' > > and `extension' (to coin this term), where `width' is the amount right > > of the y-axis, and `extension' the left amount (and let's assume that > > `extension' is positive). > > > > The above scheme code gives `width + extension', but I need `width' > > only. How can I get that? ly:stencil-extent will return a pair (A . B) with A < B, and A typically negative. I've added a ly:stencil-origin, which returns the coordinates of O. HTH, Han-Wen -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Fingering
Please always keep the discussion on the mailing list, for the
benefit of yourself since you get access to the collected
expertise on the list and for the benefit of others who experience
similar problems. I hope you don't mind that I forward your answer
to the mailing list.
/Mats
TIM HUCKER wrote:
In accordion music it indicates that you should use the counterbass row
of buttons in the left hand. I don't know how many accordionists use
Lilypond, but I've engraved several accordion pieces very sucessfully.
Thanks again
Tim Hucker
*/Mats Bengtsson <[EMAIL PROTECTED]>/* wrote:
By the way, why do you want underlined fingerings? Does the underlining
denote any difference compared to normal fingerings? (Just trying to
figure out if there's any reason to add regular support for this in
LilyPond.)
/Mats
TIM HUCKER wrote:
> Sorry about the misposting - a slip of the finger after a long day!
>
> Will try your solutions tonight on Lilypond 2.2.2.
>
> Many thanks
>
> Tim Hucker
>
> */Mats Bengtsson /* wrote:
>
> Please send usage questions like this to [EMAIL PROTECTED] and
> save this mailing list for actual bug reports. All the mailing
> lists and links to the archives are available at www.lilypond.org
> if you click on "About".
>
> Also, always tell which version of LilyPond you use, otherwise you
&g t; might get an answer that's irrelevant for your version.
>
> TIM HUCKER wrote:
> > Two questions:
> >
> > 1 Does anyone know the best way of underlining fingering
> instructions?
>
> That's not supported for the moment. In LilyPond up to version 2.2.6,
> you could do it with inline LaTeX code, something like
> c4^"$\underline{3}$"
>
> > 2 What is the best way to make my fingering appear always under the
> > note. I have tried
> >
> > \set fingeringOrientations = #'(down)
> >
> > without success.
> fingeringOrientations is only r elevant when you have a chord.
> To set the direction of all fingerings below the stave, use
> \override Fingering #'orientation = #down
> or simply use
> c_3
> instead of
> c-3
> to force a single fingering below the note. Similarly,
> c^3
> gives a fingering above th e note.
>
> /Mats
>
> > Any advice gratefully received.
> >
> > Regards
> >
> > Tim Hucker
> >
> >
> >
>
> > *ALL-NEW Yahoo! Messenger*
> > * - all
> > new features - even more fun!** *
> >
> >
> >
>
> >
> > ___
> > bug-lilypond mailing list
> > [EMAIL PROTECTED]
> > http://lists.gnu.org/mailman/listinfo/bug-lilypond
>
> --
> =
> Mats Bengtsson
> Signal Processing
> Signals, Sensors and Systems
> Royal Institute of Technology
> SE-100 44 STOCKHOLM
> Sweden
> Phone: (+46) 8 790 8463
> Fax: (+46) 8 790 7260
> Email: [EMAIL PROTECTED]
> WWW: http://www.s3.kth.se/~mabe
> =
>
>
> *ALL-NEW Yahoo! Messenger*
> * - all
> new features - even more fun!** *
>
>
>
>
> ___
> lilypond-user mailing list
> [EMAIL PROTECTED]
> http://lists.gnu.org/mailman/listinfo/lilypond-user
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
Send instant messages to your online friends http://uk.messenger.yahoo.com
--
=
Mats Bengtsson
Signal Processing
Signals, Sensors and Systems
Royal Institute of Technology
SE-100 44 STOCKHOLM
Sweden
Phone: (+46) 8 790 8463
Fax: (+46) 8 790 7260
Email: [EMAIL PROTECTED]
WWW: http://www.s3.kth.se/~mabe
=
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Transposed Chord name "F flat"
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 this logic. My music theory is not overly sound, so I'm perfectly willing to accept that there is a sound theoretical justification for this. Nevertheless, I'd still argue that on a practical level, "E" might be preferable here. f ges es fes If you were to do: \transpose f' dis' You would likely get 'e' instead of 'fes' and this would be consistent with the above logic. Sure, but Jazz pianists tend to take a dim view of singers showing up with a lead sheet transposed into D sharp major :-) However, I could (and probably will) transpose the song into D or E instead. Likewise, if you had written a fis chord, it would have come out as an e chord after your transposition. Yes, but it seems somewhat counterintuitive that in order to avoid "weird" chord names in chords with flats, I have to transpose into a key with sharps, and vice versa. Matthias ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Transposed Chord name "F flat"
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 get 'e' instead of 'fes' and this would be consistent
with the above logic.
Likewise, if you had written a fis chord, it would have come out as an e
chord after your transposition.
Hope this helps.
-David
On Thu, 2004-10-28 at 07:19, Matthias Neeracher wrote:
> 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 \major
> c1
> }
>
> accompaniment = \chordmode { ges1 }
>
> \score {
> \simultaneous {
>\context ChordNames \transpose f' es' \accompaniment
>\context Voice = "mel" \transpose f' es' \melody
> }
>
> }
>
>
>
> ___
> lilypond-devel mailing list
> [EMAIL PROTECTED]
> http://lists.gnu.org/mailman/listinfo/lilypond-devel
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Transposed Chord name "F flat"
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 \major
c1
}
accompaniment = \chordmode { ges1 }
\score {
\simultaneous {
\context ChordNames \transpose f' es' \accompaniment
\context Voice = "mel" \transpose f' es' \melody
}
}
___
lilypond-devel mailing list
[EMAIL PROTECTED]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
