Premiere Pro won't Quit or Close a Project (Mac)

Hello,
This only affects a specific user account. Premiere Pro CS6 won't quit or close a project--nothing happens. Haven't been able to figure out what the cause is. I've tried blowing away the user's preferences.
What other local user files does Premiere screw with that could cause this behavior?
Cheers,
Casey

one more thing, this could be helpful if anyone else is running the same problem.
I found that if you save the encoder queue and close the encoder, then you can close the premiere project without crashing premiere.
but also found that AE does exactly the same, if you are editing a AE link comp you will need to close and quit after effects before changing premiere project

Similar Messages

Premiere pro won't display or play audio on Mac os 10.9

premiere pro won't display or play audio on Mac os 10.9; we are uploading AVCHD mts file format video clips from a Canon camcorder. we get message : "Dolby Audio licensing decode restriction."

next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.4 and OpenCL issue https://forums.adobe.com/thread/1514717
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-and https://forums.adobe.com/thread/1507936

Premiere Pro CS6 crash everytime I close a project

Hello,
I got 32 different projects with lots of AE links in the timeline (more than 80% is AE links). The problem occurs when I start the queue process for rendering in media enconder.
Everytime I send a project to enconder, when I want to close premiere pro to swtich to another project and do a big batch render list on encoder, premiere crash with a "sorry a serious error has occur" message.
Even if the queue encoder is empty but the app is open the premiere crash, whenever you quit, close project or open a new project.
It's taking a lot of time to reopen, wait for the media to come online and consolidate links, then send queue then wait for the crash the reopen etc... I making corrections on this 32 different projects and I need to batch enconde all of them everytime the clients ask me for a change.
I feel is payback time... I just switch from FCP to premiere and I was loving how fast I was doing this project working everythin in adobe over FCP+AE+Protools was so fast until now.
Any suggestion? thanks
Macpro 4,1 Quad core intel xeon 2.66Ghz
osx10.6.8
16G RAM
ATI radeon HD 5770
Blackmagic Studio HD

one more thing, this could be helpful if anyone else is running the same problem.
I found that if you save the encoder queue and close the encoder, then you can close the premiere project without crashing premiere.
but also found that AE does exactly the same, if you are editing a AE link comp you will need to close and quit after effects before changing premiere project

My Premiere Pro won't open and keeps coming up with a 0xc000007b error message!! I have uninstalled

My Premiere Pro won't open and keeps coming up with a 0xc000007b error message!! I have uninstalled and reinstalled it but it will still not open.

It worked for me, any way we have to do following things now, I have seen this happens becasue of the corrupt dll for Visual C++ packages. if the following thing will not work, I am affraid we have to reinstall the windows 7
Good Luck
Try to remove all the Visual C++ 2010 Redistributable and Visual C++ 2008 Redistributable Packages (both x86 and x64) from the Control Panel
Download and install following Visual C++ Redistributable Packages
Microsoft Visual C++ 2008 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2008 SP1 Redistributable Package (x64)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
Microsoft Visual C++ 2010 SP1 Redistributable Package (x64)

Premiere Pro CS5.5 Quit Unexpectedly. Mac 10.10.2.

Hey there,
My Mac just started popping up with the "Premiere Pro CS5.5 Quit Unexpectedly" box. Nothing has been done differently and the program has been working for years. Any help?
My Mac is a 2011 17" and currently has OSX Yosemite 10.10.2.

Hi Rotorbound,
Nothing has been done differently and the program has been working for years.
You updated OS X and that's a pretty significant change to your system. Have you tried common troubleshooting techniques?
Try the following:
Choose Help > Sign Out. Restart Premiere Pro. Choose Help > Sign In
Update any GPU drivers
Trash preferences
Ensure Adobe folder preferences are set to read/write in all 3 locations.
Delete media cache
Delete preview files
Remove plug-ins
If you have AMD GPUs, make sure CUDA is not installed
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Report back if anything here worked for you.
Thanks,
Kevin

Premiere PRO CS4 " unexpectedly quit error" since loaded Sorenson squeeze 8.5 is there a bug fix

