Re: ChordMarkup context

[Kieren MacMillan]

Hi Matthew (et al.),

> My guess is that since chord names are most often used at all for things
> like popular songs, which are relatively short and may not contain a whole
> lot of other difficult engraving, this won't be prohibitive in practice.

Unfortunately, that won't help me in many of my use cases (e.g., 2-hour stage 
musicals or operas, using chord names throughout). Hopefully, this will add a 
minimal performance hit — Lilypond already takes a *long* time to compile my 
major scores.

Regards,
Kieren.


Kieren MacMillan, composer
‣ website: www.kierenmacmillan.info
‣ email: i...@kierenmacmillan.info


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ChordMarkup context

[Thomas Morley]

2017-07-05 21:53 GMT+02:00  :
> On Wed, 5 Jul 2017, Thomas Morley wrote:
>> So I tried a proof of concept, although I'm not convinced of the idea
>> to have chords as markup only.
>
> Thank you!  This seems to be a big improvement and I hope it'll reduce the
> perennial confusion people have with chord names, if we can simply point
> them to it as a way to print names that match the input.

Because it works already with 2.18.2 I've put it in the LSR
http://lsr.di.unimi.it/LSR/Item?u=1=1057
currently unapproved.

Though, no image is displayed.
This is a reappearing problem in the LSR (not with the snippet, the
code is available), obviously unsolved ...

Thus the description is a dummy for now, I have to contact the
LSR-maintainer first 

>
>> Also, one drawback may be the huge amount of string-operations. I fear
>> it may come at a cost (compilation time) and other problems once
>
> My guess is that since chord names are most often used at all for things
> like popular songs, which are relatively short and may not contain a whole
> lot of other difficult engraving, this won't be prohibitive in practice.

Probably.

I now tested with guile-2.2
Apart from a (known) warning with argument-order for string-delete, I
didn't notice any problems.

Cheers,
  Harm

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ChordMarkup context

[mskala]

On Wed, 5 Jul 2017, Thomas Morley wrote:
> So I tried a proof of concept, although I'm not convinced of the idea
> to have chords as markup only.

Thank you!  This seems to be a big improvement and I hope it'll reduce the
perennial confusion people have with chord names, if we can simply point
them to it as a way to print names that match the input.

> Also, one drawback may be the huge amount of string-operations. I fear
> it may come at a cost (compilation time) and other problems once

My guess is that since chord names are most often used at all for things
like popular songs, which are relatively short and may not contain a whole
lot of other difficult engraving, this won't be prohibitive in practice.

-- 
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.bc.ca/

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: ChordMarkup context

[Manuela Gößnitzer]

Thank you for this really nice piece of code!

2017-07-05 1:09 GMT+02:00 Thomas Morley :

> Hi all,
>
> in the long thread starting at
> http://lilypond.1069038.n5.nabble.com/Chords-in-LilyPond-td203294.html
> a method to have a more direct way to typeset chords was requested.
>
> Some quotes from different posts by Matthew:
>
> "What I think is most needed is a chord-naming mode that *just prints what
> the user typed*, formatted with the fonts, spacing, and so on that we
> expect for chord names - not translating it to an "internal
> representation" of notes plus extra data as LilyPond "music" at all."
>
> "The natural way for typesetting of chord
> names to occur is by a direct mapping from input chord names to output
> chord names without going through the current "music" data struture
> consisting of notes, at all."
>
> "Request for rootless slash chords"
> "Request for "alt" notation for chords"
> "User wants to enter:
>   \chordmode { e13 }
> and get
>   E13
> but instead he gets
>   E9 13"
> "User wants to engrave a chord they describe as "Gm7(b5)/F""
>
> As already said in this thread a possibility would be to go for Lyrics.
>
> Meanwhile a similar request appeared in the german forum.
>
> So I tried a proof of concept, although I'm not convinced of the idea
> to have chords as markup only.
> Also, one drawback may be the huge amount of string-operations. I fear
> it may come at a cost (compilation time) and other problems once
> guile2 is used (didn't try so far).
> Admittedly, it _is_ easy to put in uncommon chords
>
> See attached with new context, engraver and printing-procedure.
> I would have loved to rename lyricmode, though I think it can't be
> done without extending the parser? (I'm guessing ...)
>
> Works with 2.18.2
>
>
>
> Cheers,
>   Harm
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user