How to automate MIO Console Mixing Board fader from Digital Performer | |
![]() |
Fader AutomationMIO 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 |
![]() |
1. You will create virtual MIDI I/O ports in DP by opening Setup > Interapplication MIDI dialog box |
![]() |
2. Click [Add] for Inputs and Outputs. The default name appears. |
![]() |
3. Create a MIDI track in DP, click-open a MIDI track output assignment popup window, and select DP Output-1 as the destination. |
![]() |
4. Insert a "Reassign Continuous Data" MIDI plug-in for the MIDI track. |
![]() |
5. Set the source to CC7, and the target to Pitch Bend. UPDATE: |
![]() |
6. In MIO Config, set the Controller input to DP Output. That's it! Enjoy!
UPDATE: |
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. |
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
25
|
40
|
19.9
|
19.9
|
29
|
35
|
35.5
|
30
|
20
|
30
|
30
|
21
|
18
|
23 tp 30
|
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 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.
This preparation steps, which will be saved as template, are to avoid later confusion and accident such as feedback loop.
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…
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.
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.
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 MIO Car! - Look at the plate: 138 MIO!
That's 321,868.8 Km!! 32万1千8百68.8キロ!