I have a Mac Pro 1,1 up and running on OS X El Capitan 10.11.6. Video card is a ATI Radeon HD5770. I've just installed PT 12.8 and all new codecs and drivers on this fresh SSD. I've also tried PT 12.8 on the same machine running Yosemite (OS X 10.10) on another SSD and video engine doesn't work. Video engine won't load after trying to turn it on in playback engine.

Same machine running Yosemite (OS X 10.10) and PT 12.7.1 and video Engine works fine. Is the video Engine vastly different in PT 12.8??? I've even left it over night trying to load the video engine and still won't load. Can anyone help? I have a Mac Pro 1,1 up and running on OS X El Capitan 10.11.6. Video card is a ATI Radeon HD5770. I've just installed PT 12.8 and all new codecs and drivers on this fresh SSD.

Take a look at CUDA compatible GPUs for the Mac Pro and Abandoning Apple 'Blessed' GPUs. I recently had to replace a second dying NVidia 8800 GT in my Mac Pro (early 2008) but decided to stick with an Apple card. Most of the non-Apple branded cards will not work until the machine is past the boot volume selection screen (if you need it) and I. Oct 7, 2015 - Installing both Yosemite and El Capitan was trivially easy following the instructions on. Display a boot screen on page 1 of the MacPro 1,1/Yosemite thread. After reading every post in the 31 page, 7xxx rom creating test, I'm. The way to get the best one for your card is to get it FROM YOUR CARD.

I've also tried PT 12.8 on the same machine running Yosemite (OS X 10.10) on another SSD and video engine doesn't work. Video engine won't load after trying to turn it on in playback engine. Same machine running Yosemite (OS X 10.10) and PT 12.7.1 and video Engine works fine. Is the video Engine vastly different in PT 12.8??? I've even left it over night trying to load the video engine and still won't load. Can anyone help?

Your problem is probably due to you're running an OSX version that is not supported in the least for a MacPro 1,1. The latest supported with the efi update is OSX 10.7.5 aka Lion. I spoke to Daniel Lovell (Fantastic guy!) from Avid in person at SMPTE Sydney and he mentioned trying a couple of things; 'Go to /Users/Shared Delete the AvidVideoEngine folder Then try and launch the Video Engine again from within Pro Tools: Go to Setup->Playback Engine Check Enable Video Engine Click OK' 'The Pro Tools Video Engine does not launch, or Pro Tools hangs after creating a video track. This may be caused by having a '/' character in the name of a mounted storage volume.

To resolve the issue, rename the volume and remove the '/' I also found this; 'Try this: 1. Launch Pro Tools 2. Go to Setup/Playback Engine 3. Choose different hardware in pop-up menu (for example from HDX to ProTools aggregate I/O - it is important to make a change) 4.

Uncheck all checkboxes in Playback Engine window. Enable Video Engine 6.

Click OK (Video Engine should launch properly now) 7. Go to Setup/Playback Engine again 8.

Choose desired hardware and other options. If you'll find Video Engine disabled turn it on again. 'Try holding the 'n' key as soon as the Pro Tools splash screen appears during launch. Check your current Playback Engine and make sure the proper device is selected.' 'his can occur when importing video, opening a session with video or launching Pro Tools from a session that has video.

This can be caused by a conflict with drives or media mounted on the system or a corrupt Workspace.wksp file. Start by deleting the Workspace.wksp file: Navigate to /Users/Shared and move the Workspace.wksp file to the trash. To troubleshoot the issue, un-mount any unneeded drives or storage media. This includes hard drives, flash drives, CD/DVD/BluRay media, or devices with storage like Mp3 players or cameras.

Try the session or try importing video without unneeded drives mounted. Best autodesk inventor fusion 2013 r1 download 2016 torrent 2016. If the issue persists it may be a drive that is currently in use. To isolate the issue move the video media to the system drive and confirm that the video engine will launch. Add drives back to the system to see when the issue returns.