On Monday 13 March 2006 20:28, Victor Lazzarini wrote:

> When running an orchestra prepared for 4.23, I kept
> getting these errors with audio rate tablew. It seems that
> csound 4 allowed for any rates for the index to tablew,
> whereas
> csound 5 is only allowing audio rate indexes. I thought
> that perhaps they should be compatible so that older
> orchestras do not get broken. Worth checking before
> the 5.01 release.

Do you mean writing an audio signal to a control rate index ?
That would not work as there is no code written for that case;
it may be that 4.xx still allowed to do so, but then the results
could be unpredictable and possibly include memory access errors.
It is actually an intentional bug fix that the table opcodes
require the signal and the index to agree in rate, to avoid the
above mentioned undefined behavior.


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net