Skip to content

Orestes‐One

Jump to bottom
Richard Smith edited this page Sep 28, 2024 · 15 revisions

This is the documentation of the RSBATechModules Orestes-One VCV Rack module and related Electra-One MIDI controller preset.

The Orestes-One VCV Rack module provides external VCV Rack parameter control from the Electra-One MIDI controller with two-way display value and control label feedback, remote module switching, automapping etc. It works together with a custom Electra-One MIDI Controller preset called "VCVRack", which you must have loaded into a preset slot on your Electra-One device.

First demo and basic mapping tutorial (Youtube)

Separate user guide pages for the module and the Electra-One preset are linked below, followed by a list of main user workflows using them both together. The main idea is that once you have completed any module mapping you need to do for a Rack patch, you can then let go of your mouse and play the patch using only the Electra-One controller.

Warning

28 Sep 2024 The "VCV Rack 2" Electra One preset will ONLY work with firmware 3.7. Please install the latest 3.7 beta firmware before trying to run this preset.

Getting Started

  1. Until / unless Orestes-One is added to the VCVRack Library, you will need to install it yourself using a pre-built installer available in this git repository. See the repo README for instructions on how to install the pre-built binaries or compile and install yourself.

  2. Make sure you running Electra One firmware v3.7 (current beta) or above.

  3. Paste this into the Development Sandbox browser page to disable Electra One's automated "reset to default" action when you double tap a pot (it interferes with the reset value command sent to the Orestes One module by the VCV Rack preset, making it almost unusable):

{
  "uiFeatures": {
    "controlDoubleClickAction": "none"
  }
}

  1. Load the "VCV Rack 2" preset from the Electra-One Preset Library into a free preset slot on your Electra One controller. Make sure your Electra-One is connected to your computer via USB.

  2. Add the Orestes-One module to a VCVRack patch.

  3. Select the four MIDI Ports needed for 2-way communication with your Electra-One controller (the Electra-One USB port names might be different on your computer - they vary between mac, windows and linux):

    • e1 data port input = Electra Port 1 Channel 1
    • e1 data port output = Electra Port 1 Channel 1
    • e1 ctrl port input = Electra CTRL Channel 1
    • e1 ctrl port input = Electra CTRL Channel 1

  4. Orestes-One will load and copy its factory mapping library into the module if the preset does not already have a mapping library selected. The number label on the bottom right-hand corner shows the number of loaded mapped modules.

  5. The Electra-One "VCV Rack 2" preset should briefly show "Searching for compatible Orestes-One..." on Page 1, then display the current parameter mappings in the Orestes-One module. If there are none, this will just show a page with unmapped controllers.

  6. Press pots 7,8 & 9 together (or press the Electra-One [MENU] button and select Page 12 "Select Module").

  7. Page 12 "SELECT Module" will display any pre-mapped modules in your VCVRack patch that is in the loaded mapping library. Press a module button control on the Electra-One display to load that mapping into Orestes-One.

  8. Electra-One switches to Page 1. You can now start adjusting any of the first 36 controls which will immediately change the mapped VCVrack module parameter.

See Pages 1-6 for more details on how to use and navigate around the VCVRack patch.

Mapping Workflows

Typical mapping workflows, in approximate order of increasing complexity and sophistication

  • Map a small number of performance parameters for one Rack patch only
  • Use pre-mapped module mappings from the Orestes-One factory library
  • Switch between a Rack patch - level mapping (e.g. some manually mapped Patchmaster modules) and individual module mappings
  • Auto-map all modules in a Rack patch that are not already included in the Orestes-One mapping library
  • Auto-map a single module
  • Manually map a single module (or edit an existing module map), save in the mapping library
  • Manage the mapping library loaded into the O1:
    • Import mappings from other O1 mapping library JSON files (or the O1 factory library)
    • Select a different O1 mapping library file
    • Delete all mappings from the current loaded library file for a given plugin
    • Export all mappings from the current loaded library for a given plugin
    • Delete the mapping of a single module from the current loaded library file
Clone this wiki locally