Hello everyone,
I am trying to figure out how I can change parameters of a pad 
instrument using i statement, without re-initiating the note in 
progress. Here is what I got so far:


gisine	ftgen	1, 0, 4096, 10, 1

instr 1
kaenv	madsr	5, 0, 1, 3
ifrq	=		cpspch(8.00)
asig	foscil	ampdbfs(-12)*kaenv, ifrq, 1, p4, 1, 1
out		asig
endin



t 0 120
i1.1	0	-1	0
i1.1	2	1	1
i1.1	^+1	.	<
i1.1	^+1	.	<
i1.1	^+1	.	<
i1.1	^+1	.	<
i1.1	^+1	.	<
i1.1	^+1	.	<
i1.1	^+1	.	15
e


I need a slow attack and sustaining pad, but it seems that envelope 
opcode with i value is initialized on each i statement... Also, how 
would you interpolate the change of parameter with this? Any help or 
comments are appreciated!

Takahiko Tsuchiya


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"

Greg,
Thanks for the links, I will look up on them soon. The reason I want 
to do this is to manually sequence the change of parameters in "beats"
in score time (which is defined by t statement.) I think this, 
sequencing with i statement, would be a little more simple and 
straight foward compared to using envlpx or f-table. 

Also, according to the manual, it seems to be possible. (Please look 
just above the "Tip" in the middle.)
http://www.csounds.com/manual/html/i.html
But I just cannot make it to work...

Best,
Takahiko


Greg Schroeder  wrote:
(2010/04/13 22:09)

