Important Notice:
Although XO Wave will continue to be available for some time,
it will be discontinued as we prepare to bring you the next generation
Digital Audio Workstation.
The new software we are developing is called
Xonami and it will have
many, but not all, of the features of XO Wave.
A discount upgrade path will be available
for users who purchased XO Wave September 1st, 2010.
We realize that
there are few professional CD mastering options with the full range of capabilities offered
by XO Wave, so we will continue to offer the package as long as possible. However,
please keep in mind that as discontinued software:
- This site may not contain up-to-date information.
- Technical Support will be discontinued on November 30th.
For up-to-date information about our upcoming software, please join our
mailing list.
XO Wave: Running under Mac OS X 10.5 Leopard
Mac OS X 10.5 Leopard makes many changes to the behaviors of applications running under it. Among the most notable are the new application firewall, and different Dock / application switcher behavior. Note that beta versions of XO Wave had additional problems with Leopard, so make sure to upgrade if you are still running a beta version of XO Wave.
Mac OS X 10.5 Leopard uses a new "application firewall", which restricts which applications are permitted to listen for network traffic. Because XO Wave is designed as a client-server application, able to run on and take advantage of multiple computers (although this is an uncommon configuration), it is affected by the application firewall. Specifically, when launching XO Wave for the first time, you may see a dialog box asking if XOmux (or "XO Wave.app") should be allowed to accept incoming network connections. To use XO Wave, you must Allow this request; after that, you should not see the dialog again until you reinstall or upgrade XO Wave.
In Leopard's Dock and application switcher (invoked with Command-Tab) you may see XO Wave appear twice -- this is normal behavior for Leopard, and can be ignored. Note that XO Wave 1.0.3 no longer exhibits this behavior.
|