A Workaround for Using Atmosphere/Trilogy on an Intel
Mac
INTRODUCTION
This workaround is recommended for power users with experience
in audio and MIDI routing that already own Atmosphere
and Trilogy. We are providing this
information as a short-term workaround for existing users who wish to be able
to continue using their Atmosphere and Trilogy virtual instruments on new
Intel Macs while we are developing our long-term Intel Mac solutions for these
instruments.
These guidelines present a basic overview of how your system
can be set-up to use any non-Universal Binary virtual instrument VST/AU plug-ins
in an Intel Mac computer.
THE CONCEPT
You can think of this approach as like having your Atmosphere
and Trilogy instruments in an outboard rack of hardware MIDI instruments triggered from your sequencer, but with everything
happening within one computer.
It works like this:
Atmosphere and Trilogy are Power PC-based VST/AU plug-ins
that can therefore be loaded into a stand-alone Power PC-based VST/AU host
application. On an Intel Mac, the stand-alone host application and the plug-ins
would then be running automatically in what Apple calls “Rosetta emulation”
mode.
While this “Rosetta” approach is not recommended for your
primary DAW application, a simple, inexpensive stand-alone host application
will work fine running in Rosetta emulation mode, and has the advantage of
being able to host any non-Universal Binary virtual instrument plug-ins -
including our Atmosphere and Trilogy UVI engine-based instruments. We’ve tested
and can recommend Steinberg V-Stack and RAX for use as stand-alone host applications.
More info on where to get the correct versions is located here.
It is then possible to trigger the plug-ins running in
the stand-alone host application from your Universal Binary DAW application
via a MIDI IAC bus in CoreMIDI.
Additionally, the audio outputs of the stand-alone host
can be routed to your audio interface for monitoring or back into your DAW
application for printing to audio tracks.
This setup will allow the Intel Mac/OSX user to compose
entirely with Atmosphere and Trilogy on a single computer.
PROS AND CONS
Here are some of the Pros and Cons to using this particular
workaround:
Pros
- The ability to create new compositions using Atmosphere and Trilogy on Intel Macs in OSX.
- No need to use another computer to host the plug-ins.
- No need to use Windows XP in Boot Camp to host the plug-ins.
- Good solution for users and composers that work with a “template” approach to their system.
- Viable solution for live performance use
- Once it is configured properly - a stable and reliable workaround.
Cons
- Atmosphere and Trilogy need to be operated and run in
a separate stand-alone host application, which is not as convenient as using
native plug-ins within the DAW.
- Saving twice - Atmosphere and Trilogy plug-in settings
are not saved within the Universal Binary DAW application song/session file,
but need to be saved from the stand-alone host application as a separate file.
- No compatibility with songs/sessions created on Power
PC-based Macs (G3/G4/G5).
- In some systems, users may need to compensate for latency
issues.
Remember that these are general guidelines for a short-term
workaround for using Atmosphere and Trilogy on Intel Macs. The application of these guidelines requires
that you are knowledgeable of the audio and MIDI routing
capabilities of your audio interface and the DAW application.
Next we are going to show you the principles behind routing
the MIDI and audio in your system to make this work.
MIDI ROUTING
First, it is necessary to create an IAC bus within Core
MIDI (learn how to set up an IAC Bus). This will allow MIDI communication
between the DAW application and the stand-alone application hosting Atmosphere
and Trilogy.
Once this has been done, you can simply create a MIDI track
within the DAW application and set the MIDI output of
that track to trigger the IAC bus. Within
the stand-alone host application, assign the MIDI input
of Atmosphere or Trilogy to the same IAC bus. You can use different MIDI channels
to trigger up to 16 instances of plug-ins that are set to receive on the same
IAC bus. You can also use multiple IAC busses for access to even more plug-in
instances.
NOTE: Be careful in
your routing to avoid MIDI feedback loops.
AUDIO PLAYBACK
Once your MIDI set up is configured
to trigger the plug-ins from your DAW application, you’ll be able to hear
the plug-ins by configuring the audio drivers for both applications. If both applications are set to use the same
audio driver and physical outputs, you’ll be able to simply hear the audio
output of the DAW application and the plug-ins audio coming from the stand-alone
host application simultaneously.
This is a good setup for composing or live performance,
since there are no significant latency issues to deal with if both applications
are set to the same audio buffer size.
(For host-specific issues, please see the links at the
bottom of this page).
MONITORING/RECORDING
VIA THE DAW
If you have the need to monitor or print the audio output
of the plug-ins via your DAW application, you’ll need to physically route
the audio from the stand-alone application to the DAW inputs. There are many ways to set up the audio routing
to accomplish this, which vary depending on the type of audio interface and
the DAW application you’re using.
NOTE: Be careful in
your routing to avoid audio feedback loops.
The following steps show one example of setting up the
audio system routing that is effective:
-
Set the audio driver of the stand-alone host application
to the Mac’s Built-in Output and set your DAW application audio driver to
an external audio interface.
-
Connect the digital output from your computer into the
digital input of your external audio interface.
- Create a stereo audio input track in your DAW application
and set its input to the digital input of your external audio interface.