Arturia/MCC/UG/03 Working with Templates

• 3. Working with templates

  • Arturia/MCC/UG/03 Working with Templates/01 Sync Button

    • 3.1. The Sync button

      • Sync support varies by product. The 2017 manual lists BeatStep, KeyStep, and KeyLab as examples that support it, and BeatStep Pro, DrumBrute, Spark, and MiniLab as examples that do not.
      • Arturia/MCC/UG/03 Working with Templates/01 Sync Button/01 Sync Operations

        • 3.1.1. Sync operations

          • Sync backs up device memory as a local Template and, on supported products, permits live editing.

          • Note/Warning While synced, selecting a Template in the Project Browser sends it to the device and can erase changes made on the hardware.
            

      • Arturia/MCC/UG/03 Working with Templates/01 Sync Button/02 Non-sync Operations

        • 3.1.2. Non-sync operations

          • Without Sync, supported devices can still transfer patterns, sequences, or banks; edit device settings; and create or manage Templates.
          • Store To and Recall From move memory banks between MCC and the device.
  • Arturia/MCC/UG/03 Working with Templates/02 Memories Projects and Templates

    • 3.2. Definitions: Memories, Projects, and Templates

      • A Memory stores control assignments and sometimes sequence, arpeggio, or drum data. A Project holds a broader set of data, such as several sequencers and MIDI assignments.
      • A Template is MCC’s computer-side copy of a Memory or Project. User data is archived as Templates in the Project Browser.
      • Arturia/MCC/UG/03 Working with Templates/02 Memories Projects and Templates/01 Project Tab

        • 3.2.1. The Project tab

          • On products with a Project tab, its settings apply to the whole Template. They travel with Store To and Recall From.
          • Device Settings are separate global parameters. They are exported and imported independently of Templates.
  • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser

    • 3.3. Project / Template Browser

      • The browser holds archived Templates on the computer in Factory and User groups. A Template usually mirrors the device memory layout, though some devices hold multiple Templates.
      • Templates do not include Device Settings.
      • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/01 Device Templates

        • 3.3.1. Device Templates

          • A Template may contain several data layers. Expand or collapse them with the browser’s plus and minus controls.
      • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/02 Build Library

        • 3.3.2. Building a library

          • Use Recall From to copy changed device memory into a new User Template. MCC gives it a timestamped name, which can be renamed.
          • The User Templates area can hold a library of presets, patterns, or sequences beyond the device’s capacity.
      • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/03 Working Memory

        • 3.3.3. The Working Memory / Working Project

          • When synced, Working Memory represents the device’s active memory and most MCC edits also reach the device.
          • When unsynced, Working Memory is a staging area. MCC edits do not automatically change the device.
          • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/03 Working Memory/01 Live Editing
          • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/03 Working Memory/02 Drag and Drop
      • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/04 Revise Template

        • 3.3.4. Revise a Template

          • Select an archived Template to edit it in MCC. Save or Save As preserves changed computer data.
          • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/04 Revise Template/01 While Synced

            • 3.3.4.1. While synced

              • Selecting a Template sends its data to the connected device. Further MCC edits also affect the hardware; an asterisk signals unsaved Template changes.
          • Arturia/MCC/UG/03 Working with Templates/03 Project and Template Browser/04 Revise Template/02 Not Synced

            • 3.3.4.2. Not synced

              • Edit an archived Template in MCC, then save it. To hear the result on the hardware, drag the revised Template to Working Memory or use Store To.

              • Note/Warning Sending the revised Template overwrites Working Memory and device pattern memory. Preserve existing work before transfer.
                

  • Arturia/MCC/UG/03 Working with Templates/04 Store To and Recall From

    • 3.4. Store To / Recall From

      • Arturia/MCC/UG/03 Working with Templates/04 Store To and Recall From/01 Store To

        • 3.4.1. The Store To button

          • Select a local Template, then press Store To to transmit all of its data to the device when Sync is off or unsupported.
          • When synced, selecting the Template itself transmits it.

          • Note/Warning Store To overwrites device memory. Use Recall From first when the current device data has not been archived.
            

      • Arturia/MCC/UG/03 Working with Templates/04 Store To and Recall From/02 Recall From

        • 3.4.2. Recall edited data from the device

          • Recall From copies the device data into a new timestamped local Template. Rename the copy if a descriptive name is useful.
      • Arturia/MCC/UG/03 Working with Templates/04 Store To and Recall From/03 Template Utilities

        • 3.4.3. Template utilities

          • Save and Save As preserve or duplicate a Template. New creates one from defaults; Delete removes a Template from the Project Browser.
          • Template Import and Export exchange product-specific Template files, such as .beatstep for BeatStep. These are distinct from Device Settings Import and Export.