I think the new parser is now functional and a number of bugs have
been fixed etc.  I realise that the last release took a long time to
get out, but things are moving on.  5.12 was tagged on 17 January this year
==John ffitch

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

I think we should have a new release when and only when:

-- The ParCS code runs pieces old and new. I am prepared to work on this.
-- The new parser runs pieces old and new.
-- There are default values of all environment variables so that
Csound will install in the user's home directory out of a zip file. I
am planning to do this.
-- There a command-line option and an opcode for Csound to run
indefinitely (i.e. until explicitly turned off). I am planning to do
this.
-- The QuteCsound goodies promised have been delivered (standalones,
Python widgets).

Given the magnitude of the first two deliverables, there should be a
real beta testing release.

I have other ideas for new features that may or may not get done soon
enough and may or may not make sense:

-- Compile Faust code that is embedded in the csd file into plugin opcodes.
-- Port VST related code (CsoundVST and vst4cs) from the Steinberg VST
SDK to the open source VeSTige. This only makes sense if it is OK with
SourceForge. I will ask them.
-- Add Common Music to QuteCsound.

I really like the idea of adding Common Music to QuteCsound. This
would be like Grace, only much easier to actually use. Best of all,
the fact the QuteCsound uses the Csound API for audio output means
that QuteCsound could combine audio streams from both Csound and
sndlib in the same performance.

Regards,
Mike


On Tue, Sep 21, 2010 at 12:39 PM, john ffitch  wrote:
> I think the new parser is now functional and a number of bugs have
> been fixed etc.  I realise that the last release took a long time to
> get out, but things are moving on.  5.12 was tagged on 17 January this year
> ==John ffitch
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



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

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Michael, I think your milestone list is way too long. It also
excessively ties the csound release schedule with qutecsound's, which
may not be desirable.
As for running out of a zip file extracted in the home directory, please
don't break the possibility we distributors have in setting the system
defaults.

On 09/27/2010 08:25 AM, Michael Gogins wrote:
> I think we should have a new release when and only when:
> 
> -- The ParCS code runs pieces old and new. I am prepared to work on this.
> -- The new parser runs pieces old and new.
> -- There are default values of all environment variables so that
> Csound will install in the user's home directory out of a zip file. I
> am planning to do this.
> -- There a command-line option and an opcode for Csound to run
> indefinitely (i.e. until explicitly turned off). I am planning to do
> this.
> -- The QuteCsound goodies promised have been delivered (standalones,
> Python widgets).
> 
> Given the magnitude of the first two deliverables, there should be a
> real beta testing release.
> 
> I have other ideas for new features that may or may not get done soon
> enough and may or may not make sense:
> 
> -- Compile Faust code that is embedded in the csd file into plugin opcodes.
> -- Port VST related code (CsoundVST and vst4cs) from the Steinberg VST
> SDK to the open source VeSTige. This only makes sense if it is OK with
> SourceForge. I will ask them.
> -- Add Common Music to QuteCsound.
> 
> I really like the idea of adding Common Music to QuteCsound. This
> would be like Grace, only much easier to actually use. Best of all,
> the fact the QuteCsound uses the Csound API for audio output means
> that QuteCsound could combine audio streams from both Csound and
> sndlib in the same performance.
> 
> Regards,
> Mike
> 
> 
> On Tue, Sep 21, 2010 at 12:39 PM, john ffitch  wrote:
>> I think the new parser is now functional and a number of bugs have
>> been fixed etc.  I realise that the last release took a long time to
>> get out, but things are moving on.  5.12 was tagged on 17 January this year
>> ==John ffitch
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
> 
> 
> 


-- 
Saludos,
Felipe Sateler

How do you set the system defaults? I would not want to overwrite
that. My thought was that Csound would set its own values for
environment variables, then override them from the .csounrc, actual
user-set or system-defined environment variables, and so on. The
default values would be the typical installation locations, but
relative to Csound's bin directory.

Regards,
Mike

