It seems odd to me that min() and max() only operate at k and a-rate.
Is there a good method for doing this at i-rate?

Awesome!  Fresh build, and it seems to work using the opcode method:
itest max itest, 100

However I will mention for consistency that the function/macro method
doesn't seem to work:
itest = max(itest,100)

On Thu, Aug 21, 2014 at 6:09 AM,   wrote:
>
> Quoting Kevin Welsh :
>
>> It seems odd to me that min() and max() only operate at k and a-rate.
>
>
> No one had asked for it!  Code written now
>
>> Is there a good method for doing this at i-rate?
>
>
> Pull latest code fro git?
> ==John
>
>
>>
>> Send bugs reports to
>>         https://github.com/csound/csound/issues
>> 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
>        https://github.com/csound/csound/issues
> Discussions of bugs and features can be posted here
> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe
> csound"
>
>
>

Did this change regress?  I built fresh this morning to test the new
ftgenonce changes, I have now started receiving the error:
error:  Unable to find opcode entry for 'max' with matching argument types:
Found: i max ic

I also tested it with two i-rate vars instead of one constant, and
that didn't work either.

I'm seeing another possible bug/regression that I can't quite put my
finger on yet.  Is there a good/recommended way to A:B test with
multiple csound versions so I can compare?  Or is my best bet
installing the binaries to test, then rebuilding the dev branch when
I'm done testing the release version?


On Thu, Aug 21, 2014 at 5:08 AM, Kevin Welsh  wrote:
> It seems odd to me that min() and max() only operate at k and a-rate.
> Is there a good method for doing this at i-rate?

And the other regression I am hearing is found.  pset no longer seems
to be working with negative values.

I'm still curious what others do to test multiple versions... I lucked
out finding this regression quickly ;)

On Thu, Aug 28, 2014 at 1:35 PM, Kevin Welsh  wrote:
> Did this change regress?  I built fresh this morning to test the new
> ftgenonce changes, I have now started receiving the error:
> error:  Unable to find opcode entry for 'max' with matching argument types:
> Found: i max ic
>
> I also tested it with two i-rate vars instead of one constant, and
> that didn't work either.
>
> I'm seeing another possible bug/regression that I can't quite put my
> finger on yet.  Is there a good/recommended way to A:B test with
> multiple csound versions so I can compare?  Or is my best bet
> installing the binaries to test, then rebuilding the dev branch when
> I'm done testing the release version?
>
>
> On Thu, Aug 21, 2014 at 5:08 AM, Kevin Welsh  wrote:
>> It seems odd to me that min() and max() only operate at k and a-rate.
>> Is there a good method for doing this at i-rate?