| > We can't just change the output value as that can be sure to break an
> important orch somewhere. Unless of course we can be sure nobody
> actually uses that opcode!
Well, I wonder whether Csound5 is a big enough overhaul that it is really
such a bad thing if a small percentage or orchestras need a small change
made to run. I know this is not supposed to happen but a change log file
somewhere could make it clear what the changes are, so that changing is
simple, and csound is small enough that it would not be hard for people to
either find the right build if indicated with the older piece or to include
the right build with the piece in any kind of historical archiving.
I just question whether perhaps we are hampering the development too much in
order to *never* violate this historical principle . . . Personally as a
user I would have no problem editing orchs to run with Csound 5 or simple
using older csound to run ones I can't be bothered to edit.
My two bits!
Iain
|