On Mon, Sep 27, 2010 at 8:44 PM, Felipe Sateler  wrote:
> Michael, I think your milestone list is way too long. It also
> excessively ties the csound release schedule with qutecsound's, which
> may not be desirable.
> As for running out of a zip file extracted in the home directory, please
> don't break the possibility we distributors have in setting the system
> defaults.
>
> On 09/27/2010 08:25 AM, Michael Gogins wrote:
>> I think we should have a new release when and only when:
>>
>> -- The ParCS code runs pieces old and new. I am prepared to work on this.
>> -- The new parser runs pieces old and new.
>> -- There are default values of all environment variables so that
>> Csound will install in the user's home directory out of a zip file. I
>> am planning to do this.
>> -- There a command-line option and an opcode for Csound to run
>> indefinitely (i.e. until explicitly turned off). I am planning to do
>> this.
>> -- The QuteCsound goodies promised have been delivered (standalones,
>> Python widgets).
>>
>> Given the magnitude of the first two deliverables, there should be a
>> real beta testing release.
>>
>> I have other ideas for new features that may or may not get done soon
>> enough and may or may not make sense:
>>
>> -- Compile Faust code that is embedded in the csd file into plugin opcodes.
>> -- Port VST related code (CsoundVST and vst4cs) from the Steinberg VST
>> SDK to the open source VeSTige. This only makes sense if it is OK with
>> SourceForge. I will ask them.
>> -- Add Common Music to QuteCsound.
>>
>> I really like the idea of adding Common Music to QuteCsound. This
>> would be like Grace, only much easier to actually use. Best of all,
>> the fact the QuteCsound uses the Csound API for audio output means
>> that QuteCsound could combine audio streams from both Csound and
>> sndlib in the same performance.
>>
>> Regards,
>> Mike
>>
>>
>> On Tue, Sep 21, 2010 at 12:39 PM, john ffitch  wrote:
>>> I think the new parser is now functional and a number of bugs have
>>> been fixed etc.  I realise that the last release took a long time to
>>> get out, but things are moving on.  5.12 was tagged on 17 January this year
>>> ==John ffitch
>>>
>>> ------------------------------------------------------------------------------
>>> Start uncovering the many advantages of virtual appliances
>>> and start using them to simplify application deployment and
>>> accelerate your shift to cloud computing.
>>> http://p.sf.net/sfu/novell-sfdev2dev
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>
>>
>>
>>
>
>
> --
> Saludos,
> Felipe Sateler
>
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
>



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

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Csound currently respects CS_DEFAULT_PLUGINDIR definition at build time.
I'm not quite sure how that would work for relative paths, so I expect
you need to build some sort of runtime support.

On 09/27/2010 10:31 PM, Michael Gogins wrote:
> How do you set the system defaults? I would not want to overwrite
> that. My thought was that Csound would set its own values for
> environment variables, then override them from the .csounrc, actual
> user-set or system-defined environment variables, and so on. The
> default values would be the typical installation locations, but
> relative to Csound's bin directory.
> 
> Regards,
> Mike
> 
> On Mon, Sep 27, 2010 at 8:44 PM, Felipe Sateler  wrote:
>> Michael, I think your milestone list is way too long. It also
>> excessively ties the csound release schedule with qutecsound's, which
>> may not be desirable.
>> As for running out of a zip file extracted in the home directory, please
>> don't break the possibility we distributors have in setting the system
>> defaults.
>>
>> On 09/27/2010 08:25 AM, Michael Gogins wrote:
>>> I think we should have a new release when and only when:
>>>
>>> -- The ParCS code runs pieces old and new. I am prepared to work on this.
>>> -- The new parser runs pieces old and new.
>>> -- There are default values of all environment variables so that
>>> Csound will install in the user's home directory out of a zip file. I
>>> am planning to do this.
>>> -- There a command-line option and an opcode for Csound to run
>>> indefinitely (i.e. until explicitly turned off). I am planning to do
>>> this.
>>> -- The QuteCsound goodies promised have been delivered (standalones,
>>> Python widgets).
>>>
>>> Given the magnitude of the first two deliverables, there should be a
>>> real beta testing release.
>>>
>>> I have other ideas for new features that may or may not get done soon
>>> enough and may or may not make sense:
>>>
>>> -- Compile Faust code that is embedded in the csd file into plugin opcodes.
>>> -- Port VST related code (CsoundVST and vst4cs) from the Steinberg VST
>>> SDK to the open source VeSTige. This only makes sense if it is OK with
>>> SourceForge. I will ask them.
>>> -- Add Common Music to QuteCsound.
>>>
>>> I really like the idea of adding Common Music to QuteCsound. This
>>> would be like Grace, only much easier to actually use. Best of all,
>>> the fact the QuteCsound uses the Csound API for audio output means
>>> that QuteCsound could combine audio streams from both Csound and
>>> sndlib in the same performance.
>>>
>>> Regards,
>>> Mike
>>>
>>>
>>> On Tue, Sep 21, 2010 at 12:39 PM, john ffitch  wrote:
>>>> I think the new parser is now functional and a number of bugs have
>>>> been fixed etc.  I realise that the last release took a long time to
>>>> get out, but things are moving on.  5.12 was tagged on 17 January this year
>>>> ==John ffitch
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Start uncovering the many advantages of virtual appliances
>>>> and start using them to simplify application deployment and
>>>> accelerate your shift to cloud computing.
>>>> http://p.sf.net/sfu/novell-sfdev2dev
>>>> _______________________________________________
>>>> Csound-devel mailing list
>>>> Csound-devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>>>
>>>
>>>
>>>
>>
>>
>> --
>> Saludos,
>> Felipe Sateler
>>
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>>
> 
> 
> 


