Pro Tools HD 7.0 Win Support

       
  Compatibility     Downloads     Answerbase     Tech Docs  
When trying to open the PowerMix deck in Pro Tools, the DAE Playback Buffer ...
 
When trying to open the PowerMix deck in Pro Tools, the DAE Playback Buffer keeps resetting itself to 0.
As of DAE/DSI 3.1, if a Disk I/O is installed, the DAE Playback Buffer will always reset itself to 0. To switch to PowerMix deck with a Disk I/O installed in the machine:
- Launch DAE and switch the Playback Buffer.
- Quit DAE and launch Pro Tools, holding down the N key, and select the PowerMix engine.

This way the Playback engine dialog will come up and the higher DAE buffer setting should remain.

[Page View]
 
MIDI Controllers (CS-10, DC-16, MM-16, PC-1600, etc.) are not available ...
 
MIDI Controllers (CS-10, DC-16, MM-16, PC-1600, etc.) are not available in the MIDI Controller section of the peripherals window in Pro Tools 4.1.
- Incorrect version of the controller files in the Controllers folder within the DAE Folder. Version 4.0 and 4.01 of Pro Tools installs, for example, version 1.0 of the CS-10 controller document. Pro Tools 4.1 installs version 1.1 of the CS-10 document. Pro Tools 4.1 will not recognize the earlier versions of the controller documents.

- Controllers folder and/or its contents missing from the DAE Folder (reinstall from the Pro Tools CD).

[Page View]
 
"Could not allocate space for recording" when attempting to record in ...
 
"Could not allocate space for recording" when attempting to record in Pro Tools or when trying to record from Internal CD-ROM (in PowerMix mode).
- Hard disk is full, set Disk allocation (under the Setups menu) to a drive that has available space. (If it's a Project or Core system the drive(s) must be on the Digi SCSI bus)

- For Internal CD Rom recording: create a new session in Powermix mode (close all Pro Tools sessions, change playback Engine and then create new Pro Tools session) then go through the procedures necessary for recording from the internal CD Rom into Pro Tools.

"Transferring audio from a CD into Pro Tools 3.2-3.22 is a real-time process using Sound Manager, DAE PowerMix,and the Apple CD Audio Player. To record an Audio CD into Pro Tools:

In the Sound Control Panel:
- Select "Sound In"
- Click the "Options" button
- Select "Internal CD"
- Enable "Playthrough" then click OK
In Pro Tools:
- Select DAE PowerMix in the Playback Engine dialog
- Enable "Active In Background" in the Options menu
- Record enable 2 tracks in Pro Tools (the CD will be Input 1 and 2)
- Start recording in Pro Tools
In the Apple CD Audio Player:
- Open the Apple CD Audio Player and start playback of the CD

(Note: This functionality was tested with an Apple 300 internal CD ROM Drive.) [Page View]
 
Program Error while trying to do a bounce to disk on a PT|24 system.
 
Program Error while trying to do a bounce to disk on a PT|24 system.
- Disk Cache (in the Memory CDev) should be 512K or lower (128K is optimal). Restart the CPU after changing the cache setting.

- DAE Playback Buffer set too high. In the cases where this was reported, a setting of 8 was being used. Lowering to 2 or less fixed the problem.

- DAE prefered memory set too low.

[Page View]
 
No audio when playing a session, or Mac freezes when instantiating a Plug-In ...
 
No audio when playing a session, or Mac freezes when instantiating a Plug-In on a DSP Farm PCI/II in a PTIII PCI system (PT 4.0).
This could be caused by running DigiSystem INIT (DSI) 3.1.1 or earlier with a rev II DSP Farm. Although there is no functional difference between DSP Farm revs, DSP Farms that have serial numbers starting with "FG" require DAE/DSI 3.2 or later for proper operation.

Note: The Magma 7 Slot Chassis is not supported by DSI 3.2 or 3.2.1. Magma 7 Slot Chassis users should be running DAE/DSI 3.1.1 or 3.2.3.

[Page View]
 
Random clicks in playback.
 
Random clicks in playback.
This appears to be an issue with Pro Tools 4.1, DAE/DSI 3.2, regardless of track count.

Workaround is to switch to 44.1k sample rate.

[Page View]
 
DAE error -9117 when launching Pro Tools 4.1.
 
DAE error -9117 when launching Pro Tools 4.1.
This was reported on a system that contained both a "mixer plug-in" from 4.0 and a "16 bit enhanced mixer plug-in" from 4.1 in DAE's Plug-Ins folder.

[Page View]
 
How to sync Pro Tools 4.x to Performer, MOTU sequencers.
 
How to sync Pro Tools 4.x to Performer, MOTU sequencers.
- Download and install FreeMIDI 1.3.1 or higher from www.motu.com
- The FreeMIDI and OMS Emulator extensions must be in the Extensions folder. If FreeMIDI version 1.33 or higher is installed the OMS emulator extension is not needed.
- Disable the Open Music System Extension

In FreeMIDI Setup:
1) In the FreeMIDI Preferences window, enable "FreeMIDI applications only" and "Inter-application MIDI".
2) If version 1.32 or higher FreeMIDI is being used there is a check box in the prefs called "emulate OMS" that needs to be checked.

In Performer:
1) Always launch Performer first. If DAE loads then select "MIDI only" from the Basics menu. DAE will quit.
2) In Receive Sync window (Basics menu), select "Inter-application MIDI" and in same window select "MTC, DTL or DTLe".
3) Enable "Slave to external sync" in Basics menu.
4) Set desired frame rate from Basics menu.
4) Press the Play button on the transport - it should flash, indicating that it's waiting for MTC from Pro Tools.

In Pro Tools:
1) In the Session Setup window, set "Output Time Code" pop-up to Digital Performer.
2) Verify that the Frame Rate, Format and Start Time are the same in both Digital Performer and Pro Tools.
3) Starting Pro Tools will generate MTC, which will trigger Performer.

[Page View]
 
DAE error -6029
 
DAE error -6029
Peripheral isn't connected. Check the cable connection and be sure that it is oriented to connector correctly. We have had a few reports where the cable was inserted up-side-down.

[Page View]
 
DAE error -6034.
 
DAE error -6034.
PCI traffic is too heavy to send record overview data. This could be caused by other PCI cards, like video or SCSI accelerators.

Set SCSI accelerators to 10 MB/sec or less. If the problem persists, try recording (or bouncing) fewer tracks.

[Page View]
 

Prev  
Support Search
Search
  Next