Welcome to the Private Metric Halo Party

Go to MH Web Site

Go to Metric Halo Site »
Go to Metric Halo Mailing List »
Go to Metric Halo Forum »
Go to Mobil I/O FAQ Site »

MIO on the Job

 

How to automate MIO Console Mixing Board Channel Fader from Digital Performer

How to automate MIO Console Mixing Board fader from Digital Performer
automation

Fader Automation

MIO Console Mixing Board channel fader can receive Pitch Bend MIDI information, which can be used as automation from Digital Performer.

Here is a step by step instruction to link Digital Performer to MIO Console Mixing Board channel fader


[Mute]/[Solo] Automation explained below

Interapplication MIDDI

1. You will create virtual MIDI I/O ports in DP by opening Setup > Interapplication MIDI dialog box

Interapplication MIDI Config

2. Click [Add] for Inputs and Outputs. The default name appears.

Track Assignment

3. Create a MIDI track in DP, click-open a MIDI track output assignment popup window, and select DP Output-1 as the destination.

MIDI Plug-in

4. Insert a "Reassign Continuous Data" MIDI plug-in for the MIDI track.

MIDI Plug-in Config

5. Set the source to CC7, and the target to Pitch Bend.

UPDATE:
You need to engage "Copy" mode instead of "Change" mode, or you will not see DP fader moving with the MIO fader.

MIO Config

6. In MIO Config, set the Controller input to DP Output.

That's it!

Enjoy!

 

UPDATE:
Be sure not to create MIDI Loop.  It will bring MIO Console into SWOD (Spinning Wheel of Death). Yes, I have been there!

You can automate [Mute] and [Solo] as well

Once the above channel fader automation is working, you can toggle [Mute] and [Solo] by inserting a MIDI note. For example, I found MIDI note E-1 (this is negative 1) toggles [Mute] and MIDI note G#-2 toggles [Solo] on channel 1 in the MIO Console Mixing Board.

The hardest part is to find the exact MIDI note value. I used MIDI Monitor application for this.

This text will be replaced

MIO2882 Microphone Matching List

High Sensitive Microphones which works best with Mobile I/O
~ Sensitivity c.a. 20mV/Pa recommended to use with MIO ~
Note: High sensitivity may be only needed when tracking quiet source such as classical music from distance.

The Fomula

If x = sensitivity in dBV e.g. -66dBV/microbar(.1Pa)

then sensitivity in mV is

10^(x/20) * 1000

or .5mV/microbar - to get mV/Pascal multiply by 10 which gives 5mV/Pa for the Core Sound mics.

- Joe Buchalter, Metric Halo


The list of matching microphones for MIO2882

MIOConsoleConnect and MIO FW Process Return with DigitalPerformer

While Metric Halo web site has a very good Digital Performer (DP) Tutorial, being a long time DP user and MIO user, I have a slightly different way of setting this up, and wished to share to anyone who is interested. Remember that you should set it up on your new DP project file and save it as one of your template, or even default template. That's what I did.

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.

Time Slip Mystery

The blue soundbite on the top is the source, one of the click samples for DP I created. The pink soundbite on the bottom is the printed FWReturn.

Oddly, it is ahead by 50 samples.

This project is 24 bit / 44.1k. The MIO +DSP on this test has one instance of MIOStrip with every param engaged. The mystery here is that this 50 samples offset does not change whether Plug-in Compensation is engaged or hardware buffer is set to low/high.

My Jensen ULN-2 2d

jensen Joe Buchalter handing me the first Jensen ULN2+DSP mod.

This thing sounds sweet!

My MIO Car!

My MIO Car!: Look the plate: 138 MIO!My MIO Car! - Look at the plate: 138 MIO!

 

 

That's 321,868.8 Km!!  32万1千8百68.8キロ!