User Details
| Username: |
jonesdaadi |
| Website: |
None provided |
| Facebook: |
None provided |
| Twitter: |
None provided |
| Soundcloud: |
None provided |
| Account Status: |
enabled |
| Member since: |
Jun 25 2015 |
| About jonesdaadi: |
|
| (report this profile) |
|
Devices by jonesdaadi
Total Downloads: 573
Comments by jonesdaadi
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.
What i did to get the hardware to control the device (i'll admit this is a cheapo workaround, due to my inexperience with max4live patching), was use the internal live midi mapping to map each hardware slider to the sliders in the max4live device. this way, the remote will both act as a control from inside live (for example if you wanted to connect an LFO to one channel's tone knob so that the parameter would be automated on the hardware), and it will act as a receiver which will update the max4livedevice (and its associated automation) as you use the hardware. this then enables you to record automation for the hardware as you interact with the knobs and sliders on the MX-1. once you map this, you should save those settings as a preset and always load up the preset version of the device.
perhaps in the future i will be able to implement something more elegant like the way its done here: http://www.maxforlive.com/library/device/2512/aira-system-1 The "in control" feature works great and if i could figure out how to do it, i would do the same for this device.