ssj71 wrote:male wrote:What is this thread even about? If defining the name and number of ports of a plugin is a greater burden to you than writing the DSP part, then you shouldn't be writing plugins in the first place.
If, on the other hand, this is about generating DSP code from block diagrams a la Faust, then that's all well and good, but what does it have to do with TTL (or any other purely external description)?
Help me see the point here...
Its about being lazy. DSP code is challenging and fun, and less likely to be related between plugins and devs. Writing the TTL is tedious, syntactically strict, and somewhat unfamiliar to me. I don't mean to make a statement on whether it should be used or whatever, but I can imagine a tool that would make writing it a little quicker and more organized. If its going to start an argument I'll just keep writing the ttl by hand.
Well, writing by hand is foolish when you can just copy and paste. Alternatively, any macro processor (m4, cpp, bash, your editor, whatever) can reduce the workload to effectively filling out a form. You should look at the way the swh plugins are generated. Each plugin is defined in an XML file, which is used to generate LADSPA or LV2 versions at build time. Not that I'm recommending using XML.