The MIOConsole3d Application
194
“Open…” is a “smart” function in that it automatically analyzes the file that you have selected,
compares it to the current MHLink domain and determines how best to open it. When you are
working with a single 3d box or a stable multi-box rig, you'll just use “Open…” as usual, and it will
bring up your mixer and monitor configurations immediately as usual.
If you have changed your MHLink domain by adding or removing 3d boxes since you saved the
file, that tells the Console that some I/O routes are different between the file being loaded and the
current system setup, and opens the Box Mapping window so you can decide how you would like
to load the file.
•
“Open Console File and Replace State…”
(default:
⇧⌘O
)
In special cases, it may be desired to simply load all contents of a saved ‘.cnsl3d’ file exactly as it
was saved, with no “re-mapping” from the saved Domain to the currently running system Domain.
The
“Open Console File and Replace State…”
command completely replaces the current system state
in MIOConsole3d with the contents of the file, asserts the updated configuration on any attached
boxes, and loads the default state for any current boxes that were not in the file.
All domains saved within the file will be loaded as ‘offline domains’ in the Console System Status
Pane. Selecting each domain will reveal the entire signal path of every 3d box that domain.
Note:
This command is frankly overkill for normal production scenarios. However, some
users have found it handy for examining all the stored information in a saved file verbatim
(including Monitor Controller configurations and room tuning graphs), or to perform a
full system reset to a specific configuration as part of a calibration or troubleshooting
procedure.
That said, it won‘t hurt anything to play with it. Even if it doesn’t behave how you expected
for whatever reason, you can always just open a known-working MIOConsole3d file and
get right back to work.
•
“Import Console File and Map…”
(default:
⌥⌘O
) will display the mapping window, even if MIOCon-
sole otherwise thinks that it can map or replace the data without user intervention. This is generally
used for importing ‘.cnsl3d’ files from a different multi-box MHLink system, or if you are opening an
older ‘.cnsl3d’ file and have made changes to the I/O routing of your system since you last opened it.
Since “Import Console File and Map…” directly opens any MIOConsole3d file into the Box Mapping
interface, it is especially handy for checking the contents of a saved file.
As always, once you have examined the contents of an imported file, you can ‘Cancel’ the import
without committing any changes.
Box Mapping:
How it works
The Box Mapping interface walks you through the process of translating all box settings, routing assign-
ments and mixer parameters from a saved console mixer file to your local 3d system. There are three stages
to the process: first, selecting the Domain to import, then matching which source boxes will map to each
box in your domain, and finally you can fine-tune individual routings as necessary.
This sounds like real work, but in practice the Console3d software makes importing even the most complex
systems easy. To begin with, most MHLink systems consist of a single domain, which makes deciding which
domain to map to kind of a no-brainer.
