Many Pro Tools users run Auriteq Flow next to another HUI controller, such as a fader controller with eight channel strips. Out of the box, Pro Tools gives each of them a different set of tracks: one controller gets tracks 1–8, the other tracks 9–16, and scrolling one of them scrolls the other as well.
Auriteq Flow can instead let the other controller share its tracks. Pro Tools then sees a single HUI controller, and both devices show and control the same eight tracks. Faders, buttons and knobs on either one reach Pro Tools, and both follow the session.
This only needs to be set up once.
Note: This option is available from Auriteq Flow 3.2.0. It works with any controller that connects to Pro Tools in HUI mode. The Auriteq app has to be running for the other controller to work, because its connection to Pro Tools now goes through Auriteq.
Why This Happens
Pro Tools lines up every HUI controller it knows into one long surface, in blocks of eight channels. The first controller gets tracks 1–8, the next one tracks 9–16, and so on. Two controllers can never show the same tracks this way, and banking moves the whole surface at once.
This is how the HUI protocol works in Pro Tools. It is not specific to Auriteq Flow or to the other controller.
With the option described here, Pro Tools keeps only one HUI controller, Auriteq. The other controller connects to Auriteq instead of to Pro Tools, and Auriteq mirrors everything Pro Tools sends to its eight strips. Both devices therefore show the same tracks.
Step 1: Put the Other Controller in HUI Mode
Set the other controller to the mode it uses for Pro Tools. On most controllers this is called HUI or Pro Tools mode.
Connect it to your computer as usual.
Step 2: Remove It From Pro Tools
The other controller must no longer be connected to Pro Tools directly. Otherwise every button press reaches Pro Tools twice.
In Pro Tools, open Setup → Peripherals → MIDI Controllers. Find the row of the other controller and set its Type to None. Leave the AuriteqHUI row as it is, so that AuriteqHUI is the only HUI controller in the list. Click OK.
Note: Pro Tools gives plug-in control to the HUI controller in row #1 only. Make sure AuriteqHUI sits in the first row, whether it is the only HUI controller or it is sharing its tracks with another controller.
Then open Setup → MIDI → MIDI Input Devices and untick the other controller’s port. Click OK.
Note: If you have never added the other controller to Pro Tools, you can skip this step.
Step 3: Connect It Through Auriteq
In the Auriteq app, open Settings → Workflow and find the section Second HUI controller (Pro Tools).
Switch on Share Auriteq’s tracks with another HUI controller.
Then choose the controller’s two MIDI ports:
- Controller output is the port the controller sends on.
- Controller input is the port the controller listens on.
Most controllers use the same name for both ports. When you pick the output, Auriteq selects the matching input for you if there is one.
If the controller does not appear in the lists, make sure it is connected and in HUI mode, then click Rescan ports.
The Status line in this section tells you whether Auriteq has opened the controller’s ports and when it last received something from it.
Step 4: Check Both Controllers
With a Pro Tools session open, the other controller should now light up and show the same track names as the Auriteq controller.
Select a track on the Auriteq controller and watch the other controller follow. Move a fader on the other controller and watch the volume readout on the Auriteq controller follow.
Scrolling the tracks from the other controller, with its channel or bank buttons, keeps the selected track under the same strip on both devices.
Controllers With 16 Channels
A 16-channel controller appears to Pro Tools as two HUI controllers. Connect its first eight channels through Auriteq as described above, and add its second eight channels in Pro Tools the normal way, in the row after AuriteqHUI.
Keep AuriteqHUI in row #1 here as well: the combined first eight channels are the ones Pro Tools gives plug-in control to.
Pro Tools then shows tracks 1–8 on the Auriteq controller and on the first half of the surface, and tracks 9–16 on the second half, exactly as the 16-channel controller works on its own.
Optional: Keep the Eight Strips Where They Are
By default, Auriteq scrolls Pro Tools’ eight HUI strips whenever a track outside them is selected, so that volume, pan, sends and meters on the controller always address the selected track.
If you prefer the strips to stay put and move only when a controller scrolls them, switch off Settings → Workflow → Selected track & the eight HUI strips → Bring the selected track under the controller’s strips.
Warning: With that option off, volume, pan, sends and the meters on the Auriteq controller stop working whenever the selected track is outside the eight strips. Track selection, names, mute, solo and record-arm keep working for every track.
Troubleshooting
- The status line says “Waiting”. The controller is not connected, not in HUI mode, or another application is holding its MIDI port. Check the controller, then click Rescan ports.
- Every button press happens twice. The controller is still connected to Pro Tools directly. Repeat Step 2.
- The other controller shows tracks 9–16. Pro Tools still lists it as a HUI controller. Repeat Step 2 and make sure AuriteqHUI is the only HUI controller in Setup → Peripherals → MIDI Controllers.
- Plug-in control does not work on the Auriteq controller. AuriteqHUI is not in row #1 of Setup → Peripherals → MIDI Controllers. Pro Tools only gives plug-in control to the first HUI controller; move AuriteqHUI to the first row.
- Nothing happens on the other controller. Make sure the Auriteq app is running. Its connection to Pro Tools goes through Auriteq, so it only works while the app is open.
Done
After completing these steps, both controllers show and control the same eight tracks in Pro Tools.
You do not need to repeat this setup. Auriteq remembers the controller’s ports and reconnects to it automatically, even if you plug it in after the app has started.