Premiere Pro CC 2014 crash and crash, and crash....
Kevin and all you other Premiere Pro CC people out there.
How long before Adobe will solve the problem of Premiere Pro crashing over and over again.
I guess there is no one reading this that could tell me "it works for me".
So Kevin (staff),
Here is the 36-line-report you requested from me.
For your information. Premiere Pro CC 2014_2 and back paddling to 8.0, they all crash.
Most crashes are freeze on timeline. Thats is, nothing moves, sometime the music track
just keep going and you can't stop it, so you have to hard quit.
My power: Mac Pro 2014, 6 core, dubble graphic card, 64 GB memory, 1 TB SS storage
This is my latest report:
Process: Adobe Premiere Pro CC 2014 [717]
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.0 (8.0.0)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Adobe Premiere Pro CC 2014 [717]
User ID: 501
Date/Time: 2015-04-03 14:55:56.729 +0900
OS Version: Mac OS X 10.10.2 (14C1514)
Report Version: 11
Anonymous UUID: 3C4BE865-15A1-83C0-2A8F-247384EECB0D
Time Awake Since Boot: 19000 seconds
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000c0
VM Regions Near 0xc0:
-->
__TEXT 0000000100000000-0000000100003000 [ 12K] r-x/rwx SM=COW /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.apple.CoreText 0x00007fff8c98db95 TLine::~TLine() + 243
1 com.apple.CoreFoundation 0x00007fff9105ca9e CFRelease + 526
2 com.apple.HIToolbox 0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
3 com.apple.HIToolbox 0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
4 com.apple.HIToolbox 0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
5 com.apple.HIToolbox 0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
6 com.apple.HIToolbox 0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
7 com.apple.HIToolbox 0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
8 com.apple.HIToolbox 0x00007fff8d59c785 HIThemeGetTextDimensions + 185
9 com.apple.HIToolbox 0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
10 com.apple.HIToolbox 0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
11 com.apple.HIToolbox 0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
12 com.apple.HIToolbox 0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
13 com.apple.HIToolbox 0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
14 com.apple.HIToolbox 0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
15 com.apple.HIToolbox 0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
16 com.apple.HIToolbox 0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
17 com.apple.HIToolbox 0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
18 com.apple.HIToolbox 0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
19 com.apple.HIToolbox 0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
20 com.apple.HIToolbox 0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
21 com.apple.HIToolbox 0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
22 com.apple.HIToolbox 0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
23 com.apple.HIToolbox 0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
24 com.apple.HIToolbox 0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
25 com.apple.HIToolbox 0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
26 com.apple.HIToolbox 0x00007fff8d604c5e _HandleMenuSelection2 + 446
27 com.apple.AppKit 0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
28 com.apple.AppKit 0x00007fff917b72f0 _DPSNextEvent + 1843
29 com.apple.AppKit 0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
30 com.apple.AppKit 0x00007fff917aa593 -[NSApplication run] + 594
31 com.adobe.Frontend.framework 0x00000001000c948d FE::MacApplication::RunSelf() + 45
32 com.adobe.Frontend.framework 0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
33 com.adobe.Frontend.framework 0x00000001000cad44 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
34 com.adobe.Frontend.framework 0x00000001000d1f25 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
35 com.adobe.AdobePremierePro 0x00000001000018ac main + 508
36 com.adobe.AdobePremierePro 0x00000001000016a4 start + 52
Hi,
Sorry to hear about the experience. Can you please try this:
Go to the following locations:
Location 1: When in Finder, click on Go > Go to Folder > ~/Library/Application Support/Adobe
Location 2: Go > Go to Folder > ~/Library/Preferences/Adobe
Location 3: Documents > Adobe
In all the locations, rename the 'Adobe' folders to 'OldAdobe'
Launch Premiere, accept the License Agreement and see if it works.
Note: You will lose your customized workspaces and keyboard shortcuts. Wait for Premiere to generate the media cache the first time you launch the project.
Also i would suggest you to make this change if the playback issue continues and see if it works better:
Under File > Project settings > General, change the Video renderer to Mercury Playback Engine software only. Click OK and select "Delete Previews"
Thanks,
Rameez
Similar Messages
-
Premiere Pro CC 2014 (8.0.1.21) crashes when opening or creating a project
I just downloaded the trial for Premiere Pro CC (2014), and the program keeps crashing every time I open or create a new project. I can idle at the "Startup Screen" but as soon as I open a project the program closes without warning. I've re-installed all Adobe products I have, re-installed the Microsoft Visual C++ Redistributable 2012 and 2013 to get new MSVCR110.dll files (which seems to be the file causing the crash) but nothing is helping. I've also looked in every thread I've found on this forum and a lot of people seem to be having the same problem, but no one had got any answers for how to solve the problem.
Anyone have a clue on what to do? According to others formatting the hard drives don't seem to solve the problem either.
Here's the crash log:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.0.1.21
Application Timestamp: 53c7b17f
Fault Module Name: MSVCR110.dll
Fault Module Version: 11.0.51106.1
Fault Module Timestamp: 5098826e
Exception Code: 40000015
Exception Offset: 00000000000740da
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1053
Additional Information 1: dac8
Additional Information 2: dac844fabf0ae09d193ac750f70263ad
Additional Information 3: 6e8b
Additional Information 4: 6e8b89b059d1639bd5ba176e9f652c56
I'm running a:
Intel i7-3770K, not overclocked
ATI Radeon 7850, not overclocked
16gb RAM
64-bit Windows 7 Professional with Service Pack 1Me too with this one have it randomly when just opening the same project and begining to edit
had it happen about 4 times now.
Latest update
Microsoft Visual C++ Runtime Library
Program C:\Program Fi...
R6025
- pure virtual function call
[ok]
Adobe Premiere Pro CC 2014.1 has stopped working
roblem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.1.0.81
Application Timestamp: 5426694c
Fault Module Name: MSVCR110.dll
Fault Module Version: 11.0.51106.1
Fault Module Timestamp: 5098826e
Exception Code: 40000015
Exception Offset: 00000000000740da
OS Version: 6.1.7601.2.1.0.256.1
Locale ID: 2057
Additional Information 1: a22a
Additional Information 2: a22a26525c716a6a7fdf0a84944bf385
Additional Information 3: 9245
Additional Information 4: 9245cf38809b383bd6a86e3f052c9114
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\Windows\system32\en-US\erofflps.txt -
Why can't Adobe Premiere Pro CC 2014 Time remap Audio and Video together?
In case you didn't notice, my question is WHY. I don't know why Premiere Pro can't do this. From what I understand at the moment, the only way to time-remap audio in any way shape or form using Adobe software is through Adobe After Effects, which my computer has absolutely no chance of running ever. I know how to do regular stretching of audio in both Audition and Premiere Pro, but apparently I can't time-remap audio using either of these programs.
So why can't Adobe Premiere Pro time remap audio along with the video? What's the reason that it can't? It's a massive disappointment and would be very impressive to see accomplished in the future. If it's possible to time remap audio and video together in After Effects, that's great and all, except for the fact that I can't use that program. Why can't it be done in Premiere Pro and will it ever be possible in Premiere Pro?
Also, will time remapping audio become possible in Audition someday?That sounds like a great idea. File a Feature Request:
Adobe - Feature Request/Bug Report Form -
I paid but Premiere Pro CC 2014 is still "Trial" and asking for license key.
Please help - this is very frustrating and poor service / software performance from Adobe. I have wasted hours trying to resolve this and can't figure it out. I have paid for a "Complete" monthly service but the Adobe app on my computer (Mac, OS Yosemite) acts as though nothing has changed and still refers to countdowns on trials for other software as well. Have I just paid for nothing?
You have activated the CC once today , hope the issue is resolved, still I would like to mention that
The CC does not needs any serial number, it is based on Adobe ID.
In case you are being asked for serial number then you can refer to.
Creative Cloud applications ask for serial number
Re: Invalid serial number?
Regards
Rajshree -
Premiere Pro CC 2014 imported video length mismatch
I've got a problem in Premiere Pro CC 2014 where the audio and video get out of sync the farther you go into the imported clip. While troubleshooting I noticed that Premiere isn't properly reading the video length of the imported file. Windows reports the right length, as do VLC and Handbrake, but Premiere shows a time about 30 seconds shorter than the real file. I've included the file info from MediaInfo and Premiere here. Windows reports a (correct) length of 1:56:39. This happens on two different Windows computers both running the latest release of Premiere Pro. Has anyone seen this? I've tried to search for similar issues but haven't found anything like this. Thanks!
----- MediaInfo -----
General
Complete name : C:\Users\aprice\Desktop\CI_EOUGame.mp4
Format : MPEG-4
Format profile : QuickTime
Codec ID : qt
File size : 3.22 GiB
Duration : 1h 56mn
Overall bit rate : 3 954 Kbps
Encoded date : UTC 2015-01-10 02:38:58
Tagged date : UTC 2015-01-10 04:35:38
Writing library : Apple QuickTime
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings, CABAC : Yes
Format settings, ReFrames : 4 frames
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 1h 56mn
Bit rate : 3 756 Kbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Variable
Frame rate : 29.871 fps
Minimum frame rate : 7.500 fps
Maximum frame rate : 30.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.061
Stream size : 3.06 GiB (95%)
Language : English
Encoded date : UTC 2015-01-10 02:38:58
Tagged date : UTC 2015-01-10 04:35:38
Audio
ID : 2
Format : AAC
Format/Info : Advanced Audio Codec
Format profile : LC
Codec ID : 40
Duration : 1h 56mn
Source duration : 1h 56mn
Bit rate mode : Constant
Bit rate : 192 Kbps
Channel(s) : 2 channels
Channel positions : Front: L R
Sampling rate : 44.1 KHz
Compression mode : Lossy
Stream size : 160 MiB (5%)
Source stream size : 160 MiB (5%)
Language : English
Encoded date : UTC 2015-01-10 02:38:58
Tagged date : UTC 2015-01-10 04:35:38
----- End MediaInfo -----
----- Premiere -----
File Path: C:\Users\aprice\Desktop\CI_EOUGame.mp4
Type: MPEG Movie
File Size: 3.2 GB
Image Size: 1920 x 1080
Frame Rate: 29.97
Source Audio Format: 44100 Hz - compressed - Stereo
Project Audio Format: 44100 Hz - 32 bit floating point - Stereo
Total Duration: 01:56:09:09
Pixel Aspect Ratio: 1.0
----- End Premiere -----Thanks Ann. I noticed that in the MediaInfo output and thought it was strange, since I don't typically deal in variable frame rate footage. After converting it to constant frame rate with Handbrake the problem appears to have been resolved. I'm working to find out if the program that records the video can be switched to constant frame rate mode to fix this issue permanently. Thanks for the help!
-
Porque Premiere Pro CC 2014 antes si reconocia archivos m2ts y ahora no los reconoce
Tengo Premiere Pro CC 2014 desde hace unos meses. El ultimo trabajo lo hice con el con archivos M2T. Llevo trabajando desde la version CS5 sin problemas con este tipo de archivos.
Por un cambio de disco duro de arranque tuve que formatear. Descargue de nuevo de Creative Cloud, Premiere Pro CC 2014 y mi sorpresa fue que al abrir el mismo archivo creado en
el mismo ordenador y con la misma version de Premiere, me dice "Formato de archivo de compresion no admitido". ¿Que puedo hacer para recuperar la posibilidad de seguir editando
este tipo de archivos en Premiere?Thanks Kevin.
15 days ago undertake a project where work editing a m2t file with other files in Premiere Pro CC 2014. I finished my work and deliver. Use this 150 times m2t file in this project.
7 days ago change my boot disk by one solid state. I had to reformat my hard drive. Then install Premiere Pro CC 2014 and try to open the same project created with Premiere Pro CC 2014 15 days before and tells me that does not support the compression type of this file and no connection appears in red.
This is my problem: if admitted of 15 days before such m2t file after formatting and reinstalling, no longer supported? I have worked with Premiere Pro CS4 and then since I updated to 2014 CC.
I hope this explanation helps you to help me. -
Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly
Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out. -
Premiere Pro CC 2014 crash when I Click and Drag
Hi All, I have a problem with Premiere CC 2014 that is driving me crazy!
The issue is as follows:
If I try to drag a clip, sequence, effect or transition anywhere within the premiere, it will crash - with "Sorry, a serious error has occurred" message. The program will crash, quit and the saved recovery project is usually healthy (luckily!). BUT, as soon as I've re-started the program, and reloaded the project - or any project for that matter - the problem persists. As soon as I click and drag, Premiere crashes!
In order to 'reset' this, I have to restart my machine. Once I have done so, I can continue editing as normal for a while (not long, perhaps up to an hour, or so) but eventually, it WILL crash again. I've not been able to work out what I have to do in order to trigger this - it seems random. But once it's happened, only restarting my computer will resolve it - and then only temporarily.
Here are all the facts:
The crash ONLY happens when I drag something... This can include moving a clip on the timeline, dragging a clip form the source viewer or project window, dragging an effect or transition.
The crash happens after I have clicked, as soon as I start to move my mouse.
I CAN click and drag to extend in and out points on the timeline, and I can do 'insert' edit using the button on the source monitor. No crash here.
The footage plays fine.
I am trying this on a CLEAN OS X install, with only Adobe packages installed, to eliminate any potential of interference from other programs. There are no third party plugins or drivers installed. No user data installed either (preferences, photos, documents, etc) - as fresh as it comes!
I am not running Time Machine in the BG
My system is: Macbook Pro 2011, 16GB Ram, 1tb SSD, OS X Yosemite 10.10.1. Intel Graphics card, so no option to turn on or off hardware acceleration. It is set to software only.
I have tested this with projects and footage on an external drive, as well as internal, same issue.
I noticed the issue had started on, or around 25-27th November 2014.
Interestingly, I have noticed that once this crash has occurred in Premiere, a similar problem will occur in After Effects as soon as I drag a file or layer... doesn't matter what the layer is. The crash seems less elegant here, I don't get an error message, it just freezes and I have to 'force quit'. Again, the problem persists until the machine is restarted.
I have been using my macbook and premiere pro cc 2014 on Mavericks for a long time, and had no problems - so I know it should work fine! The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups, I installed a few new fonts and any CC updates that happened in the background... I can rule out most of these because of my fresh install, with no user data, fonts plugins or time machine to confuse matters... It must be an Adobe bug with Yosemite!
Any ideas?
Thanks so much in advance!!Hi Vince,
vince_email wrote:
...The only things that changed were an update to Yosemite, I started using Time Machine to make regular backups...
Please check this blog post. Updating from Time Machine can cause this issue: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later).
Thanks,
Kevin -
Adobe Premiere Pro CC 2014 keeps lagging and crashing
My Adobe Premiere Pro CC 2014 keeps lagging and crashing to a point where I cannot do my job. When I open my premiere file, I can work on my timeline for maybe two or three minutes before it lags, freezes, and then finally crashes. I'm at a loss of what exactly is causing my problem because I edit primarily H.264 files and my sequences are not complex in any sense of the word. I've been dealing with this for days and I cannot seem to find a solution. If anyone has any advice please let me know because I am desperate. Thank you.
Specs:
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: Quad-Core Intel Xeon E5
Processor Speed: 3.7 GHz
Number of Processors: 1
Total Number of Cores: 4
L2 Cache (per Core): 256 KB
L3 Cache: 10 MB
Memory: 16 GB
Boot ROM Version: MP61.0116.B05
SMC Version (system): 2.20f18
Illumination Version: 1.4a6Hi Dana,
Can you go to File-Project Settings-General and change the video renderer to Software Only Mode.
Check if that works or not.
Are you using any third party plug-in's for Premiere Pro?
Thank You
Arjun -
Premiere Pro CC 2014 playback freezing and crashing with new iMac i7
Using Premiere Pro CC 2014 and having constant playback freezing and software crashes on a brand new iMac i7.
Here are the specs:
iMac i7 4.0GHz 5k Retina
32 GB Ram
AMD Radeon R9 M295X 4GB graphics card
512GB Solid State Drive
I was on chat yesterday with an Adobe tech. Although playback/render settings show the OpenCL option to utilize the AMD graphics card for processing, I was advised to switch to "Software Only" as that card is not supported yet. I had to re-render my 45 minute documentary (which doesn't appear to be any faster than it was on my old 2011 iMac by the way) and it still has the same issues.
So frustrating? Anyone else experiencing this? Any advice? I hope I didn't just buy this "super machine" in vein.
Thanks,
JasonHi All,
Taking some tips from Kevin Monahan. If you haven't already gone through this list please do so.
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe preference files are set to read/write
Delete media cache
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
Best,
Peter Garaway
Adobe
Premiere Pro -
Premiere Pro CC 2014 Crashing and Bogging Down on Documentary Film Project
We have been working in Premiere on this documentary film for months.
As we reach completion it is beginning to really bog down and crash a lot.
Equipment is
iMac 27 inch 3.5 GHz Intel Core i7 Late 2013 Model
Apple Cinema HD Display
32 GB 1600 Mhz DDR3 RAM
NVIDIA GeForce GTX 780M 4096 MB Graphics Card
1TB internal SSD Drive
We are running Premiere Pro CC 2014.0.1 and have remained there because we don't want to upgrade the software in the middle of the project.
The media is all on the external drive. It's a USB 3.0 connection. There is quite a lot of footage that we are working with.
We do have some After Effects comps that are linked in the project and we have exported the ones that are complete as QuickTimes to try to stop that from bogging us down.
Any advice on how we can manage this crashing and freezing problem would be much appreciated.
We don't have the cash to upgrade the computer and it has been working pretty well for us so far.
Here are things we have done:
Made a smaller timeline because we were working on one that was the entire movie.
Turned off the secondary monitor and unplugged it.
We are looking at moving the render cache off the external drive to a thunderbolt drive, but I'm concerned that this may take a long time.
Any recommendations would be greatly appreciated.Splitting up the read/write items is rather a key to getting smoother operation out of PrPro. Either that or putting things on a large RAID-0/5, this sort of thing is covered over on the
Tweaker's Page ...
http://ppbm7.com/index.php/tweakers-page
And I highly recommend you take a look. Their info isn't just "we think ... " ... but the results of many many carefully crafted test sequences run on many machines with all sorts of hardware bits & pieces. You can also register, download the PBM test and run it on your own machine. It takes only a little while to do so, and with the logger app that's included and posting the results back to them, you can get a very good breakdown on where your machine is doing ok ... and where any choke points are occurring.
I think this would be good for you right now ... you need to get stuff done, not guess & try things.
Neil -
Premiere Pro CC 2014 freezes frequently and crashes
Since upgrading from Premiere Pro CC to Premiere Pro CC 2014 my projects crash in regular intervals, which didn't happen before.
All my settings and presets have been pulled across fine, but suddenly relatively slim projects get stuck during editing, rendering or exporting. The progress bar stops, the preview screen freezes and that's it. I can only radically crash the sucker. I did delete all preview files and it improved marginally... only that the time until it froze took a few minutes longer.
I'm on 64bit high-end Windows 7 machine and have never had this problem with previous versions of Premiere Pro.
Very frustrated.@bendubb37: I'm not the least bit defensive about complaints regarding the stability and general quality of the program. As a quality engineer on the Premiere Pro development team (not a member of the technical support team), I'm quite familiar with many if not most of the problems--both those that are legitimate bugs in our code and those that result from conflicts with OSes, hardware, codecs, other programs, etc. I genuinely appreciate having customers come to this forum to report issues they're having. Such reports sometimes help us identify bugs that we weren't aware of, and they always help us to prioritize bugs to fix based on which issues are biting the most customers and having the greatest impact on their productivity and satisfaction. And naturally I understand the frustration and anger of customers who are wrestling with one problem or another in the program.
What I took issue with was cutco's derision of a perfectly valid troubleshooting step recommended by a technical support agent and his assertions that a) "This community is kind of useless" and b) "Adobe is absent." Cutco graciously acknowledged that he had let his frustration get the best of him.
As to the oft-repeated claim that CC2014 is buggier and less stable than prior versions, I submit that it's a problematic claim to substantiate, at least based on anecdotal personal experience or taking the pulse of this forum & others. There's no question that some customers who enjoyed smooth sailing with an earlier version are experiencing problems with CC2014. But I know for a fact that this release included fixes for a significant number of bugs, including crashers, so many other customers who were having problems with earlier versions are now cruising along without a hitch (or at least without those old, fixed hitches). Alas, those people are not frequenting the forum to sing the praises of CC2014.
My point here is simply that claims about the relative quality of one release versus others can be a distraction from the more important--and much more concrete--fact: a certain number of customers using CC2014 are having Problem X, which didn't happen in CC7.x. The more we can learn about Problem X--and the more clearly we can differentiate X from Y and Z, which may manifest similarly--the sooner we can nail down the cause.
Don't get me wrong: there is an objective trajectory of a product's quality. Unfortunately, even when you have a large pool of data in front of you, the trajectory doesn't lend itself to quantification. You can't simply count the number of deferred bugs, for instance, because not all bugs are equal. You can't even go by the number of known crashers because some are extreme edge cases while others lurk in the path of mainstream workflows. That said, for people like me who spend our working lives trying to deliver the highest quality possible, the trajectory our program's quality is a common topic of discussion. -
Latest Premiere Pro CC 2014 Freezing and crashing. Why?
While editing a project everything runs smooth for a while, but then PPCC will freeze, become sluggish and or will crash from time to time. I have a new MacPro (Late 2013) 3.5 GHz 6-Core Intel Xeon E5, 64 GB ram, with duel AMD FirePro D700 graphics cards. I purchased my machine a few months ago. in Addition I'm editing off of a Thunderbolt 2 raid SSD drive. SO I don't know why my projects are freezing and crashing. This happens weather I'm editing DSLR 1080 footage Or RED 6K Footage. My system has more than enough power to handle my project, but premiere works for awhile then doesn't play nice. Why? PPCC 2014 by far has the best tools for editors in my opinion but if its not as stable a FCPX then why should we continue to use it. in addition, yes I have done a complete clean install so there should not be any conflicts.Running OS X 10.10.1
My Premiere Pro CC 2014 also freezes when I try to export. I do not get any error messages, it just freezes and I have to restart my computer. The only way I can render is to Queue to Media Encoder CC 2014.
I have tried posting my problem many times but this Community Forums will not accept my post and keeps telling me to 'try again later .m4'. -
Adobe Premiere Pro CC 2014 Crashing very often! Please Help!
Hello,
I am currently editing my first feature on Adobe Premiere Pro CC 2014 and it is currently up to date.
I am editing on a iMac 27in, late 2013 brand new computer.
Processor: 3.5 GHz Intel Core i7
Memory 32GB 1600 MHz DDR3
Graphics: NVIDIA GeForce GTX 780M 4096MB
System: OSX Yosemite V 10.10.1
The project is located on a 8TB G Drive
7200 RPM
High Performance ThunderBolt drive.
Details of the project:
I am currently working on a fine cut of 5K Red Footage that is being cut in the RAW.
I work at 1/2 quality settings and have no lag.
The timeline includes limited stacked video files and various mp3 audio files.
The Problem:
Lately, the program will randomly quit or freeze up 4-5 times during an 5-6 hour edit session.
Many times it is random, however, it seems to happen often if I accidentally click on the end of a clip on the timeline and it goes to switch into trimming mode.
Also, it will randomly go into the "pinwheel of death" out of nowhere followed by "Adobe CC is not responding."
My project file is just about 15MB now.
What is causing this reoccurring problem?
How can I make it happen less? I have scoured the forums and found similar articles but no helpful solutions.
I have recently turned auto save on to save every 2 minutes because there have been more than one occasion where I lost A LOT of work because of this issue.
I am about two weeks out from picture lock delivery and this issue is driving me crazy and loosing me a ton of time.
Please help or let me know if any more additional information can help solve the issue.
I have sent in well over 25 error reports already.
Thanks,
Thomas.I think I may have found the solution...
I completely removed the Premiere Pro folder under User > Documents > Adobe and so far it seems to have solved the problem.
I of course backed up my projects and than deleted this folder. So far it seems it worked.
I'll know for sure in a day or two, but after constantly crashing, Premiere hasn't crashed for the last 4-5 hours of work.
Goran -
Premiere Pro CC 2014 crashes when loading project file
Hi guys, any help on this is much appreciated as I have a job due in 18 hours and I'm in big trouble if I can't fix this.
I've been editing a project in Adobe Premiere Pro CC 2014 (updated to the latest version) and when I tried to access the same file today it is giving me the error message:
'Sorry, a serious error has occurred that requires Adobe Premiere Pro to shut down. We will attempt to save your current project.'
I had saved other version files and they all seem to be working properly so I know it's not my HD that is corrupt. In fact my suspicion is that it has something to do with a blur effect i'm using. The only problem is, I can't even access the file to delete the effect as the project file won't open.
Information about my computer:
I am using a Macbook Pro
OS X version 10.9.4
2.6 Ghz Intel Core i5
Memory 16 GB, 1600 MHz DDR3
Any suggestions/comments would be appreciated.Guys I solved my own problem - thought I'd share with you how in case anyone else is having this problem -
I came across this thread
Premiere Pro CC error message and crash
which had the suggestion -
"Do tou have after effects installed? If yes, please try to import the main sequence into it and then export it as premier pro project from file/export ootion and then try to open that in premiere pro."
This didn't work for me too but I did try and import my existing project into a new project and copy all the files over. Works fine now.
I don't know if I will have the same issue again tomorrow so I'm going to render out a super high res video before I close premiere just in case
Maybe you are looking for
-
I have installed Adobe Creative Cloud for teams CC Packages which says that Acrobat XI Pro is installed. Your support page says it does not install Acrobat and I have to look in the Extensions folder for an MSI file. I have run a number of searches
-
Even if an iPod 5 is Stolen , and i buy another new one can, my old iPod5 deletes what ever its was on my iCloud account? and transfer the same thing as my old one to a new one?
-
How do you burn photos to CDR from Iphoto. 9.5.1
How do you burn photos in Iphoto 9. You used to do it from Share and now I can't find the instruction.
-
When I start up my PC I get the following message. Apple Sync Notifier.exe entry point not found. Sqlite3_wal_checkpoint could not be locatedin the dynamic link library SQLite3.dll. What do I need to do to correct this?
-
Hi Consultants. Does anyone know how to stop the canceling the FYI notification after a atual notification had timed out? We have reuirement to send FYI notification after timeout the remider approval notification. i addeed FYI notification but when