Device Details

Device Overview

Name/Version: DSI PRO 2 Control 1.0
Author: techbuzz  
Description: This is the control I created to store patches created on the PRO 2 in Live. Each time the device is loaded it sends a SYSEX message to the PRO 2 to U1 P1 with the name Ableton Patch. This is that sound. The midi device receives NRPN and sends NRPN to the PRO 2.

I made a short video of the operation and how it works.


Device Details

Downloads: 144
Tags utility, hardware, push
Live Version Used: 10.0.1
Max Version Used: 8.0
Date Added: Nov 23 2018 19:35:35
Date Last Updated: Dec 15 2018 22:30:16
Average Rating -n/a-
Rate this device: (must be logged in to rate devices login)
Device Type: midi_device
URL (optional):
License (more info): None

Device Files

Device File: DSI PRO 2 Editor.amxd


Can this device capture the state of a preset? ...So I could then automate it...

Great work btw!


Thank you. Right now it will not import the patch that is loaded on the instrument. This works one way right now. The patches are stored in Ableton when you save this in a track. For it to work like you are asking I need to read the patch out of the PRO 2 and interpret this data. This could be done. That is what the sound tower VST does. There would need to be a request patch button or something like that. I write the data that is in this patch now when it is loaded into Ableton.


I currently use your devices to control Omnisphere 2.5 hardware profiles, and it works great. Can you possibly make a Moog Sub 37 ?

Hello vertibration,

I don't own a Moog Sub 37. I make these interfaces for synths I own. If you want to loan me one I will gladly make you an interface and return the synth to you. : )

Hello and thanks a lot for sharing this. The UI is really well made !!!
Unfortunately, I've got issues with your plugin as it breaks other plugin functionnality. I asked to a programmer if he can find the problem and here is his report. Just to share with you. Hope that helps ! I'll will not use this version of that plug as it is not enough efficient for my purpose but thanks again ;-)

Here are the comments from the programmer :
" the issue is within the "DSI_PRO2_NRPN_to_Sysex.js" file on line 25: "eval = array[0];" does not make sense. It's replacing the eval object with something else, which means no script will be able to use eval() anymore. Since all Max for Live devices exist in the same "universe" so to speak, they can break each other like this. To fix this, I think simply deleting that line or commenting it out should solve the problem. I could do it as well and send you a modified version of the device, but I'm not sure if I'm allowed as it's not my work that I would be sharing.

In general, his JavaScript code is not very efficient either. There are 401 functions calls happening just on loading the device and these functions have a massive amount of if statements. This is probably a big reason why it takes so long to load the device and I haven't checked how often these functions are being called while using the device yet. I would be careful using this device, especially with many instances and in a live setting as you probably do."

Login to comment on this device.

[ browse device library ]