 I get a "catastrophic error" while launching Pro Tools v6.7.
|
| I get a "catastrophic error" while launching Pro Tools v6.7. |
Try disabling the Data Execution Prevention (DEP)
To disable DEP follow these steps:
Right-click "My Computer".
Select "Properties".
Select the "Advanced" tab.
Under "Startup and Recovery" category click the "Settings" button.
Under the "System startup" category, click on the "Edit" button, which will open the system startup parameters in Notepad. Change NoExecute=Optin or Optout to NoExecute=AlwaysOff.
Close window.
Click OK and say Yes to saving the settings and restart your computer.
[Page View]
|
|
|
Machine Track Arm Window GUI corruption
|
| Machine Track Arm Window GUI corruption |
This is a problem seen in Pro Tools v6.4.
This problem was seen when having a Sony PVW2800 Node selected. However the problem will occur when moving from machine profile to machine profile in the Nodes list.
To bring back the Track Arming layout and GUI back to what it should be you will need to reselect the machine again you are controlling.
This issue was also seen with DA88 and PCM 7030.
[Page View]
|
|
|
Sony PMC7030 has incorrect Track Arming Layout in Pro Tools track arming ...
|
| Sony PMC7030 has incorrect Track Arming Layout in Pro Tools track arming window |
This is a known issue with Pro Tools v6.4 in Windows XP.
If you select PCM 7030 from the nodes list it will present you with tracks 1-8. This is a stereo machine.
The first two tracks should be functional.
[Page View]
|
|
|
Why is the Apple G5 second generation single 1.8 GHz Power Mac G5 (model ...
|
| Why is the Apple G5 second generation single 1.8 GHz Power Mac G5 (model M9555) NOT qualified with Pro Tools|HD or HD Accel systems? |
Digidesign did not quality the 2nd generation Single 1.8 GHz Power Mac G5 (model M9555), because we were unable to achieve maximum tracks counts with this model computer. With the G5 model M9555 you should expect approximately 20% less track count than you would get using a FireWire Drive.
http://www.digidesign.com/compato/osx/hd/drives.cfm
[Page View]
|
|
|
The error message: "could not save 'Session Name' because file is busy ...
|
| The error message: "could not save 'Session Name' because file is busy -47 while deleting randomnumbersandletters while moving randomnumbersandletters to ""Session Name"". |
In one case, the workaround was to Save Session Copy In and include all audio files.
Although this was a workaround, the cause was most likely the SATA RAID boot drive configuration in the G5 Dual 2gHz Mac.
[Page View]
|
|
|
When you bounce selected parts of a stereo audio file the end and beginning ...
|
| When you bounce selected parts of a stereo audio file the end and beginning will not be bounced correctly |
This is a bug that occurs in PT 6.4 and 6.7, to be fixed in future release of Pro Tools.
A workaround would be to slice the whole file into single files, record it in Pro Tools. Then use the file created during recording.
If the sample rate and bit depth needs to be changed import the file into a session with the appropriate settings.
[Page View]
|
|
|
Pro Tools v6.7cs7 breaks the possibility of creating shortcuts for certain ...
|
| Pro Tools v6.7cs7 breaks the possibility of creating shortcuts for certain menu items. (This is referring to the OS X keyboard shortcut feature) |
This problem has been fixed in Pro Tools v6.7cs8.
Here's where you can download the cs update:
http://www.digidesign.com/download/cs/
On launch, Pro Tools would remove any shortcuts the user had set up in the System Preferences to handle Pro Tools menu items. They would still be visible in the System Preferences, but they would have no effect on the running Pro Tools instance. A menu item either (a) had an existing shortcut or (b) had its name changed during program execution.
[Page View]
|
|
|
In OS 10.3.1 (Mac G5) using UL3D SCSI config: Pro Tools hangs during launch ...
|
| In OS 10.3.1 (Mac G5) using UL3D SCSI config: Pro Tools hangs during launch if formatted SCSI disks contain ghosted bogus volumes created by OS X.2/X.3 Disk Utility. |
This is a known issue in Pro Tools v6.2.3. There is no solution at this time.
[Page View]
|
|
|
When using the signal generator plug-in the user makes a blank selection, ...
|
| When using the signal generator plug-in the user makes a blank selection, and then hits 'process' in signal generator, Pro Tools throws a 'no audio is selected' error. |
Signal Generator has always been the one plug-in that only requires a selection (not a contained region) to process, this broke in Pro Tools 6.1
workaround: select 'create continuous file' in the AudioSuite window.
[Page View]
|
|
|
frequently on my machine, initiating playback results in a 3-10 second ...
|
| frequently on my machine, initiating playback results in a 3-10 second SWOD pause, and then no playback; the cursor returns to normal, restoring control to the user, but no playback or DAE error communicating the termination of playback. |
This was reported to happen on a G4 computer that only had 256 megs of ram. Adding more ram so that it was at the 512 megs recommended, solved this problem.
Please check the compatibility page at
www.digidesign.com/compato
for information on memory requirements for your computer and the version of Pro Tools you are running.
[Page View]
|
|
|
