User Details
Username: |
RutterStudios |
Website: |
None provided |
Facebook: |
None provided |
Twitter: |
twitter.com/NSGoat |
Soundcloud: |
None provided |
Account Status: |
enabled |
Member since: |
Jan 07 2018 |
About RutterStudios: |
|
(report this profile) |
|
Devices by RutterStudios
Total Downloads: 5,076
Comments by RutterStudios
Comments
This website uses cookies.
Clicking “Accept” means you consent to your data being processed and you’ll let us use cookies and other technologies to process your personal information to personalize and enhance your experience.
Click “Close” to deny consent and continue with technically required cookies that are essential for the website to function.
Yes this is a bug I'm sad to say. I am not am not able to figure out what is causing this. I have tried to fix this and the .amxd issue in the description but have sadly had no success. I must admit, I am not a Max-Ninja at all. I merely wanted to crossfade between two reverbs on an aux channel with a custom curve, but got a little carried away when I delved into M4L.
The mapping part is all pulled straight from MultiMap. I think it is something in the MultiMapPro/M4L.MapButtonMultiSingle/Mapping/getParamInfo sub-patch.
If anyone has fixed or knows how to fix this, or the other bug mentioned in the description, please fire me a Tweet @NSGoat.