Unable to send rate multiplier to rate~ using send~ — possible bug?
Here's a patch demonstrating the issue
When I run this I'm getting no output from the rate~ connected using send~. Does anyone know of a reason for this?
Max 6.08
Windows 7
[attachment=217139,5153]
Attachments:
Probably "rate" has a special meaning as receive symbol. Using other name (eg "rate1") solves the problem (here).
Thank for the reply. That's really good to know, but actually in the patch I was using the dens is called rateA so I've slightly confused the issue I'm afraid. By clearing up that this should work you've definitely helped – I just discovered the problem is that I was (I think) inadvertently sending rate~ some 0 signals. I'm adjusting it with techno~ and although it should only be sending signals between 1-12 it seems not to be the case as I get -1.IND if the connection is probed (see pic). I don't totally understand it, but [clip~ 1. 12.] before the rate~ multiplier seems to fix the issue.
[attachment=217240,5156]
Attachments:
The issue has something to do with how dsp chain is created. Give any random name to your s~/r~ pair and restart DSP – the issue occurs. I think it's related to some internals of rate~ object or how DSP chain is optimized. Definitely "patch smell".
[attachment=217243,5158]
Attachments:
Yeah, my clip~ fix has fallen apart. The ramp out of rate~ seems to temporarily go below 0 at times. odd.