MIOConsoleConnect with DigitalPerformer

MIOConsoleConnect makes MIOConsoleX setting saved with your DP project. Whether you wish to save one setting per project file or one setting per sequence within single project file, the best way is to use one of the MasterFaders as the place holder.

Note: To avoid the real MIOConsoleX to keep restarting, you may wish to have it launched before you use MIOConsoleConnect in DP.

Note: For people like me who dislike floating window in general and is too used to switch applications with Cmd+Tab, MIOConsoleConnect offers Conduit Mode via its preferences, which still gives great benefits of saving MIO settings with project.

Preparation steps

This preparation steps, which will be saved as template, are to avoid later confusion and accident such as feedback loop.

1. Open Audio Bundle (Shift+U)
2. Click on Busses tab
   
3. Click Add
   The default is Stereo pair. Even though MIOConsoleConnect does not need to be stereo, I leave it because it is easier to keep things in even numbered pairs.
   
4. RENAME newly created "bus 1-2" to "MIO Dummy" to avoid later confusion.
   
5. Scroll to the right end and double-click at bus 63 so both bus 63 and 64 are selected.
   

Instantiate MIOConsoleConnect

If you need one MIOConsoleX setup saved per project, you should use DP's V-Rack for where MIOConsoleConnect instantiated. On the other hand, I use 4 MIO boxes for mixing with MIO+DSP mix bus, and it becomes necessary to instantiate MIOConsoleConnect per sequence especially when I am mixing for album. In this case, I instantiate within each sequence instead of using V-Rack.

1. Create MasterFader (Ctrl+Cmd+F) where you desire, sequence or V-Rack
2. RENAME MasterFader
   This is very important for me because it is just a place holder and is not really functioning as MasterFader. I would rename it as MIOConsole
   
3. Assign MasterFader's output to "MIO Dummy"
   
4. Insert MIOConsoleConnect as you usually insert effect plug-in on MasterFader

If you wish to use a normal MasterFader for your analog output, you may do so by ignoring MIOConsoleConnect Master Fader

TIP: The MasterFader that holds MIOConsoleConnect, which was instantiated in a sequence, can be moved to V-Rack easily by selecting "MIOConsole" MasterFader track in Track Overview Window first then Project Menu » Sequences » Move Selected Tracks to V-Rack…

MIO FW Process Return with DigitalPerformer 5.12

Again, Metric Halo site has very good tutorial page and tutorial movie. I would like to share slightly different approach for my conveniences especially the goal is to create a template for future use. In this tutorial, the differences between 2882+DSP and ULN2+DSP will be noted when applicable.

1. 2882+DSP only: Set Digital Output from ADAT to FW Return
   
2. Open DP's Audio Bundle (Shift+U)
3. 2882+DSP: Create 3 stereo pair of outputs and 6 mono outputs
   
   ULN2+DSP: Create 2 stereo pair of outputs and 4 mono outputs
   
   IMPORTANT: RENAME them to "Send" — To avoid feedback loop, it is very important to rename them so there will be no confusion when assigning
   NOTE: These DP outputs will be labeled DAW in MIOConsoleX
   Remember that DAW 1-2 is reserved for Analog output monitoring
   
4. Under MIOConsoleX Patchbay, patch Process output to FW Return/ADAT
   Tip: Holding Opt when selecting makes result in stereo pair
   
5. Back to DP, Create 4 stereo pair of inputs and 8 mono inputs, and RENAME them to "RETURN"
   
6. At this point, send—return path has been established.
   • You can send the track signal to +DSP by selecting the track output
     
   • You can send the channel signal to +DSP
     
   • Audition the +DSP return signal by using AUX track
     
   • Print the +DSP return signal
     

   You could skip using AUX track by returning the signal to an audio track via Audio Patch Thru option under DP's Studio menu, which may cost your CPU usage, however.