Jump to content
Sign in to follow this  
amsdenj

Helix Native MIDI Operations in Logic Pro X

Recommended Posts

Knowledge base article Helix Native Midi Operations in a DAW provides instructions on how to use MIDI messages to control block bypass and parameter values in a number of common DAWs, including Logic Pro X. The instructions for Logic Pro X don't actually make use of the new feature in Helix Native 1.60 and beyond that allows direct use of MIDI CC messages for block bypass and parameter control. This is because Logic Pro X does not send MIDI messages to audio track plugins, you have to use controller assignments that map to the Helix Native switch and knob automation parameters which are then configured as automation assignments in Helix Native.

 

There is however a way to use this direct MIDI CC control of block bypass and parameters in Logic Pro X. What you do is use a software instrument track instead of an audio track so that the MIDI messages will be sent to the track, and you can choose which MIDI channel to get the messages from. Next you select the Instrument slot for the software instrument track, and add Helix Native. Now Helix Native isn't a tone generator, and generally won't respond to MIDI messages the same way a software instrument would, but it will respond to MIDI CC messages that are mapped to block parameters, and that's just what we want. 

 

Unfortunately, software instrument tracks don't support audio inputs, so no sound comes out of Helix Native since your guitar isn't connected to that track. But there's a work around for this - software instrument plugins include a Side Chain audio input that can be used to control the software instrument tone generator based on an analog input. If you set the Side Chain input to the audio interface input your guitar is connected to, then your guitar will be input into Helix Native. Now you have both audio inputs and MIDI messages being sent directly to Helix Native - not as an Audio FX plugin, but as a Software Instrument with an analog side chain input.

 

There are however a couple of complications you should be aware of. First, if you have any controller assignments configured for the same MIDI device and CC messages, you won't see the MIDI messages in the software instrument track. All MIDI messages that are mapped to controller assignments are consumed by the controller, and are not sent to any software instrument track. So be careful about overlapping controller assignments and Helix Native direct MIDI CC assignments, the track won't see any of the overlapping assignments.

 

The second complication is recording. MIDI tracks only record MIDI, not audio. So although the software instrument track with instrument set to Helix Native will provide monitor sound, this sound won't be recorded. To record you need to create an audio track for your guitar input, record that track with dry guitar, and route the output of that track to a bus which is then used as the input to the side chain. Now when you record, one track will record the audio, and the other will record the MIDI CC messages. On playback, you'll be playing the audio track through Helix Native since the track is going through the bus into the software instrument's side chain. Recorded MIDI messages will also be sent to Helix Native, essentially playing back the button presses you did when recording. 

 

This is a little complicated, but works great and is very flexible.

 

Why is this useful? Really three reasons. First, controller assignments are pretty tricky with Logic Pro X (MainStage is much better). You might find direct mapping of MIDI CC messages to Helix Native parameters a lot simpler. Second, Helix Native only supports 16 switches and 16 knobs that can be the target of controller assignments in order to configure plugin parameter automation. That might not be enough control for complex patches. Third, it can sometimes be quite difficult to get plugin automation to record and playback properly. For some plugins, the state of the automation parameters is not known until the track gets the first MIDI message. This can for example cause a distortion block that you turned on for the first chorus to be turned on from the beginning of the track - the automation parameter didn't get initialized properly. You can easily fix this by manually adding the missing automation point, but this adds more work.

 

Hope you Logic Pro/Helix Native users find this helpful.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×