-- 
Saludos,
Felipe Sateler

Hello Michael,

perhaps it is too soon, but is it possible you squeeze in your TODOlist the
making of (an outline of) manual pages for the STK opcodes and extension of
the controllers to 8?
I'll do the examples.

bye,
menno
-- 
View this message in context: http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p2857253.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

It's not too much.

MKG from cell phone

On Sep 28, 2010 2:23 PM, "menno" <nabob_cd@yahoo.com> wrote:


Hello Michael,

perhaps it is too soon, but is it possible you squeeze in your TODOlist the
making of (an outline of) manual pages for the STK opcodes and extension of
the controllers to 8?
I'll do the examples.

bye,
menno
--
View this message in context: http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p2857253.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Start uncovering the...

Menno, I committed a fix to the STK opcodes upping the maximum number
of simultaneous controllers to 8. I will do the outline of the man
page next.

Thanks for the reminder,
Mike

On Tue, Sep 28, 2010 at 3:05 PM, Michael Gogins
 wrote:
> It's not too much.
>
> MKG from cell phone
>
> On Sep 28, 2010 2:23 PM, "menno"  wrote:
>
>
> Hello Michael,
>
> perhaps it is too soon, but is it possible you squeeze in your TODOlist the
> making of (an outline of) manual pages for the STK opcodes and extension of
> the controllers to 8?
> I'll do the examples.
>
> bye,
> menno
> --
> View this message in context:
> http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p2857253.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Start uncovering the...



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

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

thanks Michael,
i just rebuild Csound doubles, tested them and they work nicely!

bye,
menno
-- 
View this message in context: http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p3073229.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Thanks for your help! I should have the outline of the reference
manual page for you by Monday.

Regards,
Mike

On Fri, Oct 1, 2010 at 3:49 PM, menno  wrote:
>
> thanks Michael,
> i just rebuild Csound doubles, tested them and they work nicely!
>
> bye,
> menno
> --
> View this message in context: http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p3073229.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing.
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



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

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Here is a draft of the manual page for the STKRhodey opcode. The
others would all be very similar except for the name (of course), the
description, and the descriptions of the controller pairs. I copied
the descriptions out of the STK source code with very light editing.

Regards,
Mike

