It wasn't my intent to have so many posts about customizing lilypond. Eventually I'll get my tools to a usable state and talking about cadence composition itself will take precedence. Until then, it's about the only relevant information to be shared, and I apologize for this.
There's quite a bit of documentation on the web for using, programming and contributing to lilypond, but it's quite hard to wade through. After about 12 hours of reading documentation, experimenting, stumbling upon more documentation, reading through and trying to understand articulate.ly, I finally have accomplished something. It's not enough to where I can start composing hardcore, but it's a start.
I've finally found the stage in the lilypond music generation process where code I write can tweak lilypond's internal music structure and help lilypond generate more complete midi files. I thought I'd find such details in the developer documentation, but I didn't. I found it in the usage documentation, in section 6, which describes the interfaces provided to programmers. I should have known. The developer documentation is for people that are working on lilypond itself, not those that are working with lilypond to generate music. Guess that means I'm a normal user once again.
Why has it taken so long? Because lilypond is composed of tons of code, and good documentation is hard to write. And, of course, I'm new to the specific blend of programming languages and technologies that are used to make lilypond. But that is fine with me, as long as I eventually figure this mess out.
blog comments powered by Disqus