[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Musicology with Lilypond (and now correct attachments ;-)
From: |
Urs Liska |
Subject: |
Re: Musicology with Lilypond (and now correct attachments ;-) |
Date: |
Sun, 27 Oct 2019 22:39:40 +0000 |
Oops, forgot to CC the list.
But one more remark: You may have a look at the thread starting with
https://lists.gnu.org/archive/html/lilypond-user/2019-04/msg00335.html and
there especially the ZIP archive attached to
https://lists.gnu.org/archive/html/lilypond-user/2019-04/msg00351.html which
gives two really beautiful LilyPond renderings.
Urs
27. Oktober 2019 21:48, "Urs Liska" <address@hidden> schrieb:
> Hi Karsten,
>
> I will have a closer look into this ASAP.
> But in the meantime it may be rewarding for you to have a look at the
> http://ctan.org/pkg/lyluatex
> package.
>
> In addition I would encourage you to consider integrating your efforts with
> https://github.com/openlilylib/analysis where we even have a stub for a
> harmony module.
> One caveat though: a "perfect" tool for musicologists will have to support
> not only one style of
> analysis symbols.
> Regarding musicological use cases you might want to also have a look at
> https://github.com/openlilylib/scholarly,
> https://github.com/uliska/lyluatexmp and
> https://github.com/uliska/lycritrprt (although the last two are pretty
> preliminary). Maybe also
> https://github.com/uliska/lilyglyphs
>
> Best
> Urs
>
> Am 27. Oktober 2019 17:31:28 MEZ schrieb Karsten Reincke <address@hidden>:
>
>> Dear Friends;
>>
>> Musicologists need more than writing pure music scores. They must be
>> able to embed the score of music samples into their scientific texts.
>> And they must be able to integrate the symbols of the functional
>> harmony theory into the score of their music samples.
>>
>> For using Lilypond with LaTeX there exists a well established method to
>> embed the scores into the texts: lilypond-book. But there does not
>> exist a good, sufficient and appropriate method to integrate the
>> analysis symbols into the scores. (Unfortunately, you cannot combine
>> the LaTeX and the Lilypond techniques, because lilypond-book finally
>> embeds a picture into the LaTeX code).
>>
>> Howsoever, the needs of a LaTeX loving musicologists can completely be
>> fulfilled by using LaTex + MusixTeX + harmony (a LaTeX package). (see
>> attached file cadenca2-by-musixtex-harmony.png) But in this case, the
>> musicologist must unfortunately deal with the awkward syntax of
>> MusixTeX which he probably does not want.
>>
>> Hence we have a problem: either we use Lilypond (and cannot express,
>> what we have to do) or we use MusixTex (and reduce our productivity).
>>
>> For solving this challenge, I started to develop a GUILE based Lilypond
>> library named 'harmonyli' which follows the idea(s) of the LaTeX
>> package harmony. I published it under the MIT license in a github
>> repository [ https://github.com/kreincke/harmonyli ]. (If you feel,
>> that another license would better fit the needs and habits of the
>> Lilypond community, feel free to make respective proposals). This
>> repository contains the lib and an example (including a Makefile). This
>> example is the Lilypond code of the MusixTex-eample above (see attached
>> file cadenca2-by-lilypond-harmonyli.png)
>>
>> As you can see, the lilypond result is still a bit ugly, especially if
>> you compare it with the MusixTeX solution. Hence, I need your help for
>> improving the lib 'harmonyli':
>>
>> a) How can we place the number under the main functional symbols (T, D,
>> S, Tp, Sp Dp, Tg, Sg, etc) [ this number indicates which tone is played
>> by th bass ] exactly in the middle of the functional harmony symbols?
>>
>> b) how can we place the stack of numbers right aside of the main symbol
>> as a superscriptblock really near by the symbol and without losing the
>> feature, that each number of the stack can contain more than only one
>> number (for enabling us to express grace notes like D4>3)?
>>
>> c) How can we align the symbols in a better way - just as it is done by
>> the orginal LaTeX lib harmony?
>>
>> d) how can we enforce that the next note is printed into the staff if
>> and when the analysis symbol of the note before is completely printed?
>>
>> e) How can we enforce that all analysis symbols are printed in row with
>> suffcient space between them to understand them correctly?
>>
>> f) How can cross out the main harmony symbols for indicating that the
>> base tone is missed (=not played)? Do we need additional symbols in a
>> extra font or is there a technique to strike out any text?
>>
>> g) How can we condense / refactor the code so, that we do not have to
>> write the same code twice or more.
>>
>> If you need to see the existing code, have a look at
>> https://github.com/kreincke/harmonyli/blob/master/inc.harmonyli.ly . I
>> appreciate any help you can give. I want to develop a perfect tool for
>> musicologists - simply because I need it for a larger work of myself ;-
>> )
>>
>> How can you help me? Feel free
>> a) to comment this mail
>> b) to clone the rep, integrate your improvements and resend a pull
>> request
>> c) become an official developer by sending me your github account
>>
>> So: many thanks for your support beforehand, I am looking forward to
>> your proposals.
>>
>> heartfully your Karsten
>
> --
> Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.
- Musicology with Lilypond (and now correct attachments ;-), Karsten Reincke, 2019/10/27
- Re: Musicology with Lilypond (and now correct attachments ;-),
Urs Liska <=
- Re: Musicology with Lilypond (and now correct attachments ;-), Urs Liska, 2019/10/27
- Re: Musicology with Lilypond (and now correct attachments ;-), Karsten Reincke, 2019/10/28
- Re: Musicology with Lilypond (and now correct attachments ;-), Andrew Bernard, 2019/10/28
- Re: Musicology with Lilypond (and now correct attachments ;-), David Kastrup, 2019/10/28
- Re: Musicology with Lilypond (and now correct attachments ;-), Urs Liska, 2019/10/28
- Re: Musicology with Lilypond (and now correct attachments ;-), David Kastrup, 2019/10/28