Hi Bob,

Went down this rat hole a few weeks back and came across some solutions regarding the removal of the DVCPROHDoutput codec in the Quicktime Library. I removed it on some of our bays, but still see this issue popping back up in the activity monitor from day to day.

Here are some pages to read I found when dealing with the issue:

https://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in-after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html

https://blogs.adobe.com/aftereffects/2011/02/troubleshooting-quicktime-errors-with-after-effects.html

https://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in-after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html

Also terminal fix for Ap Nap issues if you are running Mavericks or Yosemite.
https://forums.adobe.com/message/6561278#6561278

You can also apply the new ProApps Codec pack from Apple (https://support.apple.com/kb/dl1396 ) if the machine has any of the Apple aps on it (FCPX or Compressor).

Adobe is aware of the issue, thus the blog posts above.

We had some playback issues with our older AJA Kona cards and upgraded to the latest drivers. It has helped, but still needed extra fine tuning with the help of AJA support call.

If you come across any more info, please post back.

Andy Edwards
Denver

Hi Bob,
This is from Premiere Pro QE:

“The QT32Server process always shows as “Not Responding” in the activity monitor, this is normal (in OS X 10.9.x, and later – KM). The way to tell if QT32Server is hung (which happens if  QuickTime crashes or get stuck and never returns control to us) is to look at the CPU load for that process when doing some QuickTime intensive thing (non-native import and export).”

[Bob Zelin] “getting terrible performance in playback of Premiere CC2014 on Mac Pro with 12gig RAM. Drives are fast enough.”

Primarily, we’ve seen issues from those updating complex project files from Premiere Pro CC 2014 (8.0) to Premiere Pro CC 2014.1 (8.1). Many of those reporting issues are Mac users on OS X 10.9.x, or later and on the 2013 Mac Pro with dual AMD GPUs. Currently, I am recommending against updating project files and only do so for new projects only.

Brand new projects typically don’t exhibit these performance issues. You may want to perform a test with a new project. Personally, I am on OS X 10.8.5, and experience no trouble, even with updating legacy projects (however, my projects are rather simple).

[Bob Zelin] “I did a google search on this, and lots of people complain about it on the Adobe forums, with no apparent solution.”

We have a bug filed and are actively looking for a solution as we are having a difficult time reproducing the issue. If you can file a bug report here, it would be most appreciated: https://adobe.ly/ReportBug

One common problem that may be related to your performance issues is that updating OS X can sometimes reset the permissions of crucial Adobe folders. See my blog here: https://blogs.adobe.com/kevinmonahan/2014/09/10/premiere-pro-cc-freezing-on-startup-or-crashing-while-working-mac-os-x-10-9-and-later/

Other things that may help: