ShowCockpit Academy
  • 🏠Welcome
  • Getting Started
    • Installation
    • Elements
    • Mapping
  • Tutorials
    • 🧩Integration
      • Ableton Link to MA2
      • LTC Input to MA2 OnPC
      • REAPER Markers to Onyx Cues
      • Ableton Link to Onyx FX Speed
      • MIDI Device with Bitfocus Companion
    • 🎬Timecode
      • LTC to MTC
      • MTC to LTC
      • Static Time Offset
      • LTC Input from Dante
    • 🔄Protocol Conversion
      • OSC to MIDI
      • MIDI to OSC
      • Keyboard to MIDI
      • Joystick to MIDI
    • 💡Lighting
      • grandMA3 OnPC Hotkeys
      • MIDI device(s) with an MA3 Desk
      • Connecting to MA3 OnPC on the same PC
      • MIDI device(s) with MA2
      • MA2 Bi-directional Page Sync
      • MIDI device(s) with Chamsys MagicQ
      • Obsidian Onyx - Multiple OSC Devices
      • Obsidian Onyx Pre-Dylos vs. Dylos
      • MIDI device(s) with Obsidian Onyx
    • 🎥Video
      • Resolume Arena Timecode Clip Trigger
      • Controlling OBS with a MIDI device
      • Controlling vMix with MIDI Devices
    • 🎛️Generic MIDI Mapping
      • Encoders Tips
    • 🤓LUA Scripts
      • Get MA2 Speed Master BPM value
    • 🌐Networking
      • Loopback Network Adapter
      • Multiple IP Addresses on a NIC
  • FAQs
    • License FAQs
    • Registration FAQs
    • Drivers FAQs
Powered by GitBook
On this page
  • Is it really an encoder?
  • My encoder behaves as a fader - is there a workaround?
  • Workaround 1 - Edit device output
  • Workaround 2 - Map it as a fader

Was this helpful?

  1. Tutorials
  2. Generic MIDI Mapping

Encoders Tips

Mapping MIDI encoders can sometimes be confusing. This page will guide you through better understanding these controls.

PreviousGeneric MIDI MappingNextLUA Scripts

Last updated 1 year ago

Was this helpful?

Is it really an encoder?

Before you start, you must ensure the control you are trying to map as an encoder really behaves as an encoder. The difference between faders and encoders:

  • Faders: outputs discrete absolute values in a range (between a maximum and a minimum)

  • Encoders: outputs relative values (increment or decrease)

In the MIDI world, sometimes there are devices that have physical encoders, but will output data as faders.

So, being an encoder means, in general, that when you rotate the physical encoder to the right, it keeps outputting the same value (with no limits). Rotating the encoder to the left, will output a different value. The increment/decrease value depends on the number of encoder "ticks".

If you set the Generic MIDI (or any other MIDI driver) in , the application will output the raw MIDI data received from the device.

This is very helpful to distiguish faders and encoder types

My encoder behaves as a fader - is there a workaround?

Workaround 1 - Edit device output

Some MIDI devices allow you to edit the controls output. Some of them can be set to work as encoders or faders using a manufacturer's application. Please check out your device User Manual for this.

Another workaround is to set the minimum "fader" value of 0 and maximum of 1. This will turn your control into an encoder-type because rotating to the right will make it output 1 and rotating it to the left will output 0.

Workaround 2 - Map it as a fader

If you cannot edit the control output to make it behave as an encoder, you can still map it as a fader and then use the driver.

🎛️
Verbose log level
Fader to Encoder