Unable to send rate multiplier to rate~ using send~ — possible bug?

Mar 9, 2013 at 9:00am

Unable to send rate multiplier to rate~ using send~ — possible bug?

Here's a patch demonstrating the issue

– Pasted Max Patch, click to expand. –

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:
  1. RateIssue.jpg
#66977
Mar 9, 2013 at 11:43pm

Probably “rate” has a special meaning as receive symbol. Using other name (eg “rate1″) solves the problem (here).

#241065
Mar 10, 2013 at 10:34am

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:
  1. ratecrop.jpg
#241066
Mar 10, 2013 at 12:45pm

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”.

– Pasted Max Patch, click to expand. –

[attachment=217243,5158]

Attachments:
  1. Zrzutekranu20130310o13.32.57.png
#241067
Mar 10, 2013 at 1:40pm

Yeah, my clip~ fix has fallen apart. The ramp out of rate~ seems to temporarily go below 0 at times. odd.

#241068

You must be logged in to reply to this topic.