Premiere PRO CS4 " unexpectedly quit error" since loaded Sorenson squeeze 8.5 is there a bug fix

CS4 is old, and there will be no more updates, past the ones on the update site
All Adobe updates start here and select product, read to see if you need to install updates in number order, or if the updates are cumulative for the individual product http://www.adobe.com/downloads/updates/
Ask Sorenson if 8.5 is even supposed to work with CS4

Premiere Pro CC crash on launch, crash opening project, update issues

Hi,
iMac 2011 quad i7 3.4 GHz, 20GB RAM, MacOS 10.9.2 and 10.7.5, Premiere CC 7.0.0 & 7.2.1
I've been having a crazy time with Premiere CC. I started an Africa documentary 2 weeks ago, which forced me to upgrade to CC (on MacOS 10.9.2). Other than some issues with the Creative Cloud installer app (which seems like a great idea but never seems to work as it should, especially with updates), I was happily working away for about 10 days.
During that time I had to install Premiere CS6 again to open another project -- and continued happily working.
Then I needed to export some markers... and discovered that the Creative Cloud app wasn't reporting any updates beyond 7.0.0, and I needed 7.2.1 to export markers. That's when my problems started.
I tried to update to 7.2.1 with the Creative Cloud app -- it wouldn't see the update.
I tried to download the 7.2 and 7.2.1 patches from Adobe's site directly -- neither of these would install, because they said I didn't have the right software (or something like that -- didn't write down the error).
Finally I used the Adobe Cleaner tool to uninstall and clean all Adobe apps off my system. Then I was able to use the CC app to download 7.0.0, and my patches to update to 7.2.1.
I tried to open my project... Premiere crashed as it opened the project (as it was loading the clips).
I uninstalled all 3rd party effects, checking to ensure nothing was in the MediaCore folder. I deleted all caches and previews. I checked the permissions of the Adobe preferences folder, and trashed the Premiere preferences. I rebuilt permissions.
Now, not only could I not open the project, but Premiere itself would not launch -- it would freeze to the point of forcing a reboot.
Cleaned Adobe apps again, went online with Adobe tech support for a full hour. The main thing they did was remove a CUDA extension, but after reinstalling, the problem persisted... at first it crashed while loading the project, and then crashed in the launch itself.
Luckily, I had a backup of MacOS 10.7.5, which I had been using before starting this documentary project. I went back to that backup, installed Premiere 7.2.1... and now Premiere launches properly but still crashes about halfway through loading my project.
I can load the project if the clips are offline (temporarily renaming the footage folder), so it seems that somewhere along this zany process, one or more clips got corrupted.
With 15,000 clips of different formats in this project, finding which clip(s) is corrupted is like finding a needle in a haystack. For now, I am importing my sequences into a new project, and just importing the clips I need to finish my edit at hand. Then I will likely have to build a new project from scratch -- a long process, since Premiere can't import nests of subfolders like After Effects and Final Cut Pro can, and that's how the footage from this project has been organized.
Arg! At this point I have a workaround (at least in MacOS 10.7.5), so I'm not really asking anything, but if anyone has light to shed I'm all ears.
P.S. I think when I installed CS6 after installing CC, it confused the CC app. I don't think that caused my Premiere issues, but I think it may have contributed to the issues installing updates, and the CC app getting confused.

Hello GrayJones,
This does seem like some pretty unusual behaviour! And I can only imagine the frustration it must be causing (believe me, I've been there!)
I've seen a lot of crash issues that are related to computer's graphic cards. You may want to try updating your graphics card's driver before proceeding forward. Also, there are a very small number of graphics cards that just don't work well with Premiere. You can also check the settings of your Mercury Playback Engine GPU. This can impact the performance of your software, especially depending on your graphics card. I may have missed it above, but didn't see anything related to Graphics cards in what you tried.
If you update your graphics card's drivers, and then update your version of Premiere Pro, it may solve the crashing on launch issue that you were having. Moving forward with fully updated PP software would be my first course of action, if it's possible.
Although I see that you have tried it alreay, you might want to reset your preferences (hold Cmd and Shift on the Mac while opening the program until you hit the splash screen) and resetting your PP cache (Premiere Pro - Preferences - Media - Click on "Clean Media Cache Database"
Without seeing the errors that caused your updates to not install originally I can't really offer suggestions regarding that. It could be a system conflict somewhere on your computer, but there are dozens of possibilities of what could be causing, especially if you have other plugins, older versions of Adobe or other video softwares, that kind of thing...
Moving forward from there:
How are you working? Are your images stored on an external hard drive or locally? How are you connecting the hard drive to your machine? Are you tossing all of the clips with different time code into one sequence and working from there, or editing on separate sequences?
As for your project: Do you have the ability to test it on a different machine? You can try doing a project manager (File-Project Manager) and putting your entire managed project onto a different machine to see the behaviour, that way you can figure out if the issues are related to the project itself, or to your install of Premiere Pro on your machine. IF the project works fine on another system, then clearly the issue is related to your software/hardware configuration, if you have the same issues with the project on every machine, then it might be something different. Can you test other projects on your current set-up? Is this the only project that is affected?
If you have one or several corrupted files I know it can be painstaking to try to locate where the damage is at, generally it's a process of elimination, make a sequence with files from one camera and see what happens, if it glitches, try another camera until you can see if it's a general issue to all of your cameras or specific to some. Narrow it down from there, if it's multiple cameras, then the error (again) is software/hardware or transfer related or occurs in your transfer/storage process, or may be related to your uninstalls/re-installs with CC and CS6 (although I don't think I've ever seen that!)
If it's only clips from one camera (you mention the Canon XF100 has problems) maybe something affected your camera. I once saw standing too close to a radar-dish corrupt 1/4 of the clips from a BBC videographer's camera. I have no explanation why... but it can happen, so if only one camera is affected you should consider the possibility.
I'll try to assist with this as much as I can! But remember that the forums are not here for Adobe personnel to provide support to clients, but as a community for Adobe-philes to share and help. A lot of Adobe staff who are posting on here are generally doing it because they've got a bit of free time and want to help out. You should consider contacting support again if you can't resolve the problem and getting them to connect you to a video specific team.
Cheers!
J

In Premiere Pro, is it possible to change the project aspect ratio once started?

In Premiere Pro, is it possible to change the project aspect ratio once started?

On a side note, 'projects' do not have as aspect ratio, sequences and footage do. And a project can contain any number of sequences or footage.

PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B

Dear Sir,
I'm in a big ****. I've directed and edited 1h documentary for Finnish television, also, the technical specs requested by the TV Channel is all production Broadcast masters must be encoded with Apple ProRES codec or MJPEG A or B.
As i'm working on PC (win7), the ProRES codec doesn't exist on PC system, so i've done the export to MJPEG. The problem is i have a different gamma level when i watch the final export with Quicktime or VLC. Of course i can adjust the level in those players, but it doesnt effect the file. When i import the Qt file into a Premiere sequence, the gamma level is still **** and different from my original level i have from my timeline and preview window. If i export the project to H264 1920x1080p25, then the gamma is perfect with Qt, VLC and WinMedia player. But the TV station don't wanna work with H264. Deadline is on next monday, and i can't send a Qt MJPEG file with wrong gamma !!!Any chance to find a solution to fix it ??? After reading different forum, i can see this problem exist since many years and never been solved.
What can i do ??
Denis.

Things is my prpject includ few effect plugins i bought, so what ever i could find a mac, not your i could export xml project to finalcut with plugins it dont have
Denis
Sent from my iPad.
Le 31 mai 2013 à 15:20, Fuzzy Barsik <[email protected]> a écrit :
Re: PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B
created by Fuzzy Barsik in Premiere Pro - View the full discussion
If it were me, I wouldn't encode to MJPEG.
So as to encode to ProRes on Windows you can utilise any solution based on ffmpeg/ffmbc or better yet find a Mac with Final Cut or Compressor installed for delivering critical work.
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5368019#5368019
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5368019#5368019
To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5368019#5368019. In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Premiere Pro by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

Premiere Pro CC updated - crashes almost immediately on my mac OS X Yosemite 10.10.3. Crashes at startup, crashes with media import, crashes when creating a sequence. NEED HELP FAST I have tried many troubleshooting solutions I found online nothing has

Premiere Pro CC updated - crashes almost immediately on my mac OS X Yosemite 10.10.3. Crashes at startup, crashes with media import, crashes when creating a sequence. NEED HELP FAST> I have tried many troubleshooting solutions I found online nothing has worked.

Hi,
Sorry to hear about the experience. Please provide your computer configuration details.
Memory, Processor, Graphics card, Exact version of Premiere Pro, Error message that you are get. If you can post screenshots of the error report that would be helpful.
Thanks,
Rameez

CC Won´t Work, When i open Premiere PRO It Works until i open a project and it closes with no advice

Well i am REALLY dissapointed so far, i just purchased the CC full for one year and i have not been able to use it. First it asks for ******* serials, already did all the steps in the guides you provide.
Now i try to open Premiere Pro CC and it closes unexpectedly when i try to start a project

I do not find any other messages from you, so I do not know what you mean by provided guides... so I will post the links I have and hope one will help
You download & install & activate Cloud programs by logging in to your Cloud account
http://www.adobe.com/products/creativecloud/faq.html
http://helpx.adobe.com/creative-cloud/help/install-apps.html to install or uninstall
http://forums.adobe.com/community/download_install_setup/creative_cloud_faq
what is http://helpx.adobe.com/creative-cloud/help/creative-cloud-desktop.html
Cloud Getting Started https://helpx.adobe.com/creative-cloud/topics/getting-started.html
For Premiere Pro, More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840

Premiere Pro CC wont quit

Running a brand new Creative Cloud install on a Windows 7 machine...
Every time I run Premiere Pro CC and then close the program, it "appears" to have closed. However when I try to run it again it won't launch a second time. When I bring up the Task Manager, Premiere doesn't show as running in the "Applications" tab, but it does show up in the "Processes" tab... and it's hogging down a ton of memory.
So, I have to force the process to terminate, then I can launch Premiere again. But, as soon as I exit Premiere, the problem is right back again. Pretty frustrating to have to bring up the task manager and kill a process every time you want to exit a program.

Add another to this list.
Projects in Premiere spontaneous freezes. Sometimes audio works but video won't play.
Only force Quit will help.
Working with a iMac (27-inch, medio 2011) AMD Radeon HD 6970M 2048 MB, 16 GB 1333 MHz DDR3
Cleaning up cache database did'nt help!
What is best to do? reïnstall?

Premiere Pro won't save my project

My project has been working fine up until a while ago when I tried to save it and the loading bar came up but the yellow loader wouldn't move. It won't save my project and when I click cancel the Premiere Pro simply freezes and then I have to force quit. How do I save my project??

It sounds like you're not doing this correctly.
1. CLOSE Premiere Pro entirely. All projects. The entire Premiere Pro program. Close it down. Completely. Maybe even restart the computer to make sure that Premiere is NOT running.
2. Now, Hold down the Shift+Option keys. Make sure you hold them both down at the same time. You can hold down Shift, first, or you can hold down Option, first, but whatever you do keep holding them down. Together. Keep holding them down.
3. WHILE you're STILL holding down the Shift+Option keys, open Premiere Pro. You can open Premiere Pro any way you wish, just make sure that when you do, you're STILL HOLDING down the Shift AND Option keys. Keep them held down while Premiere opens.
When Premiere opens do you see any of your recent projects in the recent projects list? If you don't, then you've successfully trashed your preferences.

Premiere Pro won't shut down

Hi,
The problem is that Premiere Pro Cs6 won't shut down or close a project and must be force quit. It will also now allow me to open two projects at once (which can happen when one project fails to close.) However, this quickly leads to a crash.
Does anyone know how to solve this?
It emerged suddenly, right after fixing a problem with a serial number conlfict for Red Giant Color Suite. We repaired the preferences and reinstalled the Red Giant plug, but then the problem emerged. My feeling is it's related. Some kind of goofed up preferences, but how to fix?
Thanks for any help.
Carolyn

Now I find that out. I upgraded to Maverick after we
uninstalled/reinstalled. What fresh hell can I look forward to? I'm getting
to the point where I would rather amputate a body part than update my
software.
All joking aside, should I uninstall/reinstall again?
Right now, my workflow is to save a dated version (save as: name-date)
before I close the project, which i then do by force quitting. It crashes
and my file is saved as a recovery. My theory is that if my recovery file
gets corrupted, I have the most recent save-as version to go back to. God
willing and the creek don't rise, I can go on indefinitely this way, no?

Premiere Pro crashes after quit - Mac OSX Lion

Greetings,
Symptoms:
I'm experiencing a consistent crash behavior after quiting Premiere Pro (ver 5.5.1 and 5.5.2). The complexity of the project doesn't seem to matter and once it crashes, i get the prompt indicating the app encountered a serious error and will try to save the project. I then get the usual crash report prompt to send to apple followed by the adobe crash report a few minutes later (must be why i see "dynamiclinkmanager" in top for a bit after PP crashes).
If I reopen PP, I'm prompted with a dialog box asking if I want the last project opened. If I say yes, I'm back to a crash before any assets load (unexpected serious error and the app will need to close) followed by the crash reports again for apple and adobe. Basically, i get one chance to make a project and it goes bad when closing the application.
I'm using an install from a DVD, but had also tried the web version. I was able to create a couple projects with the web version (trial) and then when I got the DVD, i believe i used that for updating/authenticating, etc - maybe that's where things went south (anyone else observe a similar pattern?). I didn't think too much of mixing the DVD content with the web install, so the steps around how i mixed those two sources is somewhat fuzzy.
For reference, i'm pasting the crash report inline. To reproduce, I just had to open PP, click no when asked to open the last project that unexpectedly quit, and then just hit quit and got the crash. I didn't do anything other than accept the project defaults in order to test out hitting command-Q.
If I can provide futher info to help with a repro, please let me know.
Any help is appreciated and thanks in advance,
Todd
<<begin crash report>>
Process:         Adobe Premiere Pro CS5.5 [280]
Path:            /Volumes/VOLUME/*/Adobe Premiere Pro CS5.5.app/Contents/MacOS/Adobe Premiere Pro CS5.5
Identifier:      com.adobe.AdobePremierePro
Version:         5.5.2 (5.5.2)
Code Type:       X86-64 (Native)
Parent Process: launchd [126]
Date/Time:       2011-12-08 21:42:17.998 -0800
OS Version:      Mac OS X 10.7.2 (11C74)
Report Version: 9
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
objc[280]: garbage collection is OFF
terminate called without an active exception
abort() called
Message was edited by: Jeff Bellune. Edited for brevity.

Thanks for reply zikade, here's my rig:
Model Name:          Mac Pro
Model Identifier:          MacPro5,1
Processor Name:          6-Core Intel Xeon
Processor Speed:          2.66 GHz
Number of Processors:          2
Total Number of Cores:          12
L2 Cache (per Core):          256 KB
L3 Cache (per Processor):          12 MB
Memory:          64 GB
ATI Radeon HD 5770:
Chipset Model:          ATI Radeon HD 5770
Type:          GPU
VRAM (Total):          1024 MB
Regarding en/disabling the mercury engine, is there another place to toggle that? I didn't think i had any other choice at this time with my card option (until i get a nvidia cuda card). FWIW, When creating a new project, the options in the drop down menu for "Video Rendering and Playback" is greyed out with "Mercury Playback Engine Software Only" as the selected option.
I was also thinking of putting a fresh Lion install on another disk (bah, would prefer to not have to do this since I have other stuff all nice and set up on current OS install), but at this point I'm fine to take the hit and level the playing field w/ a fresh OS, image that for downstream testing if a fresh install is needed again, and then start installing things one at a time until something goes wrong.
It seems (i hope) this error could be caused by something pretty basic as it is a complete showstopper. Unless somehow what I'm doing is super unique, there would be other folks out there dead in the water, to, but making waves.

Premiere Pro won't Quit or Close a Project (Mac)

Similar Messages

Maybe you are looking for