>(I'm a n00b, so keep that in mind)
>How can you change a k-rate or a-rate variable mid-event with an
>i-statement? I thought that was a contradiction in terms?
>
>Could you tell me why you want to do this, rather than a plain 'ole
>envelope, just for my own curiosity?
>I'd think envlpx or maybe even using an oscillator as an envelope within a
>single i-statement would give you what you're describing, and at a pretty
>infinite degree of complexity, but I'm not sure I understand what you want
>to do.
>You could also use an ftable as a step sequencer to do this, I think. (See
>Jacob Joaquin's EAST for a simple explanation)
>I'm not trying to condescend, but I personally found most of what I wanted
>in enveloping here:
>http://ecmc.rochester.edu/ecmc/docs/allan.cs/chapter2.html#
>Is the problem that you want an i-statement not to trigger a new
>pitch/envelope/etc.?
>I thought that was the whole point of an i-statement, but I very, very
>easily might be wrong.
>
>Greg
>
>
>On Wed, Apr 14, 2010 at 9:39 AM, Takahiko TSUCHIYA wrote:
>
>> Hello everyone,
>> I am trying to figure out how I can change parameters of a pad
>> instrument using i statement, without re-initiating the note in
>> progress. Here is what I got so far:
>>
>> 
>> gisine  ftgen   1, 0, 4096, 10, 1
>>
>> instr 1
>> kaenv   madsr   5, 0, 1, 3
>> ifrq    =               cpspch(8.00)
>> asig    foscil  ampdbfs(-12)*kaenv, ifrq, 1, p4, 1, 1
>> out             asig
>> endin
>>
>> 
>> 
>> t 0 120
>> i1.1    0       -1      0
>> i1.1    2       1       1
>> i1.1    ^+1     .       <
>> i1.1    ^+1     .       <
>> i1.1    ^+1     .       <
>> i1.1    ^+1     .       <
>> i1.1    ^+1     .       <
>> i1.1    ^+1     .       <
>> i1.1    ^+1     .       15
>> e
>> 
>>
>> I need a slow attack and sustaining pad, but it seems that envelope
>> opcode with i value is initialized on each i statement... Also, how
>> would you interpolate the change of parameter with this? Any help or
>> comments are appreciated!
>>
>> Takahiko Tsuchiya
>>
>>
>> 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"
>>
>>
>
>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"



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"

> I am trying to figure out how I can change parameters of a pad
> instrument using i statement, without re-initiating the note in
> progress. Here is what I got so far:

Put the parameter that you want to change in a global variable
and modify it from a second instrument:

ga_tweakable = 0

instr 1
        consume ga_tweakable
endin

instr 2
        ga_tweakable = p4
endin


Play your long note on instrument 1, and modify your
parameter periodically using instrument 2.

Tobiah


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"

Ah! That's a clever idea. Thanks Tobiah. 

Takahiko

Tobiah  wrote:
(2010/04/14 14:50)

>> I am trying to figure out how I can change parameters of a pad
>> instrument using i statement, without re-initiating the note in
>> progress. Here is what I got so far:
>
>Put the parameter that you want to change in a global variable
>and modify it from a second instrument:
>
>ga_tweakable = 0
>
>instr 1
>        consume ga_tweakable
>endin
>
>instr 2
>        ga_tweakable = p4
>endin
>
>
>Play your long note on instrument 1, and modify your
>parameter periodically using instrument 2.
>
>Tobiah
>
>
>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"



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"

Just to note, Tobiah's method is roughly what blue uses for parameter
automation in blue, though in blue it generates an instrument to
either set the value immediately or use a line opcode to gradually
change the value, depending on the kind of parameter automation it is.

I had wanted to reply earlier that you may also want to look into
using tied notes. I wrote an article a while back for the Csound
Journal:

http://www.csounds.com/journal/2005fall/tiedNotes.html

(Audio example at end should illustrate some ways to hear differences)

I tend to use tied notes a lot in conjunction with fractional
instrument numbers for notes that are going to change values for sound
mass like effects.  This allows a single instrument design to be used
in a polyphonic way with each line of the polyphony having its own
independent changing of parameters.  Other times I use blue's
automation to affect the parameters per-instrument but that is for
different types of musical material (this is more like what is
achievable in MIDI-based environments and how MIDI control data is
sent per instrument channel).  I think both are useful to know as you
can use them to achieve different types of sound results.

Hope that helps!
steven

On Wed, Apr 14, 2010 at 3:13 PM, Takahiko TSUCHIYA  wrote:
> Ah! That's a clever idea. Thanks Tobiah.
>
> Takahiko
>
> Tobiah  wrote:
> (2010/04/14 14:50)
>
>>> I am trying to figure out how I can change parameters of a pad
>>> instrument using i statement, without re-initiating the note in
>>> progress. Here is what I got so far:
>>
>>Put the parameter that you want to change in a global variable
>>and modify it from a second instrument:
>>
>>ga_tweakable = 0
>>
>>instr 1
>>        consume ga_tweakable
>>endin
>>
>>instr 2
>>        ga_tweakable = p4
>>endin
>>
>>
>>Play your long note on instrument 1, and modify your
>>parameter periodically using instrument 2.
>>
>>Tobiah
>>
>>
>>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"
>
>
>
> 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"
>
>


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"

Thank you Steven,
I think I was trying to tie notes to begin with (in my first post,)  
but having problem with the amp envelope. Your article would help me  
solve this.
Also, as you said, tie note is basically for polyphonic automation,  
while the use of global variable may be good for monophonic (per  
instrument) automation, although not necessarily.

Best,
Takahiko


On Apr 14, 2010, at 4:52 PM, Steven Yi wrote:

> Just to note, Tobiah's method is roughly what blue uses for parameter
> automation in blue, though in blue it generates an instrument to
> either set the value immediately or use a line opcode to gradually
> change the value, depending on the kind of parameter automation it is.
>
> I had wanted to reply earlier that you may also want to look into
> using tied notes. I wrote an article a while back for the Csound
> Journal:
>
> http://www.csounds.com/journal/2005fall/tiedNotes.html
>
> (Audio example at end should illustrate some ways to hear differences)
>
> I tend to use tied notes a lot in conjunction with fractional
> instrument numbers for notes that are going to change values for sound
> mass like effects.  This allows a single instrument design to be used
> in a polyphonic way with each line of the polyphony having its own
> independent changing of parameters.  Other times I use blue's
> automation to affect the parameters per-instrument but that is for
> different types of musical material (this is more like what is
> achievable in MIDI-based environments and how MIDI control data is
> sent per instrument channel).  I think both are useful to know as you
> can use them to achieve different types of sound results.
>
> Hope that helps!
> steven
>
> On Wed, Apr 14, 2010 at 3:13 PM, Takahiko TSUCHIYA  > wrote:
>> Ah! That's a clever idea. Thanks Tobiah.
>>
>> Takahiko
>>
>> Tobiah  wrote:
>> (2010/04/14 14:50)
>>
>>>> I am trying to figure out how I can change parameters of a pad
>>>> instrument using i statement, without re-initiating the note in
>>>> progress. Here is what I got so far:
>>>
>>> Put the parameter that you want to change in a global variable
>>> and modify it from a second instrument:
>>>
>>> ga_tweakable = 0
>>>
>>> instr 1
>>>        consume ga_tweakable
>>> endin
>>>
>>> instr 2
>>>        ga_tweakable = p4
>>> endin
>>>
>>>
>>> Play your long note on instrument 1, and modify your
>>> parameter periodically using instrument 2.
>>>
>>> Tobiah
>>>
>>>
>>> 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"
>>
>>
>>
>> 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"
>>
>>
>
>
> 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"
>



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, hopefully the article will help your instrument design for tied
notes. You have to take advantage of the tivalue opcode to work out
when to initialize an opcode and when not to do it.  Sometimes too you
may go ahead an initialize but with a value that is the current value
that the previous tied note had.

If you have any further problems, just post some the instrument code
and I'll be happy to assist.

steven


On Wed, Apr 14, 2010 at 6:37 PM, Takahiko Tsuchiya  wrote:
> Thank you Steven,
> I think I was trying to tie notes to begin with (in my first post,) but
> having problem with the amp envelope. Your article would help me solve this.
> Also, as you said, tie note is basically for polyphonic automation, while
> the use of global variable may be good for monophonic (per instrument)
> automation, although not necessarily.
>
> Best,
> Takahiko
>
>
> On Apr 14, 2010, at 4:52 PM, Steven Yi wrote:
>
>> Just to note, Tobiah's method is roughly what blue uses for parameter
>> automation in blue, though in blue it generates an instrument to
>> either set the value immediately or use a line opcode to gradually
>> change the value, depending on the kind of parameter automation it is.
>>
>> I had wanted to reply earlier that you may also want to look into
>> using tied notes. I wrote an article a while back for the Csound
>> Journal:
>>
>> http://www.csounds.com/journal/2005fall/tiedNotes.html
>>
>> (Audio example at end should illustrate some ways to hear differences)
>>
>> I tend to use tied notes a lot in conjunction with fractional
>> instrument numbers for notes that are going to change values for sound
>> mass like effects.  This allows a single instrument design to be used
>> in a polyphonic way with each line of the polyphony having its own
>> independent changing of parameters.  Other times I use blue's
>> automation to affect the parameters per-instrument but that is for
>> different types of musical material (this is more like what is
>> achievable in MIDI-based environments and how MIDI control data is
>> sent per instrument channel).  I think both are useful to know as you
>> can use them to achieve different types of sound results.
>>
>> Hope that helps!
>> steven
>>
>> On Wed, Apr 14, 2010 at 3:13 PM, Takahiko TSUCHIYA 
>> wrote:
>>>
>>> Ah! That's a clever idea. Thanks Tobiah.
>>>
>>> Takahiko
>>>
>>> Tobiah  wrote:
>>> (2010/04/14 14:50)
>>>
>>>>> I am trying to figure out how I can change parameters of a pad
>>>>> instrument using i statement, without re-initiating the note in
>>>>> progress. Here is what I got so far:
>>>>
>>>> Put the parameter that you want to change in a global variable
>>>> and modify it from a second instrument:
>>>>
>>>> ga_tweakable = 0
>>>>
>>>> instr 1
>>>>       consume ga_tweakable
>>>> endin
>>>>
>>>> instr 2
>>>>       ga_tweakable = p4
>>>> endin
>>>>
>>>>
>>>> Play your long note on instrument 1, and modify your
>>>> parameter periodically using instrument 2.
>>>>
>>>> Tobiah
>>>>
>>>>
>>>> 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"
>>>
>>>
>>>
>>> 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"
>>>
>>>
>>
>>
>> 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"
>>
>
>
>
> 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"
>
>


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"