[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: GSoC in contemporary notations

From: Tsz Kiu Pang
Subject: Re: GSoC in contemporary notations
Date: Thu, 21 Mar 2019 23:06:58 +1100

Hi Urs,

Thank you for your reply, and thank you so much for asking about my name.

On Thu, 21 Mar 2019 at 17:58, Urs Liska <address@hidden> wrote:

> Hi Tsz Kiu Pang (which of these names would you like to be called, or
> should I use all of them like I did?)

Tsz Kiu Pang is fine, though people usually call me Tsz Kiu, which is my
first name.

> > I was just looking at the project suggestions, and am interested in
> working
> > on contemporary notations.
> This would be great. While all of our GSoC suggestions would be very
> welcome additions this one would maybe provide the most "visible" and
> spectacular addition, opening up LilyPond for a whole range of
> applications and therefore potential users.

I am glad to hear that my interests align with you guys.

A specific composer's package would be a secondary package built on top
> of a general package, and I think it would be great to aim at starting
> one for one specific composer (the one I had always thought of as a
> basis was Lachenmann, but Xenakis or Carter are equally valid choices),
> although it is not a requirement to achieve /comprehensive/ coverage of
> a composer.

Yes, I agree that the secondary package would have to be build on top of a
general package, and this is great since I hope this project can make
contemporary notation accessible to LilyPond users in a general sense, but
not just focusing on one or two composers.

The Scheme/Guile part has three steps for you to consider:
>   * "Counting parentheses" (i.e. the language basics)
>     Depending on how far you've got
>     might be a useful resource for you. It goes only that far but it
>     specifically addresses a) the Scheme language from a dedicated
>     LilyPond perspective and b) users counting parentheses (i.e. giving
>     a pretty slow-paced introduction)
>   * Understanding how Scheme is hooked into LilyPond (on a general level)
>   * (Learning how openLilyLib ist structured)
>   * Learning how to retrieve the relevant information about score
>     elements and how to modify them in appropriate places.
> The last one is probably the hardest one since it is pretty opaque and
> terribly documented. But it's the crucial one for a contemporary
> notation package - and it's the one where such a package will make it
> hugely easier for people to work with non-standard notation.

They all sound pretty hard, but your website seems like a great resource. I
will definitely have a look at it.
Regarding learning how Scheme is hooked into LilyPond, what is some other
good resource for it, apart from your website?

Just last week I've decided to start with a new openLilyLib package:
> The repository on Github is
> empty, and right now I only have one single uncommited function locally,
> but the idea is to create building blocks for recurring tasks like
> getting the exact position of objects relative to the staff or to
> another object, enumerating all NoteColumns included in a slur or
> similar things. This will be very much relevant for a contemporary
> notation package. One could either say that you should put much of your
> results in that package, or we can try to make development of that
> package a community effort so that would take work from you, giving you
> the freedom to go further with the specific challenges.

Making the development as a community effort sounds great, though I cannot
say for sure until I have a solid proposal.

What you should do now is:
>   * [of course dive more into Scheme]
>   * get an understanding of openLilyLib with
>     a)
>     b) the code in that repository
>     c) looking at how other openLilyLib packages are built within that
>     infrastructure
>   * Form an idea how a contemporary notation package could be approached
>     and discuss that with us
>   * Find some small things you could do to openLilyLib package(s) to a)
>     practice and b) give us an opportunity to assess your work. If we
>     have some idea about your current familiarity with the matter we can
>     find some suggestions for that.

Thank you for your concrete and useful suggestions.
I will definitely learn how to count parentheses and all that, and also try
to familiarise myself with openLilyLib.
Though if you do not mind, please except a lot of questions from me in
these couple of weeks.

Tsz Kiu

> _______________________________________________
> lilypond-devel mailing list
> address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]