This is a command line trick. If you run any script using the following:


command filename


and see a bunch of stuff scroll by, a way to capture the output of that command is to use a 'shell redirect' to an output file.


command filename > outputfilename


The output file, in your case, would be the new .sco file you want to create.

I would be more specific, but since I'm on Linux, my way of running Ruby scripts might be much different than yours . . . I have the script in /usr/local/bin, as an executable file, so I can just do something like


midi2sco file.mid > file.sco


to get the equivalent score file. I have no idea how this works on Windows, but if you can get the script to run at all, you can use the trick above to catch the output -- it works the same on both systems.

The ruby docs might have info on how to run ruby scripts from the command line.

==
http://www.jamendo.com/en/artist/bruce.h.mccosar
http://bmccosar.wordpress.com/

[Addendum: Heh --- I see that Bruce and I crossed paths! He may have explained things better than I did, too, but anyway this is what I said:]
I suspect you're using Windows, and not familiar with the concept of "redirection". [It's very hard when writing documentation not to make some assumptions that aren't necessarily true! (:-/)]

I gather from what you say first of all that you are able to run it from the command prompt. Do you see the score output displayed in the prompt window OK? If that's working, all you have to do to get it to go to a file is to use the same command line, but append a '>' ('greater-than') sign, followed by the name of the file you want to create. For example (leaving out the switch options you might actually want to include):

midi2sco mymidi.mid > myscore.sco

This should send the text you saw before to that file, suitable for submitting to Csound. Of course, you're likely to have to tweak the file -- add function tables and so on -- but the instrument events should be right.

And further to what Bruce said about running Ruby in Windows,
I think that as long as Ruby is "installed" and runnable from any folder you should be able to run the script OK. Probably best to have midi2sco and the files you want to work on all in the same folder, so you can just 'CD' to that folder from the command prompt and do your work there. (You may need the 'midifile' package there too, but it should also be possible to put it wherever Windows Ruby keeps its library scripts (".rb" files).)

Hope that makes it clearer. I never bothered to add any 'output' option to the program, because it's no more convenient than redirection, and I thought everyone would know about that. Obviously not!