-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mapper ramp above 0 breaks mapping #1017
Comments
Also tested on latest nightly build, problem seems to persist. |
The ramp function of j.parameter only works for objects that have their @type attribute set to decimal, integer or array. In my testing, if I send values to a j.parameter with another @type (or no @type specified), I get the raw values from the input with "ramp [rampValue]" appended to the end of the message. Here's a test patch - try using /mouse/position/x as input, and route the output to the various j.parameter objects within the patch (they're all under /Untitled in the mapper).
|
With Mapper, setting a ramp value above 0 breaks the mapping. In my tests no values are outputted by Mapper with a ramp value above 0, across all function types.
Tested on OSX10.10.5, Max 7.3.1, Jamoma 1.0.1, mapper.module.
The text was updated successfully, but these errors were encountered: