3 ms·
Another problem is that lilypond is slow, and any WYSIWYG interface to it would either bypass the compiler to show a "preview" of the score or would have a horr
by alextp 16y ago
Another problem is that lilypond is slow, and any WYSIWYG interface to it would either bypass the compiler to show a "preview" of the score or would have a horrible lag whenever the user edited something. This might not be obvious, but adding or removing (or even changing the pitch/duration of) a single note can potentially lead to a solution with completely different appearance (after all it's a dynamic programming algorithm that lays things out, considering all sorts of "badness" in the style of tex). If you remove this specificity for some greedy techniques, then it will no longer have lilypond's quality.
- BrandonM 16y agoThe performance would depend on how you interface with the library. I envision a setup where the entire piece is first written using a nice interface, that frontend then generates the text file that is passed to Lilypond, Lilypond does its magic (one time!), and then the user has an opportunity to make minor tweaks to the layout or start the cycle anew to fix mistakes.