On Fri, Oct 1, 2010 at 4:29 PM, Michael Gogins  wrote:
> Thanks for your help! I should have the outline of the reference
> manual page for you by Monday.
>
> Regards,
> Mike
>
> On Fri, Oct 1, 2010 at 3:49 PM, menno  wrote:
>>
>> thanks Michael,
>> i just rebuild Csound doubles, tested them and they work nicely!
>>
>> bye,
>> menno
>> --
>> View this message in context: http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p3073229.html
>> Sent from the Csound - Dev mailing list archive at Nabble.com.
>>
>> ------------------------------------------------------------------------------
>> Start uncovering the many advantages of virtual appliances
>> and start using them to simplify application deployment and
>> accelerate your shift to cloud computing.
>> http://p.sf.net/sfu/novell-sfdev2dev
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>
>
>
> --
> Michael Gogins
> Irreducible Productions
> http://www.michael-gogins.com
> Michael dot Gogins at gmail dot com
>



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

that looks good Michael. 
I would suggest a few minor changes in the text:
- in Syntax i removed 3 of the 8 controller pairs because for this
particular STKRhodey  5 different controller pairs are of interest.
-  in this text near the end of my changed manual page you can read:
      "kc1, kv1, kc2, kv2, kc3, kv3, kc4, kv4, kc5, kv5, kc6, kv6, kc7, kv7,
kc8, kv8 -- Up to 8 optional k-rate controller pairs for the STK opcodes."
      
This should make it clear that for all STK opcodes 8 are operational, but
then the text continues:

"The controller numbers and values that work for STKRhodey are:"

and this explains the number of controller pairs that for this particular
STK opcode, = 5 controller pairs and what they do
- added range for amplitude: 0-1
- i removed my name for the example because i think it does not add relevant
information for the opcode

What do you think?


  STKRhodey
  
  
    STKRhodey
  
 
  
    STKRhodey
    
      STK Fender Rhodes-like electric piano FM synthesis instrument.
    
  
 
  
    
    
      STK Fender Rhodes-like electric piano FM synthesis instrument.
  
 
  
    
    asignal STKRhodeyifrequency, iamplitude,
[kc1, kv1[, kc2, kv2[, kc3, kv3[, kc4, kv4[, kc5, kv5]]]]]
  
 
  
    
    
      This opcode implements an instrument based on two simple FM Pairs
      summed together, also referred to as algorithm 5 of the Yamaha TX81Z.
      It simulates the sound of a Rhodes electric piano, and some related
sounds.
    
   
    
      
      
        The code for this opcode is taken directly from the Rhodey class in
