3 ms·
The MP Controller is about as close as you'll get unless you go for an AIO solution like an Astrolab https://mpmidi.com/u-he-plugins-mp-controller https://mpmi
by piltdownman 9mo ago
The MP Controller is about as close as you'll get unless you go for an AIO solution like an Astrolab
https://mpmidi.com/u-he-plugins-mp-controller https://mpmidi.com/u-he-plugins-mp-controller
https://www.arturia.com/products/hardware-synths/astrolab/astrolab-61 https://www.arturia.com/products/hardware-synths/astrolab/as...
- PaulDavisThe1st 9mo agoIt still seems to me that they want "the opposite": the plugin GUI is drawn to show the control surface.
- piltdownman 9mo agoOh, well then the solution is to use Ableton Live w/Max/MSP and create Custom VST User Interfaces. https://www.ableton.com/en/live/max-for-live/ https://www.ableton.com/en/live/max-for-live/ https://www.youtube.com/watch?v=bsChOb_Oh8U https://www.youtube.com/watch?v=bsChOb_Oh8U Elisabeth Homeland does a range of Max for Live Wrappers that act as a translation layer between the host and the hosted VST, rendering the interface in the stock ableton device style. The OP would need to code up a similar template for their surface of choice, and then map the CC's and other MIDI sysex stuff as needed. https://www.elisabethhomeland.com/products/wrapper-bundle-by-elisabethhomeland-maxforlive-pack-for-ableton-live https://www.elisabethhomeland.com/products/wrapper-bundle-by...
- PaulDavisThe1st 9mo agoYou could also do the same thing in an open source DAW too. The problem is that it is specific to the control surface ... the other problem is that it's not actually clear that a given control surface is actually an ideal layout for a given plugin either (hence all the work done by the developer(s) on their own custom GUI).