Avid Unity MediaNetwork Known Issues
AVoption|V10 does not support MediaManager
AVoption|V10 and Pro Tools 6.3/6.4 do not support Avid Unity MediaManager. Log in to Media Manager is not listed in the File menu (Item #44243)
AvidComm Fake Comm Disk
The Device Manager will ask you to install the driver for the AvidComm Fake Comm Disk on a Windows machine if you are connected to a running Unity Network and the Unity Client is not installed on the client CPU. Once you install the Unity Client you should no longer see this message.
ATTO Phantom Device
The ATTO phantom device will appear if the fibre channel card does not find any devices (e.g., drives) on the fibre channel chain. If you are prompted to install the ATTO phantom device, you can simply point the Device Manager to the Expressfc.inf file (the installer) for the ATTO card.
AvidStartup Extension Incompatible
Pro Tools users should be sure that the AvidStartup extension is not installed in their Startup Items folder (OS9) or at the root of System32 on Windows XP where it is installed as a Service. This can effect the burst rate settings on an ATTO SCSI card.
Mac OS ROM v7.91
Mac OS ROM v7.91 can cause type 10 errors when working with MediaNetwork. Version 7.91 was installed with Mac OS 9.1 installer v1.3. Any other installer will install a compatible version of OS ROM.
To check which OS ROM version you have installed, launch Apple System Profiler and check System Profile > Production Information > Mac OS ROM file version. Note: Some early versions of MediaNet software are incompatible with Apple System Profiler. If Apple System Profiler unexpectedly quits, use your extensions manager to disable the Unity extension and reboot your computer. Simply disconnecting the fibre channel cable before launching Apple System Profiler may also help.
Open Session or New Session Dialog Slow to Appear
On a Pro Tools Avid Unity MediaNet client, the first time you choose File > Open Session or File > New Session in Pro Tools, it may take a long time to for the Open Session or New Session dialog to appear, or a DAE 9019 error may occur the first time play or record is attempted. This will only occur the first time the Unity Volume is accessed after you boot or reboot your computer. The next time you open a session or create a new session, the wait should be much shorter and you should not encounter a DAE 9019 error.
When Using Open Ended Record on Unity, the Drives Session Files Cannot be Saved if Drives are Full
If you record audio until your Unity drives are full, you may not be have adequate drive space available to save your session file. Under Preferences > Operations, set your Open Ended Record Allocation to an amount that fits on your assigned drives.
2 GB provides about 6 hours per track.
Open-Ended Recording or Quick Punch on Unity Results in "Could not Allocate Space for Recording" Error (Item #38028/38110)
QuickPunch or open-ended recording on Unity pre-allocates entire volumes. Because of this, it strongly recommended that you use bounded recording instead of open-ended recording when recording to Unity workspaces. It is also recommended that you specify a selection for bounded QuickPunch rather than using open-ended QuickPunch. If you must use open-ended QuickPunch, you should specify the smallest usable duration for your anticipated QuickPunch needs in the Open-ended record allocation preference (Setups > Preferences > Operations). If you encounter a "Could not allocate space for recording" warning, you will need to save your session, and then close it and re-open it. You may also want to delete any unnecessary files on the Unity workspace.
MacDrive 6 Damages Unity Volumes
If you have a Windows XP client attached to Unity volumes, do not install MacDrive 6. This application will prompt the user to update the Unity volumes whenever they are mounted. Allowing MacDrive 6 to update them will result in complete data loss for the Unity volumes, and they will need to be rebuilt.
HP Workstation xw8000 Now Supported - Warning About Early Models
Q: Now that the HP Workstation xw8000 is supported, are all models the same?
A: No, definitely not. Some early models of the HP Workstation xw8000 are incompatible with Pro Tools|HD and Pro Tools|HD Accel systems, and can cause damage to Avid Meridian cards.
Digidesign has officially qualified two configurations of the the HP Workstation xw8000 for use with Pro Tools|HD and Pro Tools|HD Accel for local use and with Avid Unity MediaNetwork. These dual 2.80 GHz and dual 3.06 GHz configurations are only available through authorized Digidesign dealers.* We cannot qualify any HP xw8000 that is purchased through other channels. Units not purchased through Digidesign dealers may have several problems:
Please see the following page for more information on officially qualified models: