I am having problems with Premiere Pro CC 2014.2 that make it almost unusable on my system. All other software, including AE, Audition, Prelude, Photoshop etc. working well.

The symptoms, which are not specific to any one project - but seem to effect all equally - are:

1) Intermittently, I loose the ability to play clips or the timeline. I can drag the playhead around, but nothing plays, nor does the viewer or program monitor change or update. I can't use the space bar for play, nor can I click the play button with the mouse. Either action requires a re-start.

2) Exiting the application, Premiere Pro will not completely shut down. It goes into some kind of limbo state. The only way to shut the application down is to use the Force Quit command from the Apple Menu. Once the application has been Forced to Quit, it will not restart until the computer has been restarted. It will just bounce up and down in the dock and never launch completely. The only way to launch it again is to completely restart the computer. If the application has been force quit, when I shut the computer down, I get the spinning wheel for a very long time during the shut down process, but the computer does completely shut down on its own. After I restart, Premiere Pro starts up promptly.

What I have done so far:

Verified Disk Permissions

Run Disk Warrior on all disks.

Trashed Premiere Pro preferences

Uninstalled the Premiere Pro app, and then re-installed a fresh download.

I don't have an answer. I have the same problem I am using a mac with Yosemite OS and a AJA kona LHi card.I will be going along just fine and then I get the spinning beach ball of eternal damnation. I am forced to quit but premiere won't quit. The external firewire drive my media is on will be unresponsive. I need to shut down and power cycle to get things back to normal. Twice out of the dozens of times this has happened I have corrupted the media drive directory. All in all a terrible experience and like Meg all other programs are fine. I use Avid Media composer and Final cut 7 on the same machine as well as photoshop boris fx motion etc.

That's normal. With OS X 10.9 and later, there is no QuickTime 32 Server any more so you get this warning. Your issue is related to something else. I've seen other users have similar issues. I am investigating this now.

If the QT32Server process always shows as “Not Responding” in the activity monitor, this is normal.

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).

That was my original setting, (which worked well over a fairly long period of time) as I was unsure of the suitability of the graphic card I'm using and the Cuda support. I switched to CUDA on your advice, the problem remains. My CUDA driver is 6.5.36.

Are you using any effects on the footage?

Mostly color correction (Fast Color Corrector, RGB Curves) filters, I do some compositing with .png graphics with transparency, and generate some titles. Anything more complicated I do in AE and export a ProRes file from AE which I bring into PPro (old habits die hard). The problems don't seem to me to related to the effects content of the sequence. I normally try to work in ProRes, I use Prelude to transcode on ingest if not ProRes source material.

How much space is left on your OS X boot disk? Your media drives?

The boot disk is a 480gig SSD with 156 Gigs available, the cache files are on thunderbolt 4 drive raid with 1.5TB available, The current media I am working on now is on another thunderbolt 4 drive raid with 1.23 Tb available. I also have single rotational disks that I use for client library footage that is connected via a USB3 line to a Burly 5 bay swappable drive enclosure.

I'll test, but not sure how much the effects have to do with the problem. This morning I had just placed three clips on an empty timeline, and then I lost playback function as described above, and then started having the crash on close problems.

Created the new user account, opened the project and got back to work - just editing, no effects and had no problems for an hour or so, then went to close Premiere and had the crash on close problem again - forcing a restart to be able to use Premiere again.

OK my problems disappeared when I un-enabled Mercury Transmit. I use either an AJA IO Express (in office) or an AJA T-Tap (out of office) to connect to a broadcast monitor.

Once I had un-enabled Mercury Transmit, Premiere runs snappy and smooth, no crashes or restart problems.

I see that today 1/22/15 AJA has released a new driver package for the IO/KONA/TTap devices with some Adobe CC fixes. I have downloaded and installed and so far (although it has only been a couple of hours) everything seems very stable.

I did a fresh install for unrelated system issues, and now premiere with this new update has this and other problems for me.

This seems to be a bug. I have this same issue. I'm on a window 7, but its the same exact thing, so it isn't system specific. Playback will freeze, saving still works, but on closing the application it hangs. Can't restart premiere until I end the quicktime server process. It has nothing to do with effects, i don't have any on any of my clips.

Issue is "solved" if I turn off mercury playback and leave it on software mode. That would be fine, but I have a separate(?) issue where i can't render the time line with out getting an error... and its impossible to edit in software mode when you can't render. This is turning into quite a real problem its so annoying.

OK my problems disappeared when I un-enabled Mercury Transmit. I use either an AJA IO Express (in office) or an AJA T-Tap (out of office) to connect to a broadcast monitor.

Once I had un-enabled Mercury Transmit, Premiere runs snappy and smooth, no crashes or restart problems.

I see that today 1/22/15 AJA has released a new driver package for the IO/KONA/TTap devices with some Adobe CC fixes. I have downloaded and installed and so far (although it has only been a couple of hours) everything seems very stable.

I'll post back if trouble resumes.

Thanks for the help!

MtD

Thanks very much for reporting back. I am so glad that the new drivers seem to be working for you.

Issue is "solved" if I turn off mercury playback and leave it on software mode. That would be fine, but I have a separate(?) issue where i can't render the time line with out getting an error... and its impossible to edit in software mode when you can't render. This is turning into quite a real problem its so annoying.

Please create your own post. Your issue is probably not the same one as Meg's.