| PP CS6 hangs on open
• | | | |
 | PP CS6 hangs on open
by Kevin B on Jul 17, 2012 at 1:48:18 pm |
Hey folks,
I have PP CS6 on a Mac (10.6.8) and it suddenly refuses to open. The program hangs at "loading ExporterQuickTimeHost.bundle."
I have found several threads on the Adobe forums about this same issue, some dating back to the CS5 release. I've tried several of the suggestions to no avail. There seems to be real confusion over what is causing this and I've seen very little from Adobe about it.
Could someone please give me an idea about what is causing this and how to fix it? Also, it's not just PP that's having issues; AE will not open either.
Thanks in advance for any help.
Kevin
| | | | |
• | | | |  | Re: PP CS6 hangs on open
by Dan Turner on Jul 17, 2012 at 2:44:19 pm |
By any chance are you running Magic Bullet and a Blackmagic Card?
I had this issue recently with a project, had to open Looks separately, and change from CPU to GPU in preferences, which did the trick...
| | | | |
• | | | | | Re: PP CS6 hangs on open
by Kevin B on Jul 17, 2012 at 4:17:05 pm |
I am running Magic Bullet Looks, however, no Blackmagic card. I changed the prefs just in case, but still get the same hang.
Thanks for your suggestion.
| | | | |
• | | | | | Re: PP CS6 hangs on open
by Kevin B on Jul 17, 2012 at 7:30:44 pm |
After several responses over on the Adobe forum (http://forums.adobe.com/message/4562868#4562868) it looks like problems with third party codecs.
After removing codecs from my Mac/Library/QuickTime folder didn't work, I took a look in my username/Library/QuickTime folder and removed the two files I found there... Voila, after a restart, PP and AE will now both successfully launch!
Below are the names of the files I removed.
AC3MovieImport.component
Perian.component
This was such a seemingly random issue (working one day, then nothing) I'm not feeling too confident about this not happening again. If anyone else has any insights into the cause, please post.
Kevin
| | | | |
• | | | |  | Re: PP CS6 hangs on open
by Roel Bus on Jul 19, 2012 at 2:10:38 am |
Thanks for posting this, I had the same thing happen to me. My daughter is learning PPRO, and was working on it today, then closed it. When I came home from work, it would not load. I did exactly what you did, and it opened...... weird.
| | | | |
• | | | |  | Re: PP CS6 hangs on open
by Kian McKellar on Aug 13, 2012 at 5:41:28 pm |
This worked for me, thanks. I was removing the quicktime components from my main library instead of the library on my user account and was frustrated because it wasn't fixing the problem.
| | | | |
• | | | | | Re: PP CS6 hangs on open
by sean arnold on Aug 30, 2012 at 1:13:34 am |
SO after trying every bit of advice I could find on the web I still could not open CS6 Media Encoder or Premiere. So, I booted into the recovery partition of my iMac. I used disk utilities and ran "Repair Permissions" three times. Rebooted and both programs now load.
I tried:
Reinstall of CS6
Deleting Quicktime Plug-ins
New User Account (Programs did load with this, however, I didn't want to transfer all my media over to this account)
Reset Admin Password through Terminal in recovery mode.
| | | | |
• | | | | | Re: PP CS6 hangs on open FLIP4MAC V3 installation
by Brian Vawter on Feb 24, 2013 at 5:47:17 pm |
FLIP4MAC V3 installation caused this problem for me.
I too got the error "loading ExporterQuickTimeHost.bundle" when launching Premiere.
I encountered the problem after I had attempted to install Flip 4 Mac V3. This was the OS Lion version of F4M. The installer checked and notified me of this (my system is Snow Leopard)
I obviously didn't update F4M but after quitting the installation I got the "loading ExporterQuickTimeHost.bundle" error and could not launch Premiere.
But I was able to solve this by going to Hard Drive/Library/Quicktime and trashing the "Flip4Mac WMV Import.component" file. I then restarted and Premiere launches again.
| | | | |
• | | | | | Re: PP CS6 hangs on open FLIP4MAC V3 installation
by Clayton Moore on Feb 26, 2013 at 6:00:48 pm |
As someone who worked in the software support business for over decade Ill just say this.
This is an Adobe bug that had Adobe and Apple (Steve) not had a falling out sometime ago would have been fixed by now. Its time that both companies make nice and move on. But if you look at the history of this error and the fixes to it, its clear it "could" have been a non issue by now.
Ive seen more then one "technical issue" clear up once the "non-technical" issues were addressed.
| | | | |
| |
|
Reply
Like
