>>>>> gd2md-html alert: ERRORs: 0; WARNINGs: 1; ALERTS: 15.
- See top comment block for details on ERRORs and WARNINGs.
- In the converted Markdown or HTML, search for inline alerts that start with >>>>> gd2md-html alert: for specific instances that need correction.</ul>
Links to alert messages:
alert1 alert2 alert3 alert4 alert5 alert6 alert7 alert8 alert9 alert10 alert11 alert12 alert13 alert14 alert15>>>>> PLEASE check and correct alert issues and delete this message and the inline alerts.
# open·control user manual # Installation: * Create a folder named Remote Scripts in Live’s User Library * Copy and paste the open_control folder into it. * Relaunch Live * Connect open·control and set the Preferences like this :>>>>> gd2md-html alert: inline image link here (to images/image1.png). Store image on your image server and adjust path/filename/extension if necessary.
 **MIDI Remote mode:** If you want to connect open·control with standard MIDI cables, connect the In and Out ports of open·control to your MIDI peripheral, and set the Input and Output ports accordingly. You need to plug open·control to a standard USB charger in order to provide it power. # Normal Use: **open·control** is very simple and straightforward to use. Each element of the controller (LEDs, display, buttons, sliders) can be configured to perform or display any of the selected actions. To configure the controller, connect it to your computer, and open the editor by opening the page open.control.html on a web Browser. **NB: The editor is currently only supported by Chrome, Opera and Edge.** When opening the editor, you will be asked if you authorize access to your MIDI devices, answer “Allow”. You should see the text ** open·control detected **, meaning that the controller is ready. All the controls will automatically be populated with the current actions.
(Back to top)(Next alert)
>>>>>>>>>> gd2md-html alert: inline image link here (to images/image2.png). Store image on your image server and adjust path/filename/extension if necessary.
 In this manual, the actions will be shown like this : **
(Back to top)(Next alert)
>>>>>This is an Action</strong>. **Display:**>>>>> gd2md-html alert: inline image link here (to images/image3.png). Store image on your image server and adjust path/filename/extension if necessary.
 This will change what is shown on the LED matrix. You can choose among: Scene Name, Track Name, Arrangement Marker Name, Variation Number and Looper Number. **Buttons:**
(Back to top)(Next alert)
>>>>>>>>>> gd2md-html alert: inline image link here (to images/image4.png). Store image on your image server and adjust path/filename/extension if necessary.
 You can choose actions for both Short and Long Press (> 0.5s). You can now choose which action you want each Button to perform among the drop-down list. The actions are effective immediately. **Snap**: The **Short Buttons** send their message when **releasing** the switch. This is necessary to achieve both Short and Long presses. However, for some actions, timing is crucial. In this case, you may need to send the value exactly when the Button is pressed. This is what Snap allows: **when it is selected, the Button performs only one action, and sends its message on button press.** **LEDs:** When selecting a Short Press action that has a LED action associated to it, the LED action will automatically be selected. For instance, if you choose **
(Back to top)(Next alert)
>>>>>Arm Track</strong> for Short Button 4, then the corresponding LED will automatically be set to show the Arm status. If you want it to show another parameter, you can still choose something else afterwhile. For actions that don’t have a color associated to them, you can set your own color by choosing **Custom Color</strong>, and then a number in the menu that appears to the right.>>>>> gd2md-html alert: inline image link here (to images/image5.png). Store image on your image server and adjust path/filename/extension if necessary.
 **Pages:** **You can set up to 3 different pages of actions**. Simply choose which page you want to edit using the top left chooser. To use the different pages, you will obviously need to set buttons to switch between them. This is done with the 2 actions at the end of the list: **
(Back to top)(Next alert)
>>>>>⇆ Page 2</strong>and⇆ Page 3. When set to **⇆ Page color</strong> , the LED will show the following colors:
You can find at the end of this document a complete list of actions for Display, Buttons, LEDs and Sliders. **External MIDI:** You can control open·control with external gear. To do so, simply connect the MIDI Out of your MIDI device to the MIDI In port of open·control. You then need to tell open·control which MIDI data acts as Button 1, Button 2 etc… You can configure it with the External MIDI part of the Editor. For instance, if your MIDI device sends Control Change 18 on Channel 4 and you want to act as Button 3, choose the corresponding values. Note: this will only work if the device sends momentary values, ie 127 (or any value greater than 1) when pressed, and 0 when released . If your MIDI gear sends MIDI messages other than the ones used by open·control, they will be passed through. This means that you can create a preset to control open·control, and still continue to use your device, open·control will then only act as a MIDI hub. If your gear has MIDI through capabilities, you can even use open·control in MIDI remote mode. To do so: - connect the MIDI Out/Through port of your controller to the MIDI In port of open·control - connect the MIDI Out port of open·control to the MIDI In port of your computer - connect the MIDI Out port of your computer to the MIDI In port of your controller # Looper: In order to be detected by open·control, the Looper devices must have (LOOPER_n_) in their name, where _n_ is a number. You can do this with the controller by selecting the Looper in Live and pressing the **Page 1 🟠 Page 2 🔵 Page 3 🟣 + Add Looper</strong> button. You can then select the Looper devices by pressing the**⧀ Prev Looper</strong>and⧁ Next Looperbuttons. **MIDI Mapping:** To use the Looper, it is necessary to combine the Control Surface and MIDI Mapping. This is because some of the features in Looper are not accessible via standard Control Surface actions. The first thing to do is make sure that “Input: Remote” is set to On for open·control. Once this is done, you need to map your buttons to the Loopers **① MIDI Map 1 (Big Button)</strong>to the Big Button **② MIDI Map 2 (Clear)</strong>to the Clear button (if needed) **③ MIDI Map 3 (Undo)</strong>to the Undo button (if needed) You need to do that individually for each Looper (don’t worry though, this is saved with your Live Set). These buttons are special, since the MIDI Note and Channel they send are automatically updated when you select a Looper device. This way, the same button lets you control several Looper devices. This also allows you to have a **Clear All</strong> button. All the **MIDI Map Buttons</strong>will send a Note On Message, where the Note number corresponds to the selected Looper number, starting at C0, ie Looper 1 = C0, Looper 2 = C#0, Looper 3 = D0 and so on. **① MIDI Map 1 (Big Button)</strong> will send the Note on MIDI Channel 16. **② MIDI Map 2 (Clear)</strong>will send the Note on Channel 15. **③ MIDI Map 3 (Undo)</strong>will send the Note on Channel 14. For instance with 4 Loopers mapped, your mapping should look like that:>>>>> gd2md-html alert: inline image link here (to images/image6.png). Store image on your image server and adjust path/filename/extension if necessary.
 **⚠︎** To have improved accuracy when using the Looper, It is better to have **Snap** on when using the **
