I think such control events are a good idea. It might be also be a good idea 
to address them either to all instances of an instrument, or to any 
individual instance or range of instances, using Csound's existing 
fractional instr number.

Regards,
Mike

----- Original Message ----- 
From: "Anthony Kozar" 
To: "New Csound Developer list" 
Sent: Saturday, February 07, 2009 8:35 PM
Subject: Re: [Cs-dev] some ideas for Csound 6


>I suppose the SAOL control events might seem limited, but from the
> perspective that you can change any variable in an instrument without
> preparing the instrument for such control, they are quite flexible over
> Csound.  In practice, such tweaking may not be useful without some
> forethought since most parameter changes need to be continuous to avoid
> clicks.  But still, it is a simple matter to ensure continuity with a
> portamento opcode.
>
> Anyways, a more flexible facility would be fine too.  Even if the Csound
> score language is not augmented to support it, if the Csound engine can
> support the SAOL-like control feature (or more), then it will be possible 
> to
> have a SAOL language interpreter with Csound as the back end.
>
> I have been combing through old musings on Csound 6, and here are some
> additional ideas that have been proposed:
>
> 1. convert Csound core to C++
> 2. sample accurate scheduling
> 3. allow a "full directed acyclical DSP graph", in place of instrument
>   list/opcode list type graph.
> 4. remove the distinction between instruments and UDOs
> 5. flexible output routing for instruments without using globals, buses, 
> zak
> 6. orch opcodes as arguments to score statements:
>
>    instr 1
>        asig oscil p4, p5, 1
>             out   asig
>    endin
>
>    i1 0 2 7500 440.0
>    i1 1 1 [[line 0, p3, 7500]]  [[kp5 expon 330.0, p3, 220.0]]
>
>
> The last of these would be another way of achieving more score control 
> over
> instruments without preparation.  No. 3 from this list would probably 
> enable
> Nos. 4, 5, and 6.  It might be difficult to both implement these 
> suggestions
> in an elegant way and maintain backwards compatibility with the existing
> orchestra and score languages.  In that case, I think as long as the 
> engine
> supports modifying individual instances of instruments (and Michael's
> concept in #3), then we could provide two parallel options in Csound 6: 
> 1)
> the traditional orc/sco model, and 2) a new language that blends synthesis
> and event control with greater flexibility than the traditional model and
> hopefully none of its baggage.
>
> I'm sure all of this is vague -- I'd be happy to elaborate :)
>
> Anthony
>
> Steven Yi wrote on 2/7/09 3:20 PM:
>
>> If I understand correctly, SAOL control events seem very limited in
>> that they only change the value discretely.  I saw no option to slowly
>> change over time linearly or with any other curve.  If we did
>> implement something in csound this way, I would say we would need some
>> method to change the value over time, but likely that would lead to
>> just doing what blue does and having an instrument to do that work.
>> One thing blue has to do is generate an instrument for every variable
>> as it has to get compiled down that way; this might be a case for
>> having the variables names maintained so that variables can be queried
>> by name, so that a single instrument could be used for any number of
>> variables.
>
>
> ------------------------------------------------------------------------------
> Create and Deploy Rich Internet Apps outside the browser with 
> Adobe(R)AIR(TM)
> software. With Adobe AIR, Ajax developers can use existing skills and code 
> to
> build responsive, highly engaging applications that combine the power of 
> local
> resources and data with the reach of the web. Download the Adobe AIR SDK 
> and
> Ajax docs to start building applications 
> today-http://p.sf.net/sfu/adobe-com
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
> 


------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Good.  I'm glad that you like the idea and your suggestions for broadening
it sound good to me.

Anthony

michael.gogins@gmail.com wrote on 2/7/09 9:58 PM:

> I think such control events are a good idea. It might be also be a good idea
> to address them either to all instances of an instrument, or to any
> individual instance or range of instances, using Csound's existing
> fractional instr number.


------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net