Dear all,

Could anyone suggest any work around for ftmorf's limitation that
interpolation only takes place when the morph value changes? This
makes sense (as we don't want the opcode to calculate interpolated
values on every k-rate period) but it would be nice if there was a way
to trigger the opcode to interpolate without changing the value at any
time. I am writing table values dynamically and this is proving
difficult.

Best,

Peiman


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've run across the same issue, and solved it by using a k-rate flag
that will reinitialize ftmorf whenever the flag is nonzero.
So, when I change the table contents, I also set this flag to a nonzero value.
excerpt of code below

Oeyvind

****** instr N ******
forceUpdate:
	ftmorf		kMorph, iMorphTab, imaskTableNum
rireturn

	kforceUpdate	chnget	"maskTableForceUpdate"
	if kforceUpdate	== 0 goto end
	reinit forceUpdate
end:
endin

****** another instr, called to set a table value (p3=1, or shorter if
you like) ******

	tableiw	ival, index, giTable

; force update table morf function
	kforceUpdate	metro	0.1
			chnset	kforceUpdate, "maskTableForceUpdate"
endin



2011/2/8 peiman khosravi :
> Dear all,
>
> Could anyone suggest any work around for ftmorf's limitation that
> interpolation only takes place when the morph value changes? This
> makes sense (as we don't want the opcode to calculate interpolated
> values on every k-rate period) but it would be nice if there was a way
> to trigger the opcode to interpolate without changing the value at any
> time. I am writing table values dynamically and this is proving
> difficult.
>
> Best,
>
> Peiman
>
>
> 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 see. That's very clever.

Thanks very much Oeyvind.

Best,

Peiman

On 9 February 2011 08:35, Oeyvind Brandtsegg  wrote:
> I've run across the same issue, and solved it by using a k-rate flag
> that will reinitialize ftmorf whenever the flag is nonzero.
> So, when I change the table contents, I also set this flag to a nonzero value.
> excerpt of code below
>
> Oeyvind
>
> ****** instr N ******
> forceUpdate:
>        ftmorf          kMorph, iMorphTab, imaskTableNum
> rireturn
>
>        kforceUpdate    chnget  "maskTableForceUpdate"
>        if kforceUpdate == 0 goto end
>        reinit forceUpdate
> end:
> endin
>
> ****** another instr, called to set a table value (p3=1, or shorter if
> you like) ******
>
>        tableiw ival, index, giTable
>
> ; force update table morf function
>        kforceUpdate    metro   0.1
>                        chnset  kforceUpdate, "maskTableForceUpdate"
> endin
>
>
>
> 2011/2/8 peiman khosravi :
>> Dear all,
>>
>> Could anyone suggest any work around for ftmorf's limitation that
>> interpolation only takes place when the morph value changes? This
>> makes sense (as we don't want the opcode to calculate interpolated
>> values on every k-rate period) but it would be nice if there was a way
>> to trigger the opcode to interpolate without changing the value at any
>> time. I am writing table values dynamically and this is proving
>> difficult.
>>
>> Best,
>>
>> Peiman
>>
>>
>> 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"