It seems that the Hapax has all the right architecture to allow for live recording CV into automation lanes, but I’m hitting a wall here, and I think it’s because there’s no apparent “source” selection for an automation lane, only “destinations.” Section 9.9 of the Hapax manual states, “For CV in recording, lanes must be created prior to recording” but it does not elaborate on workflow.
My setup:
I have a Bela Gliss touch controller connected to CV IN 1. Gliss is a high-resolution touch-sensitive control surface that sends 0-5 volts into the CV1 input, for recording purposes. CV OUT 1, 2, 3, and 4 have various modulation destinations on my modular rack.
My Goal:
I’d like to use the Gliss as a CV IN 1 “paintbrush” to live-paint automation curves directly into existing automation lanes for CV OUT 1, 2, 3, and 4 as an alternative to using the hapax pads for drawing automation points (which does not take advantage of the 192ppqn recording resolution).
This partially works if I split the workflow into two parts:
- Create a new automation lane, assign the destination as CV IN 1, and then record some expressive CV with the controller. This is unintuitive because CV IN 1 is acting like a source rather than a destination. Regardless, the high-resolution curve gets recorded, but is effectively “parked” without a real destination.
- I reassign the destination of the recorded automation lane to where I actually want it to be applied, like CV OUT 1 for example, which pastes over any automation curves that may have been present in CV OUT 1.
The problem with the above steps is that I’m separating the musical CV expression from the audible outcome, and fiddling with some menu diving in between, which isn’t aligned with the ethos of the Hapax being a live recording and modulating powerhouse. Am I missing something here, or have I identified a limitation?