2882 Quick Start Guide
103
Two things to be aware of when routing in the 3d mixer:
• Routing from a bus output to an Input strip is allowed, but as mentioned in the previous section, will
not be automagically latency-compensated.
• Since routing search filters can be combined, typing “tos” to find a TOSLINK port while the “Analog”
port type filter is selected will return zero results (because, after all, TOSLINK is a digital port). Best
practice is to select “All Channels” or “All Physical” (which includes all regular analog and digital
hardware ports, but not Host computer and SCP USB ports) when searching by text.
For more information regarding configuration and routing of ADAT/TOSLINK, MADI and USB
Digital I/O Status / Control Menu
USB Port Status and Configuration
sections
of the main manual.
Using the Mixer
You should now be in a good position to integrate the 2882 with your audio workstation. First, make
sure "Main" is selected as the Monitor Controller source. To play it safe (if you haven't already done so),
reduce the Monitor Controller level from it's default "0.0" and bring it up after the music starts. Select
“MHLink Audio” (or, if you are connecting via USB, "2882") as your audio interface in your DAW's hardware
configuration. To play from your DAW, send your DAW’s signal to outputs 1/2 and it will also come into
the 2882 on the Host 1/2 strip. Hit “Play” in your DAW and enjoy.
Now that you have some tunes going, you might feel like messing around with some insert processes and
see what this thing can really do. To get started, go to your Host input strip and click in an Insert slot. The
dialog that appears list categories for "Plugin", "Macro", "Graph" and "I/O".
Figure 4.13: Mixer Strip Insert: Plug-in selector
• Plugin: All the basic stand-alone processors, including EQs, dynamics, reverb, distortion and some
common processor "building blocks".
• Macro: Most are essentially presets of more complex process chains in a DSP Graph. Feel free to use
these as a starting point to create your own personal custom signal processors. The Reverb macros
can not be represented as modules in a normal graph, and can not be modified as-is.