the Synthesis Toolkit in C++ by Perry R. Cook and Gary P. Scavone (
http://ccrma.stanford.edu/software/stk
http://ccrma.stanford.edu/software/stk ).
      
    
  
 
  
    
    
      ifrequency -- Frequency of note played, in Hertz.
    
   
    
      iamplitude -- Amplitude of note played (0-1).
    
   
    
      kc1, kv1, kc2, kv2, kc3, kv3, kc4, kv4, kc5, kv5, kc6, kv6,
kc7, kv7, kc8, kv8 -- Up to 8 optional k-rate controller pairs
for the STK opcodes.
      Each controller pair consists of a controller number (kc) followed by
a controller value (kv). The controller numbers and values that work for
STKRhodey are:
      
        kc, kv -- 2, modulator index
1.
        kc, kv -- 4, crossfade of
outputs.
        kc, kv -- 11, speed of
low-frequency oscillator.
        kc, kv -- 1, depth of
low-frequency oscillator.
        kc, kv -- 128, ADSR 2 and 4
target.
      
    
  
 
  
    
    
      Here is an example of the STKRhodey opcode. It uses the file STKRhodey.csd,
and fwavblnk.aiff.
     
      
        
        
      
    
  
 
  
    
    
      STKWurley,
    
  
 
  
    
    
      
        Author: &namemichael; (after &nameperry;)
        Irreducible Productions
        New York, NY
      
    
    New in Csound version 5.11
  



-- 
View this message in context: http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p3194704.html
Sent from the Csound - Dev mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Looks good to me, thanks.

Regards,
Mike

On Mon, Oct 4, 2010 at 2:32 PM, menno  wrote:
>
> that looks good Michael.
> I would suggest a few minor changes in the text:
> - in Syntax i removed 3 of the 8 controller pairs because for this
> particular STKRhodey  5 different controller pairs are of interest.
> -  in this text near the end of my changed manual page you can read:
>      "kc1, kv1, kc2, kv2, kc3, kv3, kc4, kv4, kc5, kv5, kc6, kv6, kc7, kv7,
> kc8, kv8 -- Up to 8 optional k-rate controller pairs for the STK opcodes."
>
> This should make it clear that for all STK opcodes 8 are operational, but
> then the text continues:
>
> "The controller numbers and values that work for STKRhodey are:"
>
> and this explains the number of controller pairs that for this particular
> STK opcode, = 5 controller pairs and what they do
> - added range for amplitude: 0-1
> - i removed my name for the example because i think it does not add relevant
> information for the opcode
>
> What do you think?
>
> 
>  STKRhodey
>  
>  
>    STKRhodey
>  
>
>  
>    STKRhodey
>    
>      STK Fender Rhodes-like electric piano FM synthesis instrument.
>    
>  
>
>  
>    
>    
>      STK Fender Rhodes-like electric piano FM synthesis instrument.
>  
>
>  
>    
>    asignal STKRhodeyifrequency, iamplitude,
> [kc1, kv1[, kc2, kv2[, kc3, kv3[, kc4, kv4[, kc5, kv5]]]]]
>  
>
>  
>    
>    
>      This opcode implements an instrument based on two simple FM Pairs
>      summed together, also referred to as algorithm 5 of the Yamaha TX81Z.
>      It simulates the sound of a Rhodes electric piano, and some related
> sounds.
>    
>
>    
>      
>      
>        The code for this opcode is taken directly from the Rhodey class in
> the Synthesis Toolkit in C++ by Perry R. Cook and Gary P. Scavone (
> http://ccrma.stanford.edu/software/stk
> http://ccrma.stanford.edu/software/stk ).
>      
>    
>  
>
>  
>    
>    
>      ifrequency -- Frequency of note played, in Hertz.
>    
>
>    
>      iamplitude -- Amplitude of note played (0-1).
>    
>
>    
>      kc1, kv1, kc2, kv2, kc3, kv3, kc4, kv4, kc5, kv5, kc6, kv6,
> kc7, kv7, kc8, kv8 -- Up to 8 optional k-rate controller pairs
> for the STK opcodes.
>      Each controller pair consists of a controller number (kc) followed by
> a controller value (kv). The controller numbers and values that work for
> STKRhodey are:
>      
>        kc, kv -- 2, modulator index
> 1.
>        kc, kv -- 4, crossfade of
> outputs.
>        kc, kv -- 11, speed of
> low-frequency oscillator.
>        kc, kv -- 1, depth of
> low-frequency oscillator.
>        kc, kv -- 128, ADSR 2 and 4
> target.
>      
>    
>  
>
>  
>    
>    
>      Here is an example of the STKRhodey opcode. It uses the file  url="examples/STKRhodey.csd">STKRhodey.csd,
> and  url="examples/fwavblnk.aiff">fwavblnk.aiff.
>
>      
>        
>         xmlns:xi="http://www.w3.org/2001/XInclude"/>
>      
>    
>  
>
>  
>    
>    
>      STKWurley,
>    
>  
>
>  
>    
>    
>      
>        Author: &namemichael; (after &nameperry;)
>        Irreducible Productions
>        New York, NY
>      
>    
>    New in Csound version 5.11
>  
> 
>
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/When-should-we-have-the-next-release-tp2854817p3194704.html
> Sent from the Csound - Dev mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Virtualization is moving to the mainstream and overtaking non-virtualized
> environment for deploying applications. Does it make network security
> easier or more difficult to achieve? Read this whitepaper to separate the
> two and get a better understanding.
> http://p.sf.net/sfu/hp-phase2-d2d
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>



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

------------------------------------------------------------------------------
Virtualization is moving to the mainstream and overtaking non-virtualized
environment for deploying applications. Does it make network security 
easier or more difficult to achieve? Read this whitepaper to separate the 
two and get a better understanding.
http://p.sf.net/sfu/hp-phase2-d2d
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net