how do you convert a irate to a krate?
if i was doing a effects in cabbage i cant have irates and i would get error
and things would not work

instr 1
ain inch 1
aout comb ain, krvt, ilpt
out aout
endin

--
View this message in context: http://csound.1045644.n5.nabble.com/irate-to-krate-tp5706101.html
Sent from the Csound - General mailing list archive at Nabble.com.

If you are trying to convert the ilpt parameter of comb to krate it's
not possible. It's i-rate only. You can cast it to k rate using
k(ilpt) but you still won't be able to change it in real time. If you
want to change the loop time of your comb filters during run time then
use vcomb.

Rory.

Hi,

This might make things clearer:

http://www.csounds.com/journal/issue10/CsoundRates.html

Cheers,
Andrés

On Sat, May 12, 2012 at 3:21 AM, Rory Walsh  wrote:
> If you are trying to convert the ilpt parameter of comb to krate it's
> not possible. It's i-rate only. You can cast it to k rate using
> k(ilpt) but you still won't be able to change it in real time. If you
> want to change the loop time of your comb filters during run time then
> use vcomb.
>
> Rory.
>
>
> 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 often find I have k-rate variables that need to be i-rate. I have a  
method for converting k-rate to i-rate that generally works for me:

1. I compute the values of any k-rate variables. I do this in a one- 
time only section of code in instr 1.

2. I then invoke instr 2 and pass it all the parameters it needs. When  
these parameters arrive in instr 2, they can be cast as i-rate or k- 
rate as needed.

EXAMPLE:
	
instr 1
ktrig init 1 ;ensures code enclosed by "if/endif" will be executed
if(ktrig==1) then
	k1 = 
	k2 = 
	;start up instrument 2, right now, with duration assigned to instr 1
	event "i", 2, 0, p3, k1, k2
	ktrig = 0 ; ensures code enclosed by "if/endif" won't be executed  
again.
	turnoff ;turn instr 1 off
endif
endin

instr 2
	ivar1 = p4 ;p4 was k1 in instr 1
	ivar2 = p5 ;p5 was k2 in instr 1
	kenv linen 1, ivar1, p3, ivar2 ;example of using k-rate variables  
where i-rate is required
	.... more code
endin

-Lou

On May 12, 2012, at 2:50 AM, Andres Cabrera wrote:

> Hi,
>
> This might make things clearer:
>
> http://www.csounds.com/journal/issue10/CsoundRates.html
>
> Cheers,
> Andrés
>
> On Sat, May 12, 2012 at 3:21 AM, Rory Walsh  wrote:
>> If you are trying to convert the ilpt parameter of comb to krate it's
>> not possible. It's i-rate only. You can cast it to k rate using
>> k(ilpt) but you still won't be able to change it in real time. If you
>> want to change the loop time of your comb filters during run time  
>> then
>> use vcomb.
>>
>> Rory.
>>
>>
>> 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 really dont understand your example Louis Cohen
so i can send and signal every sample to the irate?
Will it be smooth?

--
View this message in context: http://csound.1045644.n5.nabble.com/irate-to-krate-tp5706101p5707951.html
Sent from the Csound - General mailing list archive at Nabble.com.

As Rory said, you need to use vcomb - that parameter on comb cannot change mid note.

As to what Louis' instrument was doing:
The main thing in his instrument is the event opcode, which starts a new instrument. This is one of the only ways to set an i rate parameter from a k rate value (another option would be to set a global value from one instrument and then load it from another, or store the value in a table from one instrument and read it on instrument init in another). At init time, when an i rate parameter is set, no k-rate parameters yet exist in its instrument.

The i stands for initialization. An i rate variable never changes: it is set only once, at the start of a note. To change an irate parameter you need to start a different note, or crossfade between different opcodes with different irate parameters, or use an opcode that can do the same thing with k rate rather than i rate parameters

On 05/12/2012 10:12 PM, Shawn56 wrote:
> i really dont understand your example Louis Cohen
> so i can send and signal every sample to the irate?
> Will it be smooth?
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/irate-to-krate-tp5706101p5707951.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"
>
>

Shawn,

As a few others have mentioned, the difference between irate variables  
and other variables is that irate variables are given values when an  
instrument is initialized -- BEFORE it makes any sound. The irate  
values cannot be changed after that, they remain constant for duration  
of the instrument.

Some opcodes have parameters that must be irate variables. Other  
opcodes have parameters that could be irate or krate or arate. You  
asked originally how to convert irate to krate. Since krate variables  
are allowed to change values every k-cycle, you cannot use a krate  
variable in place of an irate variable.

In the case of your example, "comb", this opcode requires that ilpt  
(an irate variable) must be set at the instrument's initialization  
time and cannot change during the execution of the instrument.

If you want it to change while the sound is being played, you'll have  
to use one of the solutions mentioned in other emails, for example  
play two copies of the same instrument at the same time. One  
instrument could have ilpt at one (constant) value, the other  
instrument could have ilpt at another (constant) value. Then cross- 
fade between them, by changing the amplitude of ares at krate (as in  
ares = kamplitude*ares).

I'm not sure what you mean by "send and signal every sample at the  
irate", but maybe my comments above will help to clarify what you can  
do and what you can't.

In my example, I assumed that you wanted to compute the value ilpt  
with computations involving krate variables, so I gave an example of  
how to do that. In that example, the computations are done at krate in  
one instrument. Then that instrument causes another instrument to  
execute, and passes it the results of its computations. When the other  
instrument starts up, the passed parameters will be irate variables.

But it doesn't change the main issue, an irate variable cannot change  
value during the execution of an instrument.

I hope this helps.

-Lou


On May 13, 2012, at 1:12 AM, Shawn56 wrote:

> i really dont understand your example Louis Cohen
> so i can send and signal every sample to the irate?
> Will it be smooth?
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/irate-to-krate-tp5706101p5707951.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"
>

> The irate  
> values cannot be changed after that, they remain constant for duration  
> of the instrument. 

To be slightly more rigorous, they remain constant for the duration of a
given instrument _event_. I know that's what you meant, I'm just being picky
because, well, it makes a difference.

--
View this message in context: http://csound.1045644.n5.nabble.com/irate-to-krate-tp5706101p5708272.html
Sent from the Csound - General mailing list archive at Nabble.com.

Absolutely correct. In fact, there's plenty about irate vs krate that  
has mystified me and still does. So what I wrote was my personal model  
of how irate works. This model doesn't usually mess me up.

In particular, I have never understood what kvar = k(ivar) means nor  
when I might want to use it. All I know is that I don't miss it.

I do my best...

-Lou


On May 13, 2012, at 12:25 PM, Jim Aikin wrote:

>> The irate
>> values cannot be changed after that, they remain constant for  
>> duration
>> of the instrument.
>
> To be slightly more rigorous, they remain constant for the duration  
> of a
> given instrument _event_. I know that's what you meant, I'm just  
> being picky
> because, well, it makes a difference.
>
> --
> View this message in context: http://csound.1045644.n5.nabble.com/irate-to-krate-tp5706101p5708272.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"
>