Premiere Pro CC 2014 Playback Issue / Crash Mac Pro 2011
Hi,
I've been having a big crash issue on Premiere Pro CC 2014, since the 2014.1 update.
2014.0 has been working fine this year but the update has crashed some of my biggest current projects.
Programs just starts fine, workspace responds, but anything related to playback just crashes or freezes Premiere.
My config:
Mac Pro Mid 2010
Processor : 2x2,93 6-core Xeon
Ram : 24Go 1333
2x ATI Radeon HD 5770.
I've been reading all major topics on this, this i did :
- disable Mercury Transmission
- Flushes Premiere cache
- Reinstall premiere
- Updated to Mavericks (issue happened both in 10.9 and 10.10 - thought updating drivers+opencl would help, then again no)
- Repaired permissions
- Tried with another user session
… and so on.
Nothing yet has solved my issue, anyone to help me on this major trouble ?
Thanks in advance, best regards !
Paul
Hi Paul,
Try the following:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Ensure Adobe folder preferences are set to read/write in all 3 locations.
Delete media cache
Remove plug-ins
Repair permissions
In Sequence Settings > Video Previews, change the codec to one that matches your footage
Disconnect any third party hardware
Disable App Nap
Reboot
I placed the chief culprits in bold.
Report back if anything here worked for you.
Thanks,
Kevin
Similar Messages
-
Performance Issue Premiere Pro CC 2014 with Late 2013 Mac Pro
Hi all!
Im working Premiere Pro CC 2014 on a Late 2013 Mac Pro 6 core D700s and 32GB RAM on OSX 10.9.4
After the 2014 update i have experience some drop frames and hangs with a new 1080p timeline project.
And it later results in software hang and crashing . even after a quit (force quit) and re-poen, it seems to happen again and again.
Even after a system reboot seems to be fine at first, but it still crashes on the project.
Tired to render the timeline and still the same. Also tried to delete rendered file and play right with timeline with yellow bar, same.
Even drop the preview playback to 1/2 and still..
files are mixed 1080p footage from Canon 5d3, 60D, T2i.
I have 3 layers (interview video with different angles) and a title layer (hard subtitle)
had some light color correction with fast color corrector and a sharpening on the 5d3 layer.
Ive work with the CC premiere pro before with mac pro and everything is fine and never hand an issue.
All my memory setting are set for performance and i have open GL on my D700s
Im not sure if this a software issue or someone my hardware is not working right?!
Thanks in advance!I am having the same issues.
Im working on a late 2012 iMac, 3.4 GHz Intel Core i7. 32 Gb ram, NVIDIA GeForce GTX 680MX, OS X 10.9.4.
I'm editing RED footage, about 3 TB worth for this project from a Promise Pegasus drive.
The software really slows down when using the TYPE tool and also when scrubbing through footage.
When I attempt to quite the software and restart, the interface goes away but the app is still running but says "not responding" when I attempt to force quit.
If you've figured it out since then Id love to know what works.
Thanks!
G -
Premiere Pro cc 2014 8.2 crashing
I’ve been working on a documentary with several types of footage/stills. Crashes have become more frequent as I get further into the project. Lately it’s been freezing up to the point where I have to force quit and I’ve also gotten the “Sorry, a serious error has occurred” where it has to restore the file. It's also happening with a new project file which has only one type of footage in it.
My machine’s getting old and I plan on replacing it soon but it still works fine with FCP7, Avid, After Effects, etc. Here are the specs:
2.8 GHz Intel Core 2 Duo
4 GB 1067 MHz DDR3
NVIDIA GeForce 9400M 256 MB
Footage is on an external Glyph drive 2TB
MacBook Pro mid-2009
OSX 10.9.5
Here’s what I’ve tried:
-I made sure my Adobe folder preferences are set to read/write.
-I’ve tried recreating the preference file (ctr+alt+shift) several times while starting the program. This seemed to help the first time I tried it but then it started crashing again and eventually gave me the “Sorry, a serious error has occurred” message again.
-I’ve cleaned the media cache
-The only plugin I have installed is FinalPlug (a compressor) but I haven’t been using it and don’t see that anyone’s listed it as being problematic with PP CC, so I haven’t uninstalled it.
Should I update the video driver? Can anyone advise me on how to do that?
Thanks!Hi, I have something similar to this happening to me. Does a crash report box also pop up for you? I get one, but it's for Apple, not Adobe. I didn't have my problem until getting a new Mac with Yosemite installed, so it shouldn't be your machine's age.
Part of my error message looks like this:
Crashed Thread:
0 Dispatch queue: com.apple.main-thread
Exception Type:
EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:
KERN_INVALID_ADDRESS at 0x0000000000000000
VM Regions Near 0:
-->
__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.adobe.AudioSupport.framework 0x0000000103d7f8d0 ML::Device::GetNumberOfPhysicalChannels(unsigned int, bool) + 80 -
Premiere Pro CC 2014.2 often crashes (Windows)
Hi...i'm on windows 8.1 and using premiere pro cc 2014.2.... there have been bugs and really need help as this problem has affected my workflow and i even can't get a solution of this.....
1. There are times my files will be offline and have to reconnect them one by one....and sometimes i have to restart the software or computer to reconnect them back....there are also times when i reconnect them and get a "files are corrupted" error but they can be opened in redcine x...
2. I also get error when trying to reconnect audio files stating a "header error....
3. If i mark in and out and try to copy paste from one sequence to another, the computer will not respond and freeze....
I'm using a asus g750jm, i7 2.4ghz, with 24gb of ram.....
The sequence that i use to edit these red raw files are just 1024x540....
Need serious help here...thank you...Hi Nazim,
You´re not alone! It looks like the whole world of Mac users crashes when inside Premiere Pro CC 2014.
I´ve tried back peddling to early version (8.0) same problem.
So this is for Kevin (who probably will tell me to stay with the Mac-probelm-users-thread):
Here is my latest crash report (out of hundred):
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 -
Premiere Pro CC 2014 & Media Encoder Crash when rendering
Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
Here is the log from Event Viewer:
Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
Exception code: 0xc0000005
Fault offset: 0x00000000000e7f80
Faulting process id: 0x650
Faulting application start time: 0x01cfb99562fe469a
Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
Faulting package full name:
Faulting package-relative application ID:
Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x000000002c2cce3d
Faulting process id: 0xcf8
Faulting application start time: 0x01cfb9906060796e
Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
Faulting module path: unknown
Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
Faulting package full name:
Faulting package-relative application ID:More hardware information might help someone give you an idea
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
or
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/ -
I have this on both machines running 10.10.1 OS X and AE 2014. I see on line that others are having this issue. I think it needs a Patch ASAP.
Hello. Basically I can create a new comp that is set to 1920 x 1080, @ 30 frames per second for 1 minute TRT. I create a new solid layer, say red. I hit space bar or play on the screen, and it does not play in real time. ITs on my Imac as well. same OS and Same Version software.
After effects running prerendered @ 17 FPS and fluctuating up to 20 when it should be playing @ real time. After effects 2014 CC , brand new Mac pro strapped 10.10.1
created by Dave LaRonde in After Effects - View the full discussion
Well, before you hit the panic button, why don't you tell us precisely what you're doing when AE plays at 17fps -- the keys you hit, the buttons you click to begin play.
If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7102588#7102588 and clicking ‘Correct’ below the answer
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:
Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7102588#7102588
To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following"
Start a new discussion in After Effects by email or at Adobe Community
For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.
Geoffrey M. Wetzel
[email protected]
[email protected]
302.353.0798 -
Is it possible to virtually bypass the battery on a macbook pro (retina 2014) and power the mac directly via AC power?
E.g. Dell allows you to plug the laptop into AC power but prevent battery charging.
Note: I do not want to physically remove the battery.
If there isn't an option on Mac OS, is there anything I can download to bypass the battery when I want?Thanks for linking me! Wow I had no idea the clock speed would be cut so severely! What a bunch of rubbish, as if the AC won't provide enough power!
I guess the only solution to my question would be an app which virtually disconnects the battery but tricks the mac into thinking the battery is still connected. I'm just surprised Apple haven't yet started to build prisons for the government - considering how well they lock up their software and hardware! -
New Mac Pro 2.8 vs. Refurbished Mac Pro 3.0?
I'm trying to decide between a new Mac Pro 2.8 and a refurbished Mac Pro 3.0. The refurbished 3.0 is roughly $375 less. I'll be using this for a graphic design business, so we'll be routinely using CS3. Help me decide.
I was faced with the same question at the end of 2007. I had even picked up a new Mac Pro 2.66 quad core, but did not open it. I decided to return it, and fortunately the next day, the 2008 Mac Pros came along. I went with the 8 core 2.8. The 3.0 from 2006/2007 is already dated, and there is no way you will make it faster without spending a ton of money. The refurb unit you are looking at is 2 years old in design. It first came out in August 2006. The expansion slots are all PCIe 1.1 if I recall. With the newer machines they have 2 slots that are PCIe 2.0.
You also have to factor in the upgraded graphics card. Barefeats.com did a little comparison of the video cards, and the 2600 XT fared very well against the 1900XT that is what most folks upgraded to with the 2006 3.0 GHz Mac Pro. The 1900 xt is not a bad car, however, there is no guarantee that you will ever be able to put newer cards in that older machine. There is conjecture that the 8800 GT card that was released for the Early 2008 Mac Pros may work in the older units, but that is not a done deal yet. The 2600 XT does fairly well with Motion.
The 3.0 also ships with 1 GB of RAM while the 2.8 8 core ships standard with 2 GB of RAM. Granted, you will want additional RAM, but you still come out ahead with the early 2008 8 core unit. You do not need to overspend on RAM. Otherworld Computing sells great RAM. I have Apple RAM, OWC RAM, and the Techworks RAM (sold by OWC) in my Mac Pro. I cannot tell the difference and I have had no crashes. 4 GB of RAM is about 219 bucks at OWC.
As for any video or graphics work that you may want to do, the 8 core unit is much more robust for crunching the compression. Compressor can take advantage of the multiple cores. Barefeats.com also did some benchmarking of the 2.8 octo core and the 3.0 octo core unit from 2007. The early 2008 unit was just about even because of the improved L2 Cache and the improved front side bus speed. Overall, the early 2008 units are great performers. The 2.8 quad core should be just about even with the 3.0 quad core in terms of speed. The 2.8 octo core is faster yet, and is about even with the older 3.0 octo core MP. The reason for this is that the 2008 Mac Pros have a faster front side bus and a bigger L2 cache.
I think you are wasting your money going with a discontinued unit, that has questionable upgradeability paths in regards to video cards, fewer cores, a slower bus speed, less RAM, slower RAM, and less L2 Cache memory. As an aside, the early 2008 Mac Pro features PCIe 2.0 slots, whereas the 2006 Mac Pro does not.
As for adding a second DVD drive, you can get the drives for about 30 dollars. They are not expensive like they used to be.
In regards to all of the stuff floating around about Leopard, I do a lot of graphics, including Final Cut Studio 1, and Creative Suite 3. I have had few issues. With the latest Leopard upgrade, and the recent updates with the other programs, Leopard runs every bit as good as Tiger did. The only recurring theme I have seen that has not been resolved with the newer systems and hardware has been the drivers for audio gear and recording. Otherwise, the new machines are very stable and speedy.
Other folks have went the refurb way and have been very happy. Some folks went with the newer machine, and they are happy. Only you can decide what makes the deal the best for you. Do not base everything on the higher priced Crucial RAM. Oh, one other thing that you get with the early 2008 Mac Pro is a nifty aluminum keyboard. After using this keyboard you will not want to use anything else.
Good luck with your decision. I know it is difficult. -
I am trying to do a migration transfer from an older Mac Pro, running Leopard, to a newer Mac Pro, running Lion. There is a step that asks for a "passcode" to proceed. I have no idea what that passcode is. It seems to want a numeric code. Has anyone had this experience?
This general-purpose article gives detailed step-by-step instructions for using Migration assistant, Setup Assistant, and other mehtods, and discusses the Pros and cons of each mtheod. It is very approachable and easy to understand. Wriiten by Pondini, the resident Time Machine guru.
Setting-up a new Mac from an old one, its backups, or a PC -
hi what antivirus is best in macbook pro???and may mac pro is go slow?
Forget about viruses, and don't install Sophos, which is worthless.
First, back up all data immediately, as your boot drive might be failing.
One possible cause of a slow user interface is a large number of image or video files on the Desktop with preview icons. If you have more than a dozen or so such files, move them to another folder.
Otherwise, take these steps when you notice the problem.
Step 1
Launch the Activity Monitor application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Activity Monitor in the icon grid.
Select the CPU tab of the Activity Monitor window.
Select All Processes from the menu in the toolbar, if not already selected.
Click the heading of the % CPU column in the process table to sort the entries by CPU usage. You may have to click it twice to get the highest value at the top. What is it, and what is the process? Also post the values for % User, % System, and % Idle at the bottom of the window.
Select the System Memory tab. What values are shown in the bottom part of the window for Page outs and Swap used?
Next, select the Disk Activity tab. Post the approximate values shown for Reads in/sec and Writes out/sec (not Reads in and Writes out.)
Step 2
You must be logged in as an administrator to carry out this step.
Launch the Console application in the same way as above. Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left.
Post the 50 or so most recent messages in the log — the text, please, not a screenshot.
When posting a log extract, be selective. Don't post more than is requested.
Please do not indiscriminately dump thousands of lines from the log into a message.
Important: Some personal information, such as your name, may appear in the log. Edit it out before posting. -
Wish to upgrade from SL to ML on Mac Pro. Spec says only on Mac Pros from early 2008 but unsure how old my Mac Pro is as it is from work and there are no records. How do I find out if ok to upgrade to ML?
You can write to Apple with the serial number and they can tell you exactly when your MacPro (as opposed to Mac Book Pro) was manufactured.
And in the Apple menu > about this Mac > more info > there should be sufficient detail to narrow it down.
EDIT. These are the specs for the April 2007 version.
"Suggested"
"Best"
Speed of Xeon Processors:
Dual Core 2.66 GHz x2
Quad Core 3.0 GHz x2
Memory:
1.0 GB
2.0 GB
Video Card:
NVIDIA GeForce 7300 GT
ATI Radeon X1900 XT
Video Memory:
256 MB
512 MB
Hard Drive Capacity:
250 GB
500 GB
Optical Drive:
16X "SuperDrive"
16X "SuperDrive"
Price: -
Can a shell for mac pro 13" be used with a mac pro Retina ?
Can a shell for mac pro 13" be used with a mac pro Retina ?
Thank you.No.
The entire enclosure is tuned for both external jack placement, EMI-RFI radiation, airflow, and for cooling. You need exactly the correct shell and fans for the electronics you wish to install in it. -
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 -
Issues with mac pro 2014 and Adobe CC
Having major issues with my New Mac Pro since installing 10.9.3. The issues are with render in Adobe CC products and glitches on displays.
Model Name: Mac Pro
Model Identifier: MacPro6,1
Processor Name: 12-Core Intel Xeon E5
Processor Speed: 2.7 GHz
Number of Processors: 1
Total Number of Cores: 12
L2 Cache (per Core): 256 KB
L3 Cache: 30 MB
Memory: 64 GB
Boot ROM Version: MP61.0116.B05
SMC Version (system): 2.20f18
Illumination Version: 1.4a6Well known issue and no solution yet. There is nothing wrong with your computer. http://9to5mac.com/2014/05/21/os-x-10-9-3-breaking-mac-pro-graphics-card-compati bility-with-critical-pro-apps/
-
Adobe Premiere Pro CC 2014.2 Unusuable - Crash
Hi, just updated to Premier Pro CC 2014.2, and it's unusuable.
Drivers all updated, Windows 7 Pro. Intel Core i7 8GB Ram 64 bit
Application crashes within usually 1-2 minutes of launch at random moments:
Import transparent PNG 900px wide - instant crash
Import non transparent PNG similar size - no instant crash, can add transitions, but crashes within 2 mins
Import video sequence - instant crash on preview in media browser
Create colour matte - instant crash
Examples as follows:
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: 0x0000000000000004
Faulting process id: 0x1ff8
Faulting application start time: 0x01d0297d48ce56a9
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: igdrcl64.dll, version: 10.18.10.3960, time stamp: 0x54299cb8
Exception code: 0x40000015
Fault offset: 0x00000000000b7a16
Faulting process id: 0x83c
Faulting application start time: 0x01d0297bd75304ee
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\system32\igdrcl64.dllHey Nick,
I had exactly the same problem. Crashes after 1-2 minutes of random activities.
I ended up going down to 2014.0 and then upgrading to 2014.1. Everything is working perfectly now.
If you are interested to do the same you can go here to get 2014.0: Adobe CC 2014 Direct Download Links: Creative Cloud 2014 Release | ProDesignTools
And then here for the upgrades: All Adobe CC 2014 Updates: The Direct Download Links for Windows | ProDesignTools
Make sure you read the instructions carefully. The 2014.0 link does not work unless you follow the steps.
Here are my specs and error.
Win8.1, 2x Gforce Titan Black, Intel i7-4960X @ 3.60GHz, 64GB
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: ntdll.dll, version: 6.3.9600.17476, time stamp: 0x54516b13
Exception code: 0xc0000005
Fault offset: 0x0000000000037049
Faulting process id: 0xc54
Faulting application start time: 0x01d028ef6b52f9d8
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: bd89d792-94e2-11e4-828a-54271e6b4262
Faulting package full name:
Faulting package-relative application ID:
Maybe you are looking for
-
Clearing documents rules ?
Hello, Which rules determine whether a clearing document contains lines or not ? On my system, I get different results on 2 companies : - on company A, if clearing two items of which the sum is zero, a clearing document with lines is created - on com
-
I was finally able to get a movie into my movie folder
but no matter what I try I can't burn it, what do I do once the movie is in the folder.
-
Where is XSLT Transformation located
I am trying to do an XSLT Transformation, but I have no idea where to look for this - the only area with a note about where to find this tool is to select Foundation - XSLT Transformation, but I don't have that option - I found File, New, Process, Ca
-
IPhoto:add caption on photo
Can I add captions to the photos.I have given names to the photos by clicking on Info button and entering details at top.Is it possible to see the photo name while viewing in full screen without the rest of the photo info on right?
-
Problems downloading Illustrator
I've already downloaded Photoshop successfully, and Creative Cloud is showing on my desktop and the files seem to be in place. When I try to dowload Illustrator it asks for an application to link to. I chose the .exe for Creative Cloud. It tries t