> -- Forwarded message --
> From: kbvw
> To: Lilypond-User Mailing List
> Cc:
> Bcc:
> Date: Thu, 01 Dec 2022 18:10:03 +0000
> Subject: Re: Adding text to chord names or note names (replies to
> discussion)
> Hello Jean, Elaine,
>
>
>
&g
Hi Jean,
Thanks, indeed that's useful to know. (Still learning.) Sorry about that: I'll
change it to GPLv3+ and open the issue on Gitlab.
Cheers,
Koen
--- Original Message ---
On Thursday, December 1st, 2022 at 8:31 PM, Jean Abou Samra
wrote:
> Le 01/12/2022 à 19:04, Koen van Walsti
Le 01/12/2022 à 19:04, Koen van Walstijn a écrit :
Code can be found here:
https://gitlab.com/kbvw/lilypond-tweaks/-/blob/master/harmonic-background.ly
By the way: if you want to made a piece of code available that you think
someone might want to reuse for LilyPond, you need to put it under
Le 01/12/2022 à 19:04, Koen van Walstijn a écrit :
Hello,
(Separately reply follows to some of the specific things that were
written.)
In case there is interest, what I did now was tweaking the
Current_chord_text_engraver from scheme_engravers.scm. It simply takes
the first pitch specified
Hello,
(Separately reply follows to some of the specific things that were written.)
In case there is interest, what I did now was tweaking the
Current_chord_text_engraver from scheme_engravers.scm. It simply takes the
first pitch specified in a chord as the root, takes the first one with proper
Hello Jean, Elaine,
> Amusingly, I found this post from 2001:
> https://lists.gnu.org/archive/html/gnu-music-discuss/2001-03/msg00327.html
>
> (The thread continues here:
> https://lists.gnu.org/archive/html/gnu-music-discuss/2001-04/msg0.html)
Ha, that's funny indeed. I'd say I completel
Le 30/11/2022 à 05:26, Flaming Hakama by Elaine a écrit :
I think here is where we dip into the reality that there are many
different uses of chord changes.
Chord symbols used for analysis are different than when used as an
abbreviation for specific notes/voicings, which is different when used
> Hello,
> Le 29/11/2022 à 23:22, Flaming Hakama by Elaine a écrit :
> > Lilypond provides ways both to choose among a few of the common
> > approaches, and a way to define your own.
> >
> > It does not provide a way to use different symbols for the same chord
> > in the same sequence. There are w
Hello,
Le 29/11/2022 à 23:22, Flaming Hakama by Elaine a écrit :
Lilypond provides ways both to choose among a few of the common
approaches, and a way to define your own.
It does not provide a way to use different symbols for the same chord
in the same sequence. There are workarounds for tha
2022 20:27:15 +0100
> Subject: Re: Adding text to chord names or note names
> Le 28/11/2022 à 15:37, Kieren MacMillan a écrit :
> > Hi Koen,
> >
> >> I still think it could be nice to try to write a longer-term solution.
> > There has been a lot of work done on
Le 28/11/2022 à 20:27, Jean Abou Samra a écrit :
The other piece of brainstorming I know about, although I didn’t chase
all
the discussions in the devel mailing list, is the GSoC patch. This has
the
same goal of making it easier to coerce LilyPond into formatting chord
names
the way you want, b
Le 28/11/2022 à 15:37, Kieren MacMillan a écrit :
Hi Koen,
I still think it could be nice to try to write a longer-term solution.
There has been a lot of work done on chord naming over the last decade, mainly
as part of a Google Summer of Code project a few years ago, but essentially
none of
> Le 28 nov. 2022 à 02:21, kbvw a écrit :
>
>
> Hi Jean,
>
> I just finished my reply when I saw your next message. :)
>
> Sorry, I was starting to forget about the "transposing" bit.
>
> Well, how about
>
> \version "2.22.2"
>
> t =
> #(define-music-function (text) (markup?)
>#{
>
Hi Kieren,
Thanks for your reply; I hope my message didn't come off as rude or
unsolicited.
(To be sure: I did not mean to suggest removing any functionality that's there.
I can easily see many use cases for calculating the actual pitches of a chord
internally. I meant more of an alternative
Hi Koen,
> I still think it could be nice to try to write a longer-term solution.
There has been a lot of work done on chord naming over the last decade, mainly
as part of a Google Summer of Code project a few years ago, but essentially
none of it has yet navigated through the patch submission
Hi Jean,
I just finished my reply when I saw your next message. :)
> Sorry, I was starting to forget about the "transposing" bit.
>
> Well, how about
>
> \version "2.22.2"
>
> t =
> #(define-music-function (text) (markup?)
> #{
> \once \set chordNameFunction =
> #(lambda (sorted-pitches bass inve
Le 28/11/2022 à 01:01, Jean Abou Samra a écrit :
Le 28/11/2022 à 00:41, Koen van Walstijn a écrit :
Hi Robin,
Thanks a lot! I read over that bar lines snippet indeed.
Adding the text engraver and tweaking it a bit, I managed to print
the markup above the chord symbol, so that definitely hel
Le 28/11/2022 à 00:41, Koen van Walstijn a écrit :
Hi Robin,
Thanks a lot! I read over that bar lines snippet indeed.
Adding the text engraver and tweaking it a bit, I managed to print the
markup above the chord symbol, so that definitely helped me along and
it will do for the moment.
After
Hi Robin,Thanks a lot! I read over that bar lines snippet indeed. Adding the text engraver and tweaking it a bit, I
managed to print the markup above the chord symbol, so that definitely helped me along and it will do for the
moment.After reading the documentation and Scheme source a bit more, I
On 26.11.2022 00:06, Koen van Walstijn wrote:
Ideally, I would love to be able to do something like this:
>
> \new ChordNames { \relative { c1^\markup { \super "6-9" } }}
>
> The text added to the note would get printed above the staff in a
> Staff context but gets ignored by the ChordNames c
20 matches
Mail list logo
