 When recovering a failed drive in an Avid Unity MediaNetwork environment, ...
|
| When recovering a failed drive in an Avid Unity MediaNetwork environment, is it recommended to do an Online, Offline, or Auto recovery while Pro Tools is connected to the system? |
In most Unity MediaNetwork environments, there is at least one spare drive for every drive size in the JBOD. If a drive fails, Avid allows three possible ways to recover the failed drive (i.e. swap in a spare):
1. Online Recovery - This is done manually by the administrator on the Unity File Manager. It can be done while clients continue to work on the system, however, it can degrade performance for all clients and takes longer.
2. Offline Recovery - This is done manually by the administrator on the Unity File Manager, but it is required that all clients are offline and thus, not accessing the Unity system.
3. Auto Recovery - When this is enabled on the Unity File Manager, a failed drive is automatically recovered by the spare. This can happen while clients are online and working and can thus, degrade system performance. For this to work correctly, all drives in the drive set should be the same size. Digidesign recommends that this option NEVER be enabled.
[Page View]
|
|
|
"Could not complete the Import Tracks command because an assertion occurred ...
|
| "Could not complete the Import Tracks command because an assertion occurred sys_fileutilsmacos.cpp, line 46" error when attempting to import an OMF with Digitranslator 2.0 via Import Tracks. |
In one Avid Unity MediaNet configuration, this was resolved by reinstalling the Unity client software on an Avid Symphony system which was exporting the offending OMF.
[Page View]
|
|
|
Avid Unity MediaNetwork File Manager won't start its service.
|
| Avid Unity MediaNetwork File Manager won't start its service. |
In the Setup Manager, check the minimum number of missing drives allowed setting. If this is, for instance, set to 1 and 2 drives are either missing from the JBODs or not functioning, then the File Manager will not start its service.
[Page View]
|
|
|
When running Pro Tools 5.1.3 on Unity MediaNet 2.2.1 with a JNI fiber ...
|
| When running Pro Tools 5.1.3 on Unity MediaNet 2.2.1 with a JNI fiber channel card on Mac OS 9.x, Apple system profiler hangs or quits while accessing 'Drives and Volumes'. |
This is a known issue.
workaround: If not using any Unity storage, quit Pro Tools, & unplug the connection to the fiber channel card.
[Page View]
|
|
|
When booting up a Mac with Avid Unity installed the Avid Startup extension ...
|
| When booting up a Mac with Avid Unity installed the Avid Startup extension flashes a couple of dialogue boxes (stating that it is flashing the Rom on the Meridien card) and then reboots. This will continue in a loop indefinitely until you boot up with extensions off or turn off the computer. |
The Avid Startup extension should not be installed on a Pro Tools Unity client, it is only for Media Composer clients. This extension was most likely installed during the Unity client install by selecting MediaComposer instead of "MediaNet for Pro Tools client."
[Page View]
|
|
|
What is fixed with DAE 5.1.3cs1?
|
| What is fixed with DAE 5.1.3cs1? |
DAE 5.1.3cs1 avoids a situation that could occasionally cause system crashes when using ATTO SCSI drivers and local storage. This fix will seriously degrade performance with Avid Unity MediaNet storage systems and should not be used with those systems.
Who Should Use This Update?
This update should be used only by Pro Tools 5.1.3 users with ATTO SCSI cards for local storage who have experienced random system crashes with Pro Tools. This update should NOT be used by anyone connected to an Avid Unity MediaNet storage system.
[Page View]
|
|
|
DAE 5.1.3cs1 for Pro Tools 5.1.3 with ATTO SCSI Drivers
|
| DAE 5.1.3cs1 for Pro Tools 5.1.3 with ATTO SCSI Drivers |
What’s Fixed in DAE 5.1.3cs1?
DAE 5.1.3cs1 avoids a situation that could occasionally cause system crashes when using ATTO SCSI drivers and local storage. This fix will seriously degrade performance with Avid Unity™ MediaNet storage systems and should not be used with those systems.
Who Should Use This Update?
This update should be used only by Pro Tools 5.1.3 users with ATTO SCSI cards for local storage who have experienced random system crashes with Pro Tools. This update should NOT be used by anyone connected to an Avid Unity MediaNet storage system.
Where Can I Get This Update?
DAE 5.1.3cs1 has been posted in the Support/Downloads/DAE-DSI section:
http://www.digidesign.com/download/daedsi.html
Download Includes:
DAE 5.1.3cs1 Application
DAE 5.1.3cs1 Read Me.pdf (with details & installation instructions)
[Page View]
|
|
|
Why is DigiTranslator built into Pro Tools TDM v5.1.3 but not included ...
|
| Why is DigiTranslator built into Pro Tools TDM v5.1.3 but not included with the Pro Tools|HD v 5.3 release? |
It is not included in Pro Tools 5.3 because it is considered part of the "Interoperability" suite, along with AVOption|XL, FilmFrame, PostConform, and Unity MediaNet support. Because these features are post-centric, we hold them out of "initial" releases so that we can get the initial releases out to the masses earlier, and to give us more development time to make sure they work well straight out of the box. We understand that the delay is not desirable, but we know how critical post-production schedules are, so we include these items in a follow-up release that allows us to completely focus on these features.
NOTE:
Your current authorizations for DigiTranslator 2.0 will be valid for Pro Tools|HD.
[Page View]
|
|
|
Pro Tools 5.1.3 crashes when scanning all Unity workspaces in the 'where ...
|
| Pro Tools 5.1.3 crashes when scanning all Unity workspaces in the 'where is.." dialogue. |
This is a problem with versions of Unity MedieNet lower than 2.1. Updating to MediaNet 2.1 or higher should resolve this issue.
[Page View]
|
|
|
How to run Pro Tools 5.1.3 and Pro Tools 5.2 on the Same System?
|
| How to run Pro Tools 5.1.3 and Pro Tools 5.2 on the Same System? |
Pro Tools 5.1.3 and 5.2 each contain unique features. Pro Tools 5.2 provides DigiStudio online collaboration capabilities, while Pro Tools 5.1.3 has enhancements for AVoption|XL, MediaManager, DigiTranslator, and Avid Unity(tm) MediaNet users.
Both Pro Tools 5.1.3 and 5.2can reside on the same hard drive, but cannot be launched at the same time.
To install 5.1.3 and 5.2 on the same hard drive:
Run the installation disk on a machine currently installed with the other version.
In this case, running the installation disk will not disrupt the previously installed version.
Both versions will be added to the Pro Tools application folder (with version numbers clearly stated) within the Digidesign folder. If both versions of Pro Tools are installed on your hard drive, you should not open a session by double-clicking on it (you will not be able to choose which version of Pro Tools you want to work with).
To open a session when both versions (5.1.3 and 5.2) are present:
Launch the Pro Tools version that contains the features you intend to use, then open thesession through the file menu. Or just drag and drop your session onto the icon of the desired version.
If you open and save a Pro Tools 5.2 session in Pro Tools 5.1.3:
You will lose the Local > Online track associations.
If you open a Pro Tools 5.1.3 session in Pro Tools 5.2:
You will loose the ability to work with the DigiTranslator option, MediaNet storage and 24P video clips.
You will be unable to play audio imbedded in an OMFI sequence file.
Pull-downs will only be allowed at the standard frame rates.
Pro Tools AVoption and AVoption|XL users:
You will have the full capabilities of your video system while using Pro Tools 5.2 online with DigiStudio,
with the exception of 24P support.
[Page View]
|
|
|
