On Fri, Feb 22, 2013 at 3:25 PM, Justin Smith  wrote:
> except there are valid reasons to want to build and distribute csound without those opcodes.

I'm curious: why would anyone want to distribute csound without these opcodes? I cannot imagine any advantages.


Lou Cohen
www.jolc.net
www.opensound.org

One of the reasons: it introduces yet another external dependency, which is beyond the control of developers. At one point the stk library would not even compile on OSX.
On 23 Feb 2013, at 00:15, Louis Cohen wrote:

> 
> On Fri, Feb 22, 2013 at 3:25 PM, Justin Smith  wrote:
>> except there are valid reasons to want to build and distribute csound without those opcodes.
> 
> I'm curious: why would anyone want to distribute csound without these opcodes? I cannot imagine any advantages.
> 
> 
> Lou Cohen
> www.jolc.net
> www.opensound.org
> 
> 
> 
> 
> 
> 
> 
> 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"
> 

Dr Victor Lazzarini
Senior Lecturer
Dept. of Music
NUI Maynooth Ireland
tel.: +353 1 708 3545
Victor dot Lazzarini AT nuim dot ie

That being the case, it seems to me that the STK opcodes are only available to a very small portion of the csound user base - those who have the skills to build csound in customized ways. What a shame! The opcodes appear to represent much value and yet they are out of reach to many users, perhaps the majority of users.

BTW, just what IS the external dependency?

-Lou

On Feb 22, 2013, at 7:25 PM, Victor Lazzarini  wrote:

> One of the reasons: it introduces yet another external dependency, which is beyond the control of developers. At one point the stk library would not even compile on OSX.
> On 23 Feb 2013, at 00:15, Louis Cohen wrote:
> 
>> 
>> On Fri, Feb 22, 2013 at 3:25 PM, Justin Smith  wrote:
>>> except there are valid reasons to want to build and distribute csound without those opcodes.
>> 
>> I'm curious: why would anyone want to distribute csound without these opcodes? I cannot imagine any advantages.
>> 
>> 
>> Lou Cohen
>> www.jolc.net
>> www.opensound.org
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 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"
>> 
> 
> Dr Victor Lazzarini
> Senior Lecturer
> Dept. of Music
> NUI Maynooth Ireland
> tel.: +353 1 708 3545
> Victor dot Lazzarini AT nuim dot ie
> 
> 
> 
> 
> 
> 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"
> 

Lou Cohen
www.jolc.net
www.opensound.org

I am responsible for getting the the information STK opcodes in the manual. 
And you are right, the value range for the controllers are not indicated. I
will do some testing, but they are either 0=127 or 1-128 (midi-like values).
When i know for sure, i will add this to the manual pages.



--
View this message in context: http://csound.1045644.n5.nabble.com/STK-opcodes-tp5720232p5720391.html
Sent from the Csound - General mailing list archive at Nabble.com.

+1 Aure! (I only just caught up on this conversation today).

On 2/24/13, Aurelius Prochazka  wrote:
> I guess that is bothersome right there.  These are physical models yet the
> parameters are dimensionless MIDI integers.  Yuck.  The physics of the
> physical models should be exposed to the programmer, or else it is a black
> box.  IMHO, not up to snuff for Csound.
>
> Aure
>
>
> Sent with Sparrow (http://www.sparrowmailapp.com/?sig)
>
>
> On Sunday, February 24, 2013 at 9:54 AM, menno wrote:
>
>> I am responsible for getting the the information STK opcodes in the
>> manual.
>> And you are right, the value range for the controllers are not indicated.
>> I
>> will do some testing, but they are either 0=127 or 1-128 (midi-like
>> values).
>> When i know for sure, i will add this to the manual pages.
>>
>>
>>
>> --
>> View this message in context:
>> http://csound.1045644.n5.nabble.com/STK-opcodes-tp5720232p5720391.html
>> Sent from the Csound - General mailing list archive at Nabble.com
>> (http://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
>> (mailto:sympa@lists.bath.ac.uk) with body "unsubscribe csound"
>>
>>
>
>
>
> 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"
>
>

yes, now that i see these manual pages again again, i agree.

What happened at the time was, that I wanted to have the STK opcodes in the
manual. I saw them being used in CsoundVST, i heard them, liked them,  but
there were no manual pages at all. 

Looking back i see that these manual pages do not have the same format as
other opcodes - so i will redo them.



--
View this message in context: http://csound.1045644.n5.nabble.com/STK-opcodes-tp5720232p5720405.html
Sent from the Csound - General mailing list archive at Nabble.com.

Hi all,

i did an (extreme?) makeover of the manual pages of the STKopcodes and hope
this time the information is complete.
The STKopcodes *are* not like the other Csound opcodes in some ways, but i
have tried to make the manual pages as standard as possible.

It's in Git now, but if you want to see them right now you can upload the
manual here:
http://members.home.nl/mag.knevel/csound_betamanual/manual_spring2013.zip





--
View this message in context: http://csound.1045644.n5.nabble.com/STK-opcodes-tp5720232p5720830.html
Sent from the Csound - General mailing list archive at Nabble.com.