I can’t map a parameter with the LEARN FUNCTION
The LEARN FUNCTION may not work if you try to add a parameter which is already automatized on you Ableton Live project while playing it. If you want to do so, use the LEARN FUNCTION when the project is not running.
How can I recover a parameter’s original values after playing with it on a USER MODULE?
You can recover a USER MODULE parameter’s original values (the values they had when the USER MODULE was selected on the PLAYGROUND) whenever you want. Tap on the RESET icon on your USER MODULE side menu.
Can I set a parameter’s new value and recover it when playing with it on a USER MODULE?
You can save a USER MODULE parameter’s values to memory by dragging the RESET icon into the module. The parameter value will be saved when you drop it*. You can load that parameter value by tapping on the RESET icon.
I’ve set a a parameter’s new value using the RESET function and now I can’t recover the original one
When a parameter value is saved, the previous one is eliminated. If you save a value after changing the parameter’s original values (the values they had when the USER MODULE was selected on the PLAYGROUND), these will be erased.
Can I add any parameter to the K coordinate on the XY-4D pads?
No. The K coordinate is a tap controller and can only control on/off buttons.
What if I want to play with less than 4 parameters on a XY-4D pad?
You do not have to necessarily add parameters to all four coordinates to make your XY-4D pad work.
What if a device previously set up on Conductr is changed on the Ableton Live set (i.e. changing its location, moving it to a different track or even deleting it)?
Conductr can keep the parameters’ persistence in any of the aforementioned cases in real time.
E.g., if a parameter of a device featured on track 1 is being used on a User Module and the user cuts & pastes the device on track 2 while playing live, Conductr notices it and changes its location on real time, so the user can keep on using it without having to modify the set up.
Conductr can also detect these changes and keep the persistence even when a device or a track are modified on the Ableton Live set while Conductr is not enabled. When the user opens up the Conductr project related to that specific Ableton Live set, it will automatically scan the whole project and modify all the required parameters, so the user can keep on playing it without having to worry about the changes done on the Ableton Live set.
What if I delete a parameter previously mapped on a Conductr’s User Module on my Ableton Live set?
It can’t be modified by Conductr, obvioulsy. When this happens, Conductr shows a pop-up notification and an alert icon on the User Modules set-up screen. It can be edited or deleted.
What’ are the “cID” and “cIDT” labels that appear on my Ableton Live set’s devices and tracks?
The API provided by Ableton doesn’t allow to keep the parameters’ persistence by itself. In order to recognize them, Conductr provides an ID (“cID” for devices and “cIDT” for tracks) that is automatically added at the end of each device’s or track’s name when it features any parameter mapped on a User Module.
Because of this, we make some suggestions in order to keep the persistence and not get broken parameters unnecessarily.
Do not change manually the IDs added by Conductr at the end of a device’s or a track’s name.
Do not work with various Conductr projects on a single Ableton Live set.
If a parameter appears broken and it doesn’t respond appropriately, it can be refreshed by moving the device’s or track’s position on the Ableton Live set.
We recommend to use a different Conductr project for each Ableton Live Set. In order to get an easy and quick interrelationship, we recommend to name each Conductr project as the Ableton Live set it controls.