Hi,

if someone could give some documetation on the STK opcodes in Csound i would
gladly try them out and betatest them. They are there for quite some time
now as part of Csound but i do not know at all how to implement them in an
orchestra. Is documentation available?

Menno

Bump

I really think that the opcodes in Csound, once they are there, should be
well documented. Or else these "lost" opcodes could be cleaned up and
removed so that there are less secrets in the progam and the manual.
As i said, i am willing to betatest every old opcode that has to be
documented yet - i am not a programmer but betatesting is the one thing i
can do to help to make Csound more complete and more open to the users.


menno



menno wrote:
> 
> Hi,
> 
> if someone could give some documetation on the STK opcodes in Csound i
> would gladly try them out and betatest them. They are there for quite some
> time now as part of Csound but i do not know at all how to implement them
> in an orchestra. Is documentation available?
> 
> Menno
> 

Hi Mr. Menno,
You need to look at

https://ccrma.stanford.edu/software/stk/maillist.html
https://ccrma.stanford.edu/software/stk/maillist.html 

there is stk original docs.
In Csound, if i am right, there is no documentation about these
implementations (by Mr. Gogins, again if i am right). All i know about.

ciao,
fran.

In the Windows installer, examples/CsoundAC.csd has example
instruments based on most of these opcodes. This of course is also
accessible through Csound CVS browsing at SourceForge. All the
instruments follow a similar pattern of frequency, gain, then MIDI
controller number, value pairs. The source code in
Opcodes/stk/stkOpcodes.cpp also documents this. The controller
number/value pairs are independently documented in the STK itself.

Hope this helps,
Mike

On Thu, Mar 25, 2010 at 3:29 PM, franci  wrote:
>
> Hi Mr. Menno,
> You need to look at
>
> https://ccrma.stanford.edu/software/stk/maillist.html
> https://ccrma.stanford.edu/software/stk/maillist.html
>
> there is stk original docs.
> In Csound, if i am right, there is no documentation about these
> implementations (by Mr. Gogins, again if i am right). All i know about.
>
> ciao,
> fran.
>
>
> --
> View this message in context: http://old.nabble.com/STK-tp27977017p28033730.html
> Sent from the Csound - General mailing list archive at Nabble.com.
>
>
>
> Send bugs reports to the Sourceforge bug tracker
>            https://sourceforge.net/tracker/?group_id=81968&atid=564599
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"
>
>



-- 
Michael Gogins
Irreducible Productions
http://www.michael-gogins.com
Michael dot Gogins at gmail dot com


Send bugs reports to the Sourceforge bug tracker
            https://sourceforge.net/tracker/?group_id=81968&atid=564599
Discussions of bugs and features can be posted here
To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound"

In erlier posts about the STKopcodes i read that that there was a problem in
legally distributing them in a program like Csound, so they were taken out
of the Csound distribution. Do i understand this correctly? 
Now i looked at https://ccrma.stanford.edu/software/stk/faq.html and found
this about the licensing: 

The Synthesis ToolKit in C++ (STK) 
Copyright (c) 1995-2010 Perry R. Cook and Gary P. Scavone 

Permission is hereby granted, free of charge, to any person obtaining 
a copy of this software and associated documentation files (the 
"Software"), to deal in the Software without restriction, including 
without limitation the rights to use, copy, modify, merge, publish, 
distribute, sublicense, and/or sell copies of the Software, and to 
permit persons to whom the Software is furnished to do so, subject to 
the following conditions: 

The above copyright notice and this permission notice shall be 
included in all copies or substantial portions of the Software. 

Any person wishing to distribute modifications to the Software is 
asked to send the modifications to the original developer so that they 
can be incorporated into the canonical version.  This is, however, not 
a binding provision of this license. 


Does that mean that the STKopcodes can be put back in the standard
distribution? and being documented normally in the manual? 

Menno Knevel