Device Details
Overview
| Name | Version: | Arturia Chorus DIMENSION-D Wrapper 1.0.0 |
| Author: | midrun |
| Device Type: | Audio Effect |
| Description: | (FREE FOR LIMITED TIME) A Max for Live wrapper that mirrors Arturia Chorus DIMENSION-D’s interface exactly, giving you the full look and feel of the original plugin right inside Ableton. ATTENTION: - To use the Wrapper you must have purchased and installed the Chorus DIMENSION-D Plugin. Features: - Live 12 Native Access for All functionalities from Chorus DIMENSION-D - Chorus DIMENSION-D Animations in Ableton Live - Fully Bi-Directional Mapping of Wrapper to Plugin (incl. Automations) - Ableton Push Controls Integration Notes: - Change Presets by opening the Plugin Window - Wrapper only supports VST3 (Please reach out to me if you require VST2 or AU) - Plugin opens/closes by clicking on the wrench icon. - Wrapper has only been tested in MacOS and Ableton Live Suite 12 |
Details
| Live Version Used: | 12.0.5 |
| Max Version Used: | 8.6.2 |
| Date Added: | Sep 14 2025 11:09:01 |
| Date Last Updated: | No Updates |
| Downloads: | 0 |
| Website: | https://midrun.gumroad.com/l/chorus_dimension_d_wrapper/EARLY_BIRDS |
| ⓘ License: | Commercial |
Average Rating
Log in to rate this device |
-n/a- |
Comments
Hi Frank
Thanks for your question!
From technical side: no there is no advantage, actually a disadvantage, since more CPU is used for the same audio processing.
From UX perspective: yes there is an advantage as you can see the configs of the plugin without the need of opening the plugin, as well quick access to all the parameters.
In the end it’s your individual workflow which determines if it’s useful for your case or not.
I personally like to have my favourite plugins within a wrapper. Therefore, I create from time to time wrappers for the plugins.
As you mentioned you have a programming background, you would probably have no problems with creating the wrappers by your own (as it’s not complicated but of course time-consuming if you have an eye on detail).
If you want to try out the ones I’ve shared, let me know!
I can for sure provide you some access to them and would as well be very happy for feedback and ideas for improvements.
Thanks for your question!
From technical side: no there is no advantage, actually a disadvantage, since more CPU is used for the same audio processing.
From UX perspective: yes there is an advantage as you can see the configs of the plugin without the need of opening the plugin, as well quick access to all the parameters.
In the end it’s your individual workflow which determines if it’s useful for your case or not.
I personally like to have my favourite plugins within a wrapper. Therefore, I create from time to time wrappers for the plugins.
As you mentioned you have a programming background, you would probably have no problems with creating the wrappers by your own (as it’s not complicated but of course time-consuming if you have an eye on detail).
If you want to try out the ones I’ve shared, let me know!
I can for sure provide you some access to them and would as well be very happy for feedback and ideas for improvements.
Posted on September 20 2025 by midrun |
Report Issue
Login to comment on this device.
Browse the full library
I have a programmers background so I basically understand what a wrapper is, but what's the advantage of all the M4L wrappers of existing plugins?
thanks a lot
Frank