(Back to top)(Next alert)
>>>>>① MIDI Map 1 (Big Button)</strong> # Extra Features: If you add (STOP) to a Scene name, or to an Arrangement Marker name, Live will stop playing when launching the Scene or crossing the Marker. # List of available actions and controls: **Display:**
**Buttons & LEDs:**Display Scene Name Track Name Arrangement Marker Name Variation Name Looper Number --- Global --- Button Actions LED actions LED color ■/▶ Start/Stop ■/▶ Start/Stop 🟢 ●○ Metronome ●○ Metronome 🟡 ⤶ Undo ▢ Capture ⊕ BPM +1 ⊖ BPM -1 ⮂ Arrangement/Session Toggle Clip/Device Toggle --- Arrangement --- Button Actions LED actions LED color ↞ Jump to 1.1.1 ⇉ Restart From Last Position ● Arrangement Rec ● Arrangement Rec 🔴 ⥁ Arrangement Loop ⥁ Arrangement Loop 🟡 ⇤ Go to Prev Marker ⇥ Go to Next Marker ⤓ Add/Delete Marker ⥀ Loop to Next Marker Punch In Punch Out --- Session --- Button Actions LED actions LED color ○ Session Rec ○ Session Rec 🔴 ▶ Launch Scene ▶ Launch Scene >>>>> gd2md-html alert: inline image link here (to images/image7.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
⬆ Sel Prev Scene ⬆ Sel Prev Scene >>>>> gd2md-html alert: inline image link here (to images/image8.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
⬇ Sel Next Scene ⬇ Sel Next Scene >>>>> gd2md-html alert: inline image link here (to images/image9.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
⥴ Jump to Playing Scene ⥅ Insert Scene ⧈ Stop All Clips ➟ Disable Follow Actions --- Tracks --- Button Actions LED actions LED color ← Sel Prev Track ← Sel Prev Track Color >>>>> gd2md-html alert: inline image link here (to images/image10.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
→ Sel Next Track → Sel Next Track Color >>>>> gd2md-html alert: inline image link here (to images/image11.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
▷ Launch Clip ▷ Launch Clip >>>>> gd2md-html alert: inline image link here (to images/image12.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
✽ Selected Track Color >>>>> gd2md-html alert: inline image link here (to images/image13.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
↳ Find Empty Slot ⌧ Mute ⌧ Mute 🟡 S Solo S Solo 🔵 ⌻ Arm ⌻ Arm 🔴 ■ Stop U Fold/Unfold Track ☆ Add Audio Track ✬ Add MIDI Track --- Looper --- Button Actions LED actions LED color ⧀ Prev Looper ⧀ Prev Looper Track Color >>>>> gd2md-html alert: inline image link here (to images/image14.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
⧁ Next Looper ⧁ Next Looper Track Color >>>>> gd2md-html alert: inline image link here (to images/image15.png). Store image on your image server and adjust path/filename/extension if necessary.
(Back to top)(Next alert)
>>>>>
① MIDI Map 1 (Big Button) ◈ Looper State 🔴🟢🔵 ② MIDI Map 2 (Clear) ③ MIDI Map 3 (Undo) ▣ Stop Looper ⌻ Arm Looper Track ⌻ Arm Looper Track 🔴 ⌧ Mute Looper Track ⌧ Mute Looper Track 🟡 ⌸ Show Looper "+" Add Looper ∅ Clear All --- Variations --- Button Actions LED actions LED color ⍇ Prev Device ⍈ Next Device ⌃ Prev Variation ⌵ Next Variation ▹ Launch Variation ◦ Store Variation ↩︎ Recall Last Used ⌁ Randomize Macros
**Sliders:**--- Pages --- Button Actions LED actions LED color ⇆ Page 2 ⇆ Page Color 🟠🔵 ⇆ Page 3 ⇆ Page Color 🟠🟣 --- Global --- Last Selected Parameter Global Groove Amount Scroll Scenes --- Selected Track --- Send A Send B Selected Device Param 1 Selected Device Param 2 Device 1 Param 1 Device 1 Param 2 --- Looper Track --- Looper Device 1 Param 1 Looper Device 1 Param 2