Visit our Online Manual

If you need further clarification of the Conductr App, go here for a comprehensive instructions manual.

ONLINE MANUAL

Parameters' persistence & the broken parameters case

PARAMETERS' PERSISTENCE:

Each Conductr's User Module can contain up to 5 parameters. Each parameter can belong to any device featured on any track on your Ableton Live set. This is one of the main innovations brought by Conductr and it's been a huge technological challenge.

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 on 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. No need to map it again!

THE BROKEN PARAMETERS CASE:

When on an Ableton Live set the user deletes a parameter previously mapped on a Conductr's User Module, 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. If the User Module is executed on a Playground View, the deleted parameter is shown with a lower opacity. It can be edited or deleted.

alert.png

WORKING WITH ID'S. SOME SUGGESTIONS:

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.

Have more questions? Submit a request

Comments

Powered by Zendesk