[Top][All Lists]

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

Re: Storing information in scores

From: Kieren MacMillan
Subject: Re: Storing information in scores
Date: Sun, 19 Dec 2021 09:59:56 -0500

p.s. Also compare with Urs's "ScholarLY" framework 
(, which is "a library for annotating 
LilyPond scores".
— K

> On Dec 19, 2021, at 9:58 AM, Kieren MacMillan <> 
> wrote:
> Hi Valentin,
>> I've created this small mockup of how we can store additional information in 
>> scores and let Lilypond manage it. The idea is: One might have different 
>> versions of a part of a score, be it different sources or different edits 
>> within a source. 
>> So instead of selecting some version (and maybe putting the other ones into 
>> a critical apparatus) we can have Lilypond store this additional information 
>> and then do the selecting programmatically. 
>> As I said this is a mockup and is missing many important features, like 
>> detailed overrides, nested edits and such. 
> I don't have time to examine this today, but I can't wait to see what you've 
> done!
> One immediate thought [based solely on your description]: If you don't 
> already know the edition-engraver reasonably well, you might want to see 
> whether your implementation and the EE are redundant / complementary / 
> orthogonal / somethingElse, and possibly work with Jan-Peter [et al.] to get 
> a single interface for "multi-source" and "edition" management (which I 
> believe is critical to the future of Lilypond as a serious engraving tool).
> Best regards,
> Kieren.

reply via email to

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