 Why does the playback engine on my Pro Tools system have choices for same ...
|
| Why does the playback engine on my Pro Tools system have choices for same number of voices but different number of DSP chips? Why would I want to use more DSPs for the same number of voices? |
This provides some flexibility in how the DSPs are managed.
The selections using more DSPs for the same number of voices put less strain on the PCI system – which could help to avoid DAE error -6042 (PCI “too slow”) during play/record.
If you have a system that is having trouble with -6042 errors, then increasing the number of DSPs handling the same total voice count can help. Of course, using more DSP for the streaming engine means fewer DSPs available for running TDM plug-ins.
If you are not running into -6042 errors, then using the maximum “voices per DSP” (fewest number of DSPs) is the most efficient use of DSP resources.
The additional DSP settings are also recommended with systems on an Avid Unity Network.
Examples:
Pro Tools HD
96 voices 2 DSP
96 voices 3 DSP (less prone to -6042 errors, but 1 less DSP available for Plug-Ins)
Pro Tools MIX
64 voices 2 DSP
64 voices 4 DSP (less prone to -6042 errors, but 2 less DSPs available for Plug-Ins)
[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]
|
|
|
Type 2 crashes in Pro Tools while using Unity workspaces, also sometimes ...
|
| Type 2 crashes in Pro Tools while using Unity workspaces, also sometimes the workspaces will dismount randomly. |
This was caused by having CL2 and CL3 memory in a Quick Silver G4. Use either CL2 or CL3 but not both in the same machine.
CL stands for CAS (Column Access Strobe) Latency, which is the amount of time that it takes to retrieve data from the module. CL2 and CL3 refer to the amount of clock cycles that it takes before the initial stream of data is sent. CL2 modules wait two clock cycles before sending data. CL3 modules wait three clock cycles before sending data. CL2 modules are faster since they only wait two clock cycles and therefore are usually more expensive. Some systems may require either CL2 or CL3 memory.
[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]
|
|
|
When running Pro Tools 5.1.3 in conjunction with Unity Media Net 2.2.1, ...
|
| When running Pro Tools 5.1.3 in conjunction with Unity Media Net 2.2.1, & the associated JNI fibre channel card extensions on Mac OS 9.x, the system enlesslessly searches or quits when accessing the 'Drives and Volumes' section in Apple system profiler. |
workaround: if not using any Unity storage, quit Pro Tools, & unplug the connection to the fibre channel card.
Unity bug 22093
[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]
|
|
|
What settings should be used when exporting from an OMF from an AVID system ...
|
| What settings should be used when exporting from an OMF from an AVID system and converting it with OMF Tool (v2.0.8)? |
The following export settings to be used on the Avid side:
- OMF 2.0
- Embedded Audio
This is the safest and most reliable method to export. Unless you have an AVoption or AVoption XL on your Pro Tools system, the Avid editor will need to remove any video tracks from the Avid sequence before exporting, especially if you are using OMF Tool. OMF Tool can't handle seeing video tracks.
Also, choosing SDII files is not necessary and, in fact, if the Avid is on an Avid Unity Media Net system they won't want to use SDII files. AIFF or .WAV files will be fine for you as long as you are using Pro Tools 5.1 or greater.
[Page View]
|
|
|
On a Unity system, opening a workspace at the desktop level causes the ...
|
| On a Unity system, opening a workspace at the desktop level causes the desktop icons to disappear and the system to freeze. |
In this case a bad JNI Fiber Channel card was causing the problem. Replacing the card resolved the issue.
[Page View]
|
|
|
Importing an OMF composition into Pro Tools posted the error message: ...
|
| Importing an OMF composition into Pro Tools posted the error message: "Could not complete the open session command because invalid global name string read in container 'TU116. Open_protools.omf' in OmfsOpenFile." |
This can be caused by a bad JNI Fiber Channel card. Contact technical support.
[Page View]
|
|
|
