|
From: | Knut Petersen |
Subject: | Re: Write a custom backend? |
Date: | Wed, 14 Sep 2016 12:02:58 +0200 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.3.0 |
Am 13.09.2016 um 14:04 schrieb David Kastrup:
I believe the output backend principle is a good sign of extensibility but is it really the case? How to instruct Lilypond to use a custom one, then?You'd have to make use of one of the existing translator groups (like Engraver_group or Performer_group) which might me more accurately called translator groupers: there is currently no way to define those in Scheme. Personally, I'd consider it a great project to convert _all_ of Midi generation to Scheme.
Why? We need more details of the music going into \midi{}, but it is necessary to rewrite the code in scheme first? Cheers, Knut
[Prev in Thread] | Current Thread | [Next in Thread] |