In the case of real-time compositions, there is a further issue: what 
version(s) of Csound are required for performance (of a given piece) on 
different platforms?

What is crucial is not when the opcode was introduced, but when it was fully 
debugged.

Such a case is sensekey. (Others included various FLTK opcodes in CsoundAV.) 
Sensekey was introduced long before it became fully operable (in Windows) 
with 5.07.1. In some versions of my pieces, I need to specify 5.07.1 or 
later as required for performance. Unfortunately, I have no idea on the 
requirement for other platforms.

I suppose all this info can be had from the changelogs. I'm not making any 
suggestion; just pointing out that things are more complicated than they 
might seem.

Art Hunkins

----- Original Message ----- 
From: "Rory Walsh" 
To: 
Sent: Tuesday, January 22, 2008 9:08 AM
Subject: [Csnd] Re: Re: Re: Csound manual consistency..


Maybe we can just start the practice of doing so from now on. I'm sure
people will be adding new opcodes to Csound for many years to come, it's
nice to know when things were added. I was shocked when I saw that
pvsanal was already available in version 4.13!

Rory.





Andres Cabrera wrote:
> Hi,
>
> I think this kind of consistency is good, but determining the version
> of csound when opcodes appeared will be a massive archeological task,
> which I think serves no real purpose. If anyone wants to do it, it
> would be great, but I don't volunteer...
>
> In the case of the examples, I also agree, and welcome any
> suggestions, just send me the modified files, and I'll put them in. (I
> can't volunteer for that either =) )
>
> Cheers,
> Andrés
>
>
> On Jan 22, 2008 7:16 AM, Oeyvind Brandtsegg  wrote:
>> Agreed,
>> I also have another question:
>> The examples for each opcode uses different "approaches", for example
>> the oscil example defines named input variables,
>> but the prepiano example just use numbers.
>> I find that the way it's done in the oscil example is more readable,
>> but it will lead to a lot of example code for more complex opcodes
>> (e.g. prepiano with 17 input parameters, or partikkel with 40).
>> I think the readability issue is even more important for the complex 
>> opcodes,
>> what do others think ?
>>
>> Oeyvind
>>
>> 2008/1/22, Rory Walsh :
>>
>>> I notice that only some of the entries to the Csound manual list the
>>> version of Csound that the opcodes was first released in. Could we make
>>> this standard?
>>>
>>> Rory.
>>>
>>>
>>> Send bugs reports to this list.
>>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>>> csound"
>>>
>>
>> Send bugs reports to this list.
>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
>> csound"
>>
>
>
> Send bugs reports to this list.
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
> csound"


Send bugs reports to this list.
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe 
csound" 

his is why there is an option in the .csd file to specify which version 
number is required, or after whivh version or even before which.
Somehow it has never been popular
==John ff