Premiere Pro Quitting Repeatedly
I have a MacBook Pro, 16GB Ram, 2.7 GHZ, running OS 10.9.5 with the most recent update to Premiere Pro CC 2014. I'm working with FS700 AVCHD .mts files off of my Lacie 6TB Thunderbolt external hard drive along with an Apple Thunderbolt display. I literally edit and move a couple clips onto the timeline and the program will quit. No window popping up saying "sorry premiere must shutdown etc" nothing. Program just quits. This is happening on not just one premiere project but all of them. I open a brand new one and it quits, then go back to work on a previous project and the same thing happens. I've tried clearing the cache and the problem still remains. Anybody have any fix for this? Thanks.
VST = Virtual Studio Technology and are usually .dll's that are "plugged into" applications that are VST-aware, like Audition, PrPro, ProTools and many others. Here is a LINK with much more detail.
What can happen is that programs, like Audition (PC only), and PrPro can use many. However, they survey the system and will try to load all that they find. If the program cannot use some, what usually happens is the first loading will yield an error message, stating "Premiere cannot use the SampleTank2.dll" (for instance), and you'll never see that message again. In that case, PrPro still loads it, and no harm is done. With some, the program crashes as soon as it attemps to load them. Why some are benign and others deadly is a mystery to me. Probably how they are coded.
If you have any other audio processing programs (most likely to have VST's there), you like have some that PrPro is loading, or trying to load. Like I said, some work, some do not and some kill the program.
Just found a little trick with bad VST's: on a PC, you can take the bad VST's and drag them to the Desktop. Apparently, PrPro will not find them there. When one uses the audio program, they just point it to the Desktop, or drag the folder back to the proper program. For pre-Vista OS's, there is a script to "blacklist" VST's from PrPro, but do not think that it would apply to Mac's.
I also do not know exactly how Mac's "register" VST's, so they may not be an issue. That is what happens when a PC-guy trys to help troubleshoot Mac issues - he can get it all wrong for that platform.
Because of the nature of your crash, on a PC this would throw up the immediate red flag - VST incompatibility. Do not know if it applies to Mac. The VST issues are not the only cause for crashes upon loading, but are probably the major one. Again, this is on the PC, and all could be different on a Mac.
Good luck, and I'll post any other things to think about, should I come up with them.
Hunt
Similar Messages
-
Premiere Pro Quit Unexpectedly and got rid of All of My Edits
I just purchased a membership for the Creative Cloud a few days ago and have been editing my short film on Premiere Pro. I had gotten through all of my sequencing, most of my sound editing, and most of my color grading. Everything was going well. Suddenly, earlier this evening (I had only been editing for a few minutes and had most of my work saved from the previous day), I received an alert that told me an error occurred that would force Premiere Pro to quit, though it would try to restore my work. I figured this wouldn't be an issue since I had only just started editing and most of my work was already saved. However, when I reopened Premiere Pro, another alert popped up telling me that it was trying to restore my work and would therefore have to create a copy of my project, so I agreed to it. When I opened the copy, all my sequencing edits were still there, but all of my color grades and sound edits were no more, as though they had never existed in the first place, and my clips were not sequenced the way they were. Trying to remain calm, I told myself that this was probably just because it was a copy and if I reopened the original file, all would be as it was. However, when I did reopen the original file (the file that had been saved the night before), the same thing happened. My color was not graded, my audio was not edited, and my clips were not sequenced, even though they were when I had saved my project the previous night. I tried opening the autosaved files, but they were all the same. Is there any way to salvage my edits or will I have to accept the loss of days of editing and start anew, other than the sequencing?
Start again and start a manual save backup regime. Sorry to bring you the bad news.
Edit
Start thisr egime from here on. -
I am a Mac user!!!!!!!!!!!
I have to use a PC at work(the XP thing)
when I boot up Premiere Pro 1.5, it quits.
Quicktime also quits when I open it up.
if we uninstall Quicktime 7.0.3, Premiere works.
I need Quicktime in Premiere to export .movs
this incompatibilty just popped up out of nowhere Monday.
any ideas wha is going on????
ThanksCan you please include a little more info. See this thread for guidance.
http://forums.adobe.com/thread/961741?tstart=0
Peter Garaway
Adobe
Premiere Pro -
Problems with Premiere Pro- Quits unexpectedly
Hello,
I have several key problems on Adobe Premiere CS6"
The following problem happens when I not only edit, but save, and export my project into a video file.
"Adobe Premiere Elements Has Encountered A Problem and Needs To Close - We Are Sorry For The Inconvenience"
I dunno how to solve or prevent this issue. Is it that my Mac lacks to power to edit, or are any of my settings off?
I don't think its Premiere that's the problem...
I'm guessing that either my preferences are wrong, or I'm just using too much or too large of footage to use on my sequences.
The camera I use is a "Sony HandyCam HDR- PJ650V", and the average video file runs around 1GB.
The media format is ".mts" and the only software that can understand it is Adobe After Effects or Premiere.
I've already lost so much time trying to figure out this problem, also hoping that same generic error message doesn't appear and crash Premiere again.
It always pops up!
Please help!!
This error message appears randomly through the following tasks:
1. Saving the project- It crashes w/ the same message after I click the save button.
2. Scrolling/previewing my project on the timeline- It might be processing or a GPU disfunction, but After Effects CS6 seens to be running smoothly enough, along with other somewhat hefty programs, like Photoshop. given the graphical prowess it requires.
3. Rendering the sequence, or composition (AE CS6)- I export my projects with the following settings:
Format: H.264
Preset: Youtube HD 1080p, 25
Audio format: AAC, 48000 Hz, Stereo
Also one thing to note, is the GPU is Mercury Accelerater engine, and I cannot change that to running off the CPU, not that GPU
The following specs are what I have to work with:
Mac:
I am using an IMac with software version 10.7.5.
-Processor: 2.8 GHz Intel Core i7
-Graphics: ATI Radeon HD 4850 512MB
-Kind: ATI Radeon HD 4850 OpenGL Engine
-Version String: 2.1 ATI-7.32.12
-Open GL Version: 2.1
-Texture Memory: 512
-Serial Number: W89526355RU
-Software: Mac OS X Lion 10.7.5 (11G63)
Adobe Premiere Pro CS6:
Version: 6.0.0
Last Modified: 4/29/13 10:31 PM
Kind: Intel
64-Bit (Intel): Yes
Any input/advice is greatly appreciated!!!Two problems:
Wrong forum, go to the Elements forum
Mac -
Premiere Pro Crashes repeatedly (EXC_CRASH (SIGABRT))
Hello,
Recently purchased the Adobe Suite and installed on my iMac.
(27" 2.8 Ghz Intel Core i7, 16Gb RAM 1067Mhz DDR3, OSX 19.9.4)
I'm in the middle of an Edit in Premiere Pro.
It was crashing one in a while, however now it is crashing more and more often.
- I'm in the stage of color grading - I'm using Adjustment layers with Magic Bullet Looks, and it seems to be crashing more during grading.
- I have a feeling that the origin of the problem could be with Magic Bullet.
I am attaching the crash report. Oh actually I can attach only Images ?
Ok, I'll paste below one of the crash reports...
Can someone please advise? Should I open also a ticket with Red Giant ? This crash is really annoying.
Thanks,
Tal
Process: Adobe Premiere Pro CC 2014 [699]
Path: /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier: com.adobe.AdobePremierePro
Version: 8.0.1 (8.0.1)
Code Type: X86-64 (Native)
Parent Process: launchd [171]
Responsible: Adobe Premiere Pro CC 2014 [699]
User ID: 501
Date/Time: 2014-08-24 01:29:26.615 +0300
OS Version: Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: D5A9A50F-FB2D-1422-FE58-07324419C367
Sleep/Wake UUID: F3B0D24A-DDDA-4439-A97D-16E867FB3FFC
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
Pure virtual function called!
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff8e8b3866 __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff94e5435c pthread_kill + 92
2 libsystem_c.dylib 0x00007fff8f064bba __abort + 145
3 libsystem_c.dylib 0x00007fff8f064b29 abort + 140
4 libc++abi.dylib 0x00007fff8b316f31 abort_message + 257
5 libc++abi.dylib 0x00007fff8b33b447 __cxa_pure_virtual + 18
6 com.adobe.VideoRenderer.framework 0x0000000104ff0100 ML::RenderableNodeClipSubTreeImpl::GetProducerForFrame(MF::FrameTime const&, ML::CutlistRenderParams const&) const + 368
7 com.adobe.VideoRenderer.framework 0x000000010501f009 ML::RenderableNodeSubtreeImpl::RenderSubTree(dvamediatypes::TickTime const&, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>&, bool) + 569
8 com.adobe.VideoFilterHost.framework 0x00000001059e62d5 ML::AEParameter::RenderLayerParam(ASL::InterfaceRef<BE::ISequence, BE::ISequence>, unsigned int, ASL::InterfaceRef<ML::SubTreeRender, ML::SubTreeRender>, ASL::InterfaceRef<BE::IVideoSegments, BE::IVideoSegments>, dvamediatypes::FrameRate, dvamediatypes::TickTime const&, dvamediatypes::TickTime const&, ML::AERenderState const&, bool, bool, PF_ParamDef*) const + 549
9 com.adobe.VideoFilterHost.framework 0x00000001059e567e ML::AEParameter::FillParamDef(dvamediatypes::TickTime const&, dvamediatypes::TickTime const&, ASL::InterfaceRef<BE::IComponentParam, BE::IComponentParam>, ASL::InterfaceRef<MF::IVideoFrame, MF::IVideoFrame>, ML::AERenderState const&, ASL::ParamRect<int> const&, ASL::InterfaceRef<BE::ISequence, BE::ISequence>, unsigned int, ASL::InterfaceRef<ML::SubTreeRender, ML::SubTreeRender>, ASL::InterfaceRef<BE::IVideoSegments, BE::IVideoSegments>, dvamediatypes::FrameRate, dvamediatypes::TickTime, bool, PF_ParamDef*) const + 3326
10 com.adobe.VideoFilterHost.framework 0x00000001059dd992 ML::AEInData::CBCheckoutParam(PF_ProgressInfo*, int, int, int, unsigned int, PF_ParamDef*) + 1298
11 com.redgiantsoftware.Looks3_AE 0x0000000125f7c59d AELookSuitePlugin::DoModalUI() + 477
12 com.redgiantsoftware.Looks3_AE 0x0000000125f7d79d AELookSuitePlugin::handleDrag(PF_EventExtra*) + 205
13 com.redgiantsoftware.Looks3_AE 0x0000000125f803e6 AEPluginBase::doCmd(int) + 646
14 com.redgiantsoftware.Looks3_AE 0x0000000125f77f74 EntryPointFunc + 52
15 com.adobe.VideoFilterHost.framework 0x00000001059883a8 ML::AEVideoFilterModule::CallModule(int, PF_InData*, PF_OutData*, PF_ParamDef**, PF_LayerDef*, void*, bool) + 392
16 com.adobe.VideoFilterHost.framework 0x00000001059700f7 ML::AEVideoFilter::CallAEFilter(int, PF_InData*, PF_OutData*, PF_ParamDef**, PF_LayerDef*, void*, bool) + 1063
17 com.adobe.VideoFilterHost.framework 0x000000010597f7f8 ML::AEVideoFilter::DoEvent(PF_EventExtra*, dvamediatypes::TickTime const&, ML::MultiCompoundAction&, bool) + 1976
18 com.adobe.VideoFilterHost.framework 0x0000000105981945 ML::AEVideoFilter::DoClickOrDragEvent(int, PF_Context**, ASL::ParamRect<int>&, ML::EffectArea, ML::ClickEventInfo&, dvamediatypes::TickTime const&, unsigned long, ML::MultiCompoundAction&, bool) + 853
19 com.adobe.VideoFilterHost.framework 0x0000000105981e13 ML::AEVideoFilter::EventDrag(unsigned int, ASL::ParamRect<int>&, ML::EffectArea, ML::ClickEventInfo&, dvamediatypes::TickTime const&, unsigned long, ML::MultiCompoundAction&, bool) + 419
20 com.adobe.VideoFilterHost.framework 0x00000001059821fa non-virtual thunk to ML::AEVideoFilter::EventDrag(unsigned int, ASL::ParamRect<int>&, ML::EffectArea, ML::ClickEventInfo&, dvamediatypes::TickTime const&, unsigned long, ML::MultiCompoundAction&, bool) + 42
21 com.adobe.Mezzanine.framework 0x00000001062a8ffe MZ::ParameterDirectManipulator::LeftButtonUp(ASL::ParamPoint<int> const&, MZ::KeyModifierInfo const&) + 270
22 com.adobe.HandlerEffectControls.framework 0x000000010a9af03b non-virtual thunk to HandlerEffectControls::CustomParameter::DoLeftButtonUp(ASL::ParamPoint<int> const&, UIF::KeyModifiers const&) + 43
23 com.adobe.dvaui.framework 0x0000000104130cc6 dvaui::ui::PointerCapture::InvokeEnd(bool) + 134
24 com.adobe.dvaui.framework 0x000000010413a495 dvaui::ui::UI_NodeManager::EndInputCapture(bool) + 117
25 com.adobe.UIFramework.framework 0x0000000104a61d21 UIF::PlatformViewMouseCaptureImpl::DoMouseEvent(dvaui::ui::MouseEvent const&) + 353
26 com.adobe.dvaui.framework 0x0000000104144f6d dvaui::ui::UI_Node::UI_DispatchCapturedMouseEvent(dvaui::ui::MouseEvent const&) + 429
27 com.adobe.dvaui.framework 0x0000000104144836 dvaui::ui::UI_Node::UI_DispatchPointerEventToTarget(dvaui::ui::UI_Node*, dvaui::ui::PointerEvent const&, bool) + 166
28 com.adobe.dvaui.framework 0x00000001041446e2 dvaui::ui::UI_Node::UI_DispatchPointerEvent(dvaui::ui::PointerEvent const&, bool) + 66
29 com.adobe.dvaui.framework 0x00000001041c0ed0 dvaui::ui::OS_View::UI_DispatchPlatformMouseEvent(dvaui::ui::MouseEvent const&, bool) + 608
30 com.adobe.dvaui.framework 0x00000001041c0a48 dvaui::ui::OS_View::UI_DispatchPlatformMouseClickEvent(dvaui::ui::OS_Event const&) + 600
31 com.adobe.dvaui.framework 0x00000001041bedf9 dvaui::ui::OS_View::UI_DispatchEvent(dvaui::ui::OS_Event*) + 121
32 com.adobe.dvaui.framework 0x00000001041bed56 dvaui::ui::OS_View::UI_HandleOSEvent(dvaui::ui::OS_Event*) + 22
33 com.adobe.dvaui.framework 0x00000001041c04d9 dvaui::ui::OS_View::UI_HandlePlatformEvent(NSEvent*) + 57
34 com.adobe.dvacore.framework 0x00000001002ea38c int dvacore::config::ErrorManager::ExecuteFunction<void>(boost::function0<void>*, void*) + 28
35 com.adobe.Frontend.framework 0x000000010006bc29 FE::ApplicationErrorManager::ExecuteFunctionWithTopLevelExceptionHandler(boost::function0 <int>) + 41
36 com.adobe.dvacore.framework 0x00000001002ea4d8 void dvacore::config::ErrorManager::ExecuteFunctionWithTopLevelExceptionHandler<void>(boost::f unction0<void>, bool*) + 136
37 com.adobe.dvacore.framework 0x00000001002eb875 void dvacore::config::ExecuteTopLevelFunction<void>(boost::function0<void>, bool*) + 165
38 com.adobe.dvaui.framework 0x00000001041cb7aa -[DVAMacContainerView mouseUp:] + 122
39 com.apple.AppKit 0x00007fff91489aea forwardMethod + 122
40 com.apple.AppKit 0x00007fff9148b145 -[NSWindow sendEvent:] + 781
41 com.apple.AppKit 0x00007fff9142c5d4 -[NSApplication sendEvent:] + 2021
42 com.adobe.dvaui.framework 0x00000001041c4cfb -[DVAMacApplication sendEvent:] + 603
43 com.adobe.Frontend.framework 0x00000001000c889d -[PremiereCocoaMacApplication sendEvent:] + 317
44 com.apple.AppKit 0x00007fff9127c9f9 -[NSApplication run] + 646
45 com.adobe.Frontend.framework 0x00000001000ca38d FE::MacApplication::RunSelf() + 45
46 com.adobe.Frontend.framework 0x000000010004898a FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
47 com.adobe.Frontend.framework 0x00000001000cbc44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
48 com.adobe.Frontend.framework 0x00000001000d2e25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
49 com.adobe.AdobePremierePro 0x00000001000018ac main + 508
50 com.adobe.AdobePremierePro 0x00000001000016a4 start + 52
Model: iMac11,1, BootROM IM111.0034.B02, 4 processors, Intel Core i7, 2.8 GHz, 16 GB, SMC 1.54f36
Graphics: ATI Radeon HD 4850, ATI Radeon HD 4850, PCIe, 512 MB
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E433136464B00
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E433136464B00
Memory Module: BANK 0/DIMM1, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E433136464B00
Memory Module: BANK 1/DIMM1, 4 GB, DDR3, 1067 MHz, 0x859B, 0x435434473353313036374D2E433136464B00
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x8F), Atheros 9280: 4.0.74.0-P2P
Bluetooth: Version 4.2.6f1 14216, 3 services, 15 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Hitachi HDS722020ALA330, 2 TB
Serial ATA Device: OPTIARC DVD RW AD-5680H
USB Device: Hub
USB Device: Portable HDD NH92
USB Device: PTK-440
USB Device: IR Receiver
USB Device: Built-in iSight
USB Device: Hub
USB Device: Keyboard Hub
USB Device: Apple Keyboard
USB Device: BRCM2046 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Internal Memory Card Reader
Thunderbolt Bus:
========================================
Edited by moderator to trim crash report to the essentials.
Adobe doesn’t let you attach a file to forum posts due to legal and security issues, but you can upload files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.).I have the same problem. Crazy annoying. Mac Pro. CS5.0.3 Happened before I updated as well. Working with ProRes422 and HQ clips. I've actually changed my editing habits to work around this crash bug but every now and then I forget. I am not alone. Two other coworkers have the same problem.
OSX 10.6.7
2 x 2.66 GHz Quad-Core
16GB RAM
ATI Radeon HD 5870 (had earlier version of card before - same problem)
What's going on!?
-Benny -
Premiere Pro CC repeated crashes/instability (Mac)
I am having extreme instability in Premiere CC working across several projects. Typically and image will freeze with strange horizontal distortions (see image below). Often the entire computer will crash (unable to force quite, etc). I'm working on a 2014 Mac Pro. If I bring the project into a 2013 MacBook Pro the project will not crash. Any help or ideas here would be greatly appreciated.
Hi Kevin,
Thanks for the note. I do not have NVIDIA CUDA drives installed. Although some posts have recently suggest that installing NVIDIA 5.5.28 may help. Which is counter to what I thought but I may try.
This situation is getting quite difficult for my business and has unfortunately resulted in delays for clients and soon losses of jobs for me. Extended conversations with upper level managers at both Apple and Adobe have not yielded any results yet. Regardless I appreciate your attention to this matter and hope that Apple/Adobe will move quickly in resolving this.
Regards,
Ben Silberfarb
Silberfarb - Films & Kagami Films, LLC -
Premiere Pro "quit unexpectedly" message every time I quit
There are three editors working on the latest version of Premiere. Two of us are working on the newest iMacs and one on a Mac Pro. Every time I quit Premiere on any of the computers I get a message saying that it "quite unexpectedly". It hasn't caused any noticeable problems with the projects, but I'm not doing anything funky. After I save a the project I hit "command Q". The project closes and then I wait about 10 seconds and the message comes up. Sure enough the app is still present in the dock below with the little light indicating that it's still on, but once I close the "quit unexpectedly" message, the app leaves the dock.
Like I said. I haven't noticed anything awry with the project/computer/drives, but I'm concerned that it might cause a problem. Plus it just shouldn't be happening.
Anyone else with this problem?I am having the same issue, with all of my CC apps.
Running on a month-old MacPro 6-core, dual ATI D700s, 32 GB RAM (OWC-brand). Working off an OWC ThunderBay IV configured with 4 2TB Toshiba enterprise drives.
I'll work for hours, then quit, only to be told the program "quit unexpectedly."
I did have AfterEffects crash on me once, and Premiere as well once (if I remember correctly), but I assumed both of those were normal minor hiccups for a month of work. -
After Effects sometimes won't export unless Premiere Pro quits
Has anyone run into this one? I will have both AE and Pr open and begin exporting comps out of AE (not dynamic linked comps) and the render barfs. I then exit out of Premiere, duplicate the output render that barfed in the render queue and it works fine.
Sorry guys, I'm new to posting here.
Running:
After Effects CC 12.2.1.5
Premiere CC 7.2.2
System:
Mac OSX 10.9.2
3.5 GHz 6-Core Intel Xeon E5
32 GB 1867 MHz DDR3 ECC
255GB SSD
Under Preferences > Media, I have my Disk Cache set to the SSD and it's Maximum Cache Size is at 60 GB (I've just bought an external thunderbolt drive to cache to but I haven't installed it yet).
Under Memory I have the RAM shared by Pr and AE set to 26 GB, with 6 reserved for other apps.
Should I post more info? -
PREMIERE PRO KEEPS QUITTING UNEXPECTEDLY ON LAUNCH (MAC)
Every-time i launch Premiere Pro CS3 it gets as far as the purple start-up screen and then displays a message that says "The application Premiere Pro quit unexpectedly."
What's gone wrong?
I NEED YOUR HELP!
Thanks.
Sam.VST = Virtual Studio Technology and are usually .dll's that are "plugged into" applications that are VST-aware, like Audition, PrPro, ProTools and many others. Here is a LINK with much more detail.
What can happen is that programs, like Audition (PC only), and PrPro can use many. However, they survey the system and will try to load all that they find. If the program cannot use some, what usually happens is the first loading will yield an error message, stating "Premiere cannot use the SampleTank2.dll" (for instance), and you'll never see that message again. In that case, PrPro still loads it, and no harm is done. With some, the program crashes as soon as it attemps to load them. Why some are benign and others deadly is a mystery to me. Probably how they are coded.
If you have any other audio processing programs (most likely to have VST's there), you like have some that PrPro is loading, or trying to load. Like I said, some work, some do not and some kill the program.
Just found a little trick with bad VST's: on a PC, you can take the bad VST's and drag them to the Desktop. Apparently, PrPro will not find them there. When one uses the audio program, they just point it to the Desktop, or drag the folder back to the proper program. For pre-Vista OS's, there is a script to "blacklist" VST's from PrPro, but do not think that it would apply to Mac's.
I also do not know exactly how Mac's "register" VST's, so they may not be an issue. That is what happens when a PC-guy trys to help troubleshoot Mac issues - he can get it all wrong for that platform.
Because of the nature of your crash, on a PC this would throw up the immediate red flag - VST incompatibility. Do not know if it applies to Mac. The VST issues are not the only cause for crashes upon loading, but are probably the major one. Again, this is on the PC, and all could be different on a Mac.
Good luck, and I'll post any other things to think about, should I come up with them.
Hunt -
Premiere Pro CS5.5 Won't Open - Mac
At first I had problems with AE not opening (hanging at "Initializing Media Core") and the dynamic link to some of the composiitons in my PP project, so I called support. I spent an hour and a half with a lady controlling my computer, and my AE problem seemed to disappear. We hung up, and then I opened my PP project again, and the dynamic link 'started' to work, but then PP randomly shut down. And now I have a PP problem...
I tried reopening and it loaded the project, glitched a little bit on the screen, then it said "Sorry a serious error has occured that requires Adobe Premiere Pro to shut down. We will attempt to save your current project." Now I get it EVERY time I open a project.
So I called support again, and after spending 3 hours with a guy, he told me I had to create a new user account and migrate all of my information there, but he said he could offer me no assistance in this area. I must find out for myself. So I followed the instructions here.
"pick a short user name for your new account. then run the following terminal commands
sudo mkdir /users/newshortname
sudo ditto ~ /users/newshortname
You'll have to enter your admin password (which you won't see) after the first command. that's normal. This will copy your current home directory to /users/newshortname. Then go to system preferences->accounts and create a new account with the short name newshortname. You'll get a popup saying that a home directory by that name already exists and asking if you want to use it. say yes."
As I figured (after waiting a day for all of my files and preferences to transfer to the new account) I had the same problem. I've tried deactivating, re-installing, removing the media core and then putting it back (with the help of Adobe support), and nothing is working. I'm running Mac OS X 10.6.8.
Someone, please offer some assistance. I have been out of commision from editing for three days now, and I have a bunch of deadlines coming up.
HELP ME!Hi Vinay,
1. I am using third party plug ins, and I understand that might be causing an issue, but I've also tried opening a new project with nothing in it at all, and that won't open.
2. Premiere Pro quits after the project loading bar or after I create a new project.
3. I used a lot of files! mov, mts, psd, ai, png, jpeg, and AE compositions through dynamic link.
4. The project has about five sequences. They range from 1 minute to 4 minutes.
Thanks! -
Direct link from Premiere Pro to Speedgrade won't open and stops at the post processing bar.
I've just installed the new version of Speedgrade and every time I try to open a direct link from Premiere Pro to Speedgrade, it opens and starts to load, but when the post processing bar appears it stops there and doesn't open, I've gone back to the original versions of both programmes and that same thing happens, HLEP!
Hi Vinay,
1. I am using third party plug ins, and I understand that might be causing an issue, but I've also tried opening a new project with nothing in it at all, and that won't open.
2. Premiere Pro quits after the project loading bar or after I create a new project.
3. I used a lot of files! mov, mts, psd, ai, png, jpeg, and AE compositions through dynamic link.
4. The project has about five sequences. They range from 1 minute to 4 minutes.
Thanks! -
Premiere Pro playback Footage issue - W/ After Effects Composition
Hi, I've had a very irritating issue as of late.
I've been working on a project for the past couple weeks and it has been going well.
I use AVCHD 1080p 29.97fps 24p footage. It plays perfectly fine in my Premiere Pro CS4 and After Effects CS4. I have used After Effects to replace many parts of the footage and has gone very well... Except one piece of footage.
For what ever reason, it plays terribly only when I apply an After Effects composition to it. If it is the raw footage, it's fine. If I alter it in after effects it's fine. But if it's altered from AE and I attempt to play it in Premiere Pro it repeats old frames. A mixture of stuttering and several frames back through out the whole clip.
I have NO idea what caused it or why it's happening.
Does anyone know?
Thank You.AVCHD footage is highly compressed using a GOP compression scheme. This makes it unsuitable for heavy processing and subject to all kinds of errors and artifacts when re-compressed. The best workflow is to convert (transcode) your AVCHD footage to a lossless or nearly lossless codec that preferably uses YUV color space. I work mostly on a Mac so my preference is Apple ProRez 444. I transcode everything that I work on that is going to require more than just straight cuts.
Try transcoding (Adobe Media Encoder or Compressor or even Quick Time Pro are a few of the options) your problematic clip, replace the AVCHD footage in your AE comp with the transcoded footage, then re-render to a lossless or nearly lossless codec. Bring your new render into PPro and render a preview. Let us know if this fixes your problem. -
Premire pro quit unexpectedly - where do I find my saved renditions of the time line
Premiere pro quit unexpectedly - where do I find my saved renditions of the time line - thx
there is an auto-save, which can be set to save in my documents, along with the project files, or a custom location. if you need to search for them, they use the same name as your project file, but with -1, -2, -3, -4 etc at the end, for each revision. so if needed, you can do a search for your project file on your hdd till it finds the auto-saves.
-
Premiere Pro CC quits unexpectedly
I'm running an early 2009 Mac Pro 2.66 GHz Quad-Core Intel Xeon with 12 GB RAM, on OSX 10.8.4. I've been on Adobe Creative Cloud for over a year now. Recently, I installed the CC suite, and just the other day was able to launch and work in Premiere Pro CC.
Today, neither Premiere Pro CC nor Premiere Pro CS6 will launch. Every time I try to launch either program, I get a dialog saying "Adobe Premiere Pro CC quit unexpectedly..." (yes, CS6 even has the same dialog, saying "Premiere Pro CC" the first time I try to launch it, then just crashes completely without a dialog thereafter). I've restarted, trashed my prefs for Premiere in users/user name/Library/Preferences (I've trashed all my prefs, actually), restarted again, to no avail.
I did have an issue with being forced to uninstall and reinstall Adobe Creative Cloud, but that was before the first restart, and didn't help with Premiere repeatedly blowing up on the launchpad.
The weird thing is that I haven't installed anything since it worked the other day, nor do I have any plugins or third party apps that work with Premiere that might be interfering with its launch.
Help!See if any of the solutions discussed in this thread help: http://forums.adobe.com/message/5423547#5423547
-
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.
Maybe you are looking for
-
Hi Guys, I can update my iPod from my laptop, but just copied all my file to my desktop and it won't update at all. Says it cannot read or write to disk 'my name' iPod. It still works on laptop. How can I change it so that i can update from the other
-
Officejet Pro 8620 All in One Will No Longer Scan in Color
Hello, I have an Officejet Pro 8620 all in one. I was scanning a few items last night and the first few items came out in color fine. Then all of the sudden as I continued to scan the next few images would only scan in black and white. I cannot see
-
Controlling Triggering of "WDDOMODIFYVIEW" on click of a button in view
Hi all, I have a Button in a view, on click of the button the "WDDOMODIFYVIEW" Executes before the action for the button executes. I've a requirement that the "WDDOMODIFYVIEW" shouldnt execute on click of the button in that view. Is it possible to co
-
HT202157 Apple TV is stuck on "Syncing purchased music"
After updating software, my Apple TV is stuck on "Syncing purchased music." Have given it hours and restarted with no resolution. All other features work fine. Thoughts?
-
"Variable Bit Rate Audio Not Supported"
Hello - I have several AC-3 files - sourced from satellite broadcast downloads - surround 5.1, 448kbps/48kHz - that I cannot add to DVD SP. When I attempt to import them into the assests pane, DVD SP reports they are incompatible giving the error mes