I'm going to be programming a tracker that generates .sco files for CSound. It will be built to work with CSound so that you can use it like you would a traditional DAW, previewing bits and patterns, or even your entire song. All you will need is to supply it with a CSound orchestra file, and it will handle everything else for you. That way, you can make your own instruments in the same way you would normally, but managing them is much easier. Chances are that it will work by simply creating .sco files for the parts you want to listen to and calling CSound directly from the command line.

While I had originally intended this as a tool for personal use, it occurred to me that others might be interested, and so I'd like to have some input from experienced CSound users as to how this would be best implemented. I'm fairly new to CSound itself, but as a programmer and experienced Max/MSPer it has come to me fairly easily. However, I realize that I may not be going about this in quite the right manner, and while it would be a fairly simple task to write a program to assemble scores for me, maybe there is an easier and more efficient solution. Also, if/when I ever release this to the public, it would be nice to have the blessing of the CSound community.

Anyways, now I'm just ranting. I'd really like to hear everyone's thoughts on this, so shoot.