AE CC 2014 crashed while rendering scatter fx

The program keeps crashing and after rebooting and trying to render it crashed trying to render Scatter. What going on? These simple files and all I get is crash. The program also failed while reading some Quicklime files. This is very unstable and I can render projects that worked well on my older version. I have 32gb of memory a GTX 780m cards and the performance is totally bad. The to use OpenGL when available is not showing up in Carton.

Ray E wrote:
The to use OpenGL when available is not showing up in Carton.
If you're asking about GPU acceleration of the Cartoon effect, according to the page on what’s new and changed in After Effects CC (12.0), "Rewrote Cartoon effect so that it doesn’t prevent the use of Render Multiple Frames Simultaneously multiprocessing. The Cartoon effect also no longer uses GPU acceleration." The Cartoon effect hasn't used GPU acceleration since version 12 (CC 2014 is version 13).
If you're talking about something else, please explain further.
Ray E wrote:
This is very unstable and I can render projects that worked well on my older version.
What "older version" were you using?
Ray E wrote:
The program also failed while reading some Quicklime files.
What was different about these QuickTime files compared to ones that did work correctly?
As Todd and Mylenium have said, we need a lot more info.

Similar Messages

Premiere Pro and Media Encoder crash while rendering H.264

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
It's only while rendering H.264 - other formats seem to work fine.
And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
I've tried disabling CUDA and my overclock to no avail. Please help!

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

Premiere Pro CC Crashes While Rendering With Mercury OpenCL

Hi guys!
Every time I try to render a ~2 min video in H.264 using the OpenCL renderer which is fully supported on my 7970 (2x Crossfire) the program crashes while rendering. (Usually around 28%)
If I switch to Mercury Software renderer, it renders perfectly.
I am currently using AMD 13.6beta2 drivers, and PPCC is fully updated, any suggestions?
Additionally, for the half minute that it tries to render with OpenCL before crashing, by checking the GPU utilization % in AMD catalyst overdrive, it seems to not be utilizing the gpu at all... And then promtly crashes of course...
I hope I can fix this problem soon... Really dissapointed with this adobe product.
Thanks a lot!

Rendering without any effects ----------> Still Crashes
Disabling Crossfire ----------------------- > Still Crashes
Reinstalling Premiere ---------------------> Still Crashes
Physically Removing the 2nd GPU -----> Works
So, is there any way I can get this to work while having both GPUs physically installed in the computer?
It would be quite a hastle to remove the 2nd one each time I need to use PP!
One odd thing also is that from watching the gpu utilization while rendering H.264 1080p, the GPU is only being used to about 30%, and very intermittently.... I would imagine things would accelerate quite a lot if it actually utilized the whole GPU!
Thank you very much guys!

After Effects crashes while rendering

Hi all,
We have been experiencing regular crashes while rendering on 9 different Mac systems.
We would start the render and then, all of a sudden, AE would crash.
Trying to restart, AE hangs at MediaCore initializing.
We actually need to do a hard shutdown to get the machine to reboot.
So my question is:
Could AE not release the media cache upon crashing thus blocking us to restart the app without having to reboot the machine?
We are running AE in multiproc mode with 4 GB memory allocation, which actually uses 3 procs.
I have tried bringing the memory allocation down to 3 GB on some of the systems, but it doesn't seems to make much difference.
Finally, we do not crash every time we render. It is very random.
Any ideas?
Thanks,
Rene

Hey Todd,
Sorry for the late reply, answers below:
What exact version of After Effects? 12.2.0.52 but we also use CS 5.5 (mainly for the feature where you can send your camera information to C4D, something that is not in the CC version... pitty)
Have you installed the recent updates? This is the latest update...
What operating system? Mac OSX 10.8.5
Tell us about your computer hardware. 2 x 6 cores CPUS, 24 Gb RAM, ATI Radeon HD 5870 GFX, 5 internal drives (4 of them are part of internal hardware raid with internal raid controller)
What versions of drivers for your graphics hardware do you have installed? No CUDA since it is ATI, 01.00.436
Do you have any third-party I/O hardware : AJA Kona 3G with either driver 1.47 or 1.49
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. It is a combination of a bunch of them: Animation codec into .mov wrapper, tga sequences, png files, we render to uncompressed .mov files for air.
If you are getting error message(s), what is the full text of the error message(s)? No, just the beach ball of death...
What were you doing when the problem occurred? They mainly occur when rendering sequences.
Has this ever worked before? It is very intermittent and does not happen every day. Plus, since we are in crunch time, AE is being used 24/7, so that may not help either.
What other software are you running? C4D, Photoshop, Illustrator, both in the CC and CS6 or CS5.5
Do you have any third-party effects or codecs installed? We have sapphire and Knoll lens flare, but crashes happens if we use them or not.
Are you using OpenGL features in After Effects? Not to my knowledge.
Does the problem only happen with your final output, RAM preview, or both? Render
Are you using Render Multiple Frames Simultaneously multiprocessing? Yes we do, most of the machines have it set with 4Gb memory allocation, but others have it set to 3 Gb.
Are you using the ray-traced 3D renderer? No, we are not.
If the problem is with output, give your exact output settings (both render setting and output module settings). Unfortunately, I do not have this as our artists are working and I cannot really stop them as we have things to get out to air for early morning. I will get this info next time we have the issue.
What is the exact sequence of steps that you are taking? Just sending the render out to the queue and starting and it will either crash to desktop or stay there doing nothing.
My biggest concern is why can't we just restart the app. It will always lock up while initializing MediaCore. We have our mediacaches set for 42 Gb on our main bootup drive, which is big enough to handle it. And after the crash, when we try to reboot, the machine will get to the grey Mac screen and just sit there. Have to hard shutdown the machine to have it come back up...
Let me know if you need more info.
Thanks,
Rene

CS6 crash while rendering

Hi,
recently CS 6 crashes while rendering, this happens at the beginning (ca. 800 frames), i change from GPU to CPU, deletet the cache files, try a different sequence
with other videos, all the same
in task manager i can't kill the premiere prozess
after crashing only the power/reset button helps
the strange is, at the same time my complete network crashes to ??
Windows 7 pro
16GB RAM
Genforce GTX570 Driver 340.52
Intel i7-2600K
With Media Encore there are no problems.
can someone help me ?

The problem with PP CS6 crashing during render has increased from once in a while to where it cannot complete any renders.
---->>> Encoding to H.264 MP4. Seems to do fine on AVI renders. H.264 MP4 is the key to the problem. <<<---
The error that it is reporting says that the "output directory could not be found", but the problem is the same when rendering to a different (not RAID) drive. Does not crash with AVI render. Replaced H.264 Codec -->> No change. Crashed at 90% of a 50 second file render to lowest level MP4 file.
It is not the motherboard - Replaced Gigabyte with ASUS Sabertooth 990FX
It is not the CPU - Replaced AMD 6 core with AMD 8 core FX
It is not heat. Cabinet is cool, all fans are running, no dust, no blockage.
It is not power supply - Replaced 750 W power supply with 850 W power supply.
It is not memory - Increased memory from 16GB to 32 GB, Computer repair shop rotated and tested memory.
It is not virus (no email on this machine, current virus protection and security software).
It is not drive space - Increased RAID from 2TB to 8 TB - Problem actually got worse - (crashes sooner)
It is not the video card - drivers verified correct by Nvidia - (Quadro 4000) - tested by installing a different video card - No change.
It is not software install - Uninstalled total CS6 package and reinstalled.
It is not a specific render file - It will not complete any renders now.
It is not a recent software install - The only software that has been updated is Adobe but that was ruled out by the total uninstall/reinstall. Backup install on a laptop is able to complete renders on the files that crash on the "big" machine. Nothing new has been installed. Virus and SpyBot show "clear".
It is not the CUDA or Mercury setting - Tested with CUDA on and off.
It's not the Playback settings - Tested for GPU Acceleration and Mercury Playback Engine Software only.
It is not the C: drive - Replaced with SSD.
Ran while watching Performance Monitor - No hint of problem before crash point. (video available).
So, what are we missing?
Windows 7 Pro
64 Bit
32 GB Ram
8 TB RAID
ASUS Sabertooth 990FX
AMD FX8350 (8 core)
Performance Score: 7.1
Power Supply 850 W.

Premiere Pro CC 2014 Crashing with rendering, freezing system, and more

Hello,
I'm having some serious issues with Premiere pro on my late 2013 iMac.
OSX 10.9.5
3.2GHz Intel Core i5
16GB 1600 MHz DDR3
NVIDIA FeForce GT 755M 1024MB
I'm working in 1920x1080 23.976fps. Media files are from sony FS700 .MTS and Cannon 5DmkIII .mov
Multiple times per day, PP crashes on me. It all started when I was getting really choppy playback which would be accompanied by this error message:
A Low Level Exception has occurred in ImporterMPEG (Importer)
This would soon after lead to the program freezing and me having to force quit the program. After contacting Adobe the first time about this persistent issue, the tech explained to me that it was a "Memory Leak" issue and that there was nothing that could be done. After the support team member ended our chat online before helping me solve my issue, I called support. I provided my case number and this person picked up where the helplessly left me and did the typical Adobe one fix all: He went into the hidden library and cleared all of my preferences, removed any third party plugins, and cleared the files in the root applications Adobe folder, renamed a folder "Adobe.Old" etc.
As I explained to the support team member on the phone, this is not a solution but rather a bandaid until it happens again.
Low and behold it has happened again. This time the support team member had me create a new System Administrator account on my computer thinking that there was a permissions problem with my other account which was conflicting with PPCC2014. While this was a major pain to switch between the new account and any other program that I had set up for day to day work, it allowed me to continue editing and at least (at a less efficient rate) get things done.
Now, while using my new System Administrator account, I am getting terrible crashes that not only stall the program, but force me to hard re-boot my computer. These crashes are accompanied by a terrifying looking screen that I was only able to capture once.
They've only become more intimidating as now I cant even see the program when this happens, but this is the only screen capture that did not turn out completely black.
I'm looking to see if anyone has had any extreme issues like this and if so how they were able to fix it. I've now spent 6+ hours with support and after the last one was told I would receive a personal email follow up by the end of the day (never happened) to take further actions based on the performance after the new account creation.
I need help. Now.
-John

Hi John,
First of all, try this: Re: A low level exception occured in: Importer MPEG (Importer)
Next, make sure that if you updated OS X to 10.9.x, or later, you must check the following each time you update: Premiere Pro CC, CC 2014, or 2014.1 freezing on startup or crashing while working (Mac OS X 10.9, and later)
Other things to try:
Sign out from Creative Cloud, restart Premiere Pro, then sign in
Update any GPU drivers
Trash preferences
Delete media cache
Remove plug-ins
Repair permissions
Disconnect any third party hardware
Remove QT components from Mac HD > Library > QuickTime
If you have a CUDA GPU, ensure that the Mercury Playback Engine is set to CUDA, not OpenCL
Disable App Nap
Reboot
Report back if anything here worked for you.
Thanks,
Kevin

FinalCut Studio crashing while rendering

On 2 different machines, a 2007 MacPro (6gb ram) and a 2008 Macbookpro (2gb ram) I am converting Go2meeting wmv files into h264 files for posting to brightcove.
While rendering the movies, at completely random intervals, I'll get an error message as below:
"Codec not found. You may be using a compression type without the corresponding hardware card."
This will happen while it is in the middle of rendering one of the WMV files. (no cmyk files in the wmv file)
On the Macpro desktop, I'll be able to save before Fincalcut completely crashes, on the Macbook Pro, the program will crash as soon as I hit the 'ok' button.
It takes a huge amount of time to render these sequences, and is irritating when I lose an entire night to one of these crashes. Any idea what may be causing them?
Addition info: running 10.6.4 on the desktop, 10.5.8 on the laptop, Flip4Mac, perian on both.
Message was edited by: rick knecht

The Liberator wrote:
I says every time it was due to the Perian plug-in. ..
.. I spoke with the IT guy, and he thought that is was just a simple thing of not having the video in NTSC H.246 and instead having it in PAL in DV.
you get a specific error-message, naming perian as source of error? never heard of that!
what do you try to accomplish, I assume Exporting with QT-conversion.. what settings?
perian adds a few codecs to the QT-engine, which are 'Mac-exotic', mostly divx ..
when you install other, addiional divx-plugins, e.g. for Flip-camcorders or the 'free' XviD, you get a conflict => errors.
your 'ITguy' should quit his job ... - in video editing, you don't switch standards & codecs 'like the wind'.
example: a 30fps/h264 is by many factors smaller than a 25fps/dv .. aside, you have (dramatic) losses of pic quality, by scaling the framerate ..
tell your 'ITguy', in which standard you're working, and for sure you want to export with corresponding settings.. it is HIS job, to make things done flawless .. he should 'clean' the QT-plugins to the few needed ones, not all he could get from the internet.
... The usual Admin-from-****-behavior to tell the user, s/he should change settings, not him..
your Mac/FCE DOES export in many standards.. just to mention that..
what are your sequence' settings, by the way... ?

PP CC 2014 crashes while locating media

Hello geniuses of the world-
I'm having a problem with crashes while locating media. If I let PP search for the media, it eventually crashes with the standard dialog box. If I hit Cancel and try to locate it manually, a weird white box appears (clearly it's a dialog, but it never renders fully to the screen UI, so I can't tell what it says) then I have to cmd+opt+esc to force quit the unresponsive PP.
This only occurs when trying to locate media on a Promise Pegasus2 RAID array connected via Thunderbolt 2. If I locate media on a Glyph backup, it loads the "manual" locate browser or automatically locates the media flawlessly.
To me it seems apparent that it's a problem with the Pegasus but I just figured I'd double check and see if anyone else has had this problem, maybe it's a stupid little thing I'm not remembering to do.
Specs: Mac Pro 2013 (garbage can), Pegasus2 R8 Thunderbolt 2 RAID in RAID 10 (not my first choice but it's not my hardware) formatted Mac OS Extended (Journaled)/have also tried ExFat to no avail.
Cheers,
Henry

Hi,
What is the format of the file that you are trying to locate.
Try to move some media on the internal drive and try to locate it from there.
If you feel that the drive is malfunctioning then open the project and use project manager to send the media and project file to the internal drive.
Check if it helps or not.
Thank You
Arjun

Media Encoder CC Problems - No sound and often crashes while rendering to Youtube 1080p 29.97 fps

I'm baffled by all of this.
I'm trying to render a clip similar to this:
http://www.youtube.com/watch?v=fprMxgfdpRo
except there are 8 equalizers and I have to do it for a 2 hour podcast. I have to do it in 10 minute clips because it will either crash every 2 hours of rendering, or it won't have sound, which seems like a common problem with AME. It is very difficult to get the sound to line up after the fact.
Here are my specs:
Windows 8.1
i7 - 3770K
AMD Radeon HD 7870 GHz edition
16gb Ram
I can't seem to pinpoint a fix for this problem. Anyone have any ideas?

This is user to user forum. Some of us on Adobe side check forums once in a while to help users. Contacting support is the proper direct communication with Adobe. That said..
Try encoding uisng Software rendering instead of GPU. Look for "Renderer" just below queue panel and select "Mercury Playback Engine: software only". We have seens in some cases (on longer clips) where graphic card runs out of memory and causes application to mis behave or crash.
If that doesn't solve, let us know if you can encode that particular video to any other preset (Not Youtube). Just to see if this is common issue with all preset or particular one.

Adobe Premiere Pro CC - Computer Crashes While Rendering/Exporting.

My computer crashes when exporting/rendering. I don't know why it is doing this. Please help!

More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
BSOD shutdowns http://forums.adobe.com/thread/1427408?tstart=0
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

AppleFileServer Crashing while Rendering

My setup for a cluster is two Mac Pro and one Quad G5 as the controller. A Caldigit RAID is attached to the G5 and it is shared with the two other computers so they can get the files when needed for rendering. I create a reference movie in FCP and then use that in Compressor. The cluster is then suppose to render the movie according to the presets that I use in Compressor. This has worked very well with the previous version of Final Cut Studio and it works once in a while with this version but in the last week it stopped working. I have followed advice on every article on the discussion groups to get it back to work but still I am having problems. Today I noticed that the Apple File Server was crashing when I checked the console. Have deleted the preferences for it but the next time it crashes again. Compressor works great on the G5 by itself.

The Liberator wrote:
I says every time it was due to the Perian plug-in. ..
.. I spoke with the IT guy, and he thought that is was just a simple thing of not having the video in NTSC H.246 and instead having it in PAL in DV.
you get a specific error-message, naming perian as source of error? never heard of that!
what do you try to accomplish, I assume Exporting with QT-conversion.. what settings?
perian adds a few codecs to the QT-engine, which are 'Mac-exotic', mostly divx ..
when you install other, addiional divx-plugins, e.g. for Flip-camcorders or the 'free' XviD, you get a conflict => errors.
your 'ITguy' should quit his job ... - in video editing, you don't switch standards & codecs 'like the wind'.
example: a 30fps/h264 is by many factors smaller than a 25fps/dv .. aside, you have (dramatic) losses of pic quality, by scaling the framerate ..
tell your 'ITguy', in which standard you're working, and for sure you want to export with corresponding settings.. it is HIS job, to make things done flawless .. he should 'clean' the QT-plugins to the few needed ones, not all he could get from the internet.
... The usual Admin-from-****-behavior to tell the user, s/he should change settings, not him..
your Mac/FCE DOES export in many standards.. just to mention that..
what are your sequence' settings, by the way... ?

After Effects CC 12.2 Crashes While Rendering on New Mac Pro

I have been working on a new project in AE 12.2 on my New Mac Pro. The project file runs a little slugish while I'm working. I am using Trapcode Lux, Optical Flares and a lot of expressions. When I go to render the file 1/4 of the way in my whole computer freezes and I need to force it to shutdown and restart. No error report is created I don't think.

Optical Flares is GPU dependent, which can play havoc when rendering using multiprocessing.
Try rendering with multiprocessing turned off.
If that doesn't work, try temporarily removing Optical Flares from the AE Plugins folder and restarting AE, then render. This will force a render with no Optical Flares included.

Constant crashing while rendering in Premiere Pro CC

Am trying to export a video from this sequence, Premiere Pro CC (latest) crashes every time after about 1-2mins of rendering.
"Error compiling movie.
Unknown error."
Premiere project is located on system SSD (late model Macbook Pro Retina), with source files on external USB3 HDD and cache set to external thunderbolt SSD. Have tried targeting all drives, same issues. Tried flattening all the multicam sequences, same issue.
No special plugins or anything used, just the baked in effects and settings.
Have tried rendering to h.264 and ProRes, both have the same error.
Aiming for a release of this project in the next few days, please help if you can! Thank you so much!!

After trying many many things, I ended finding two problems:
1. an image file CC didn't like, which I removed
2. some other error, unknown, but I rendered the entire sequence in premiere (pressing enter), and then exported to a file after it was fully rendered, and used the "use previews" option to export.
Very strange but so far this has worked.

Crash while rendering

When rendering footage in the latest version of premier pro on MAC OS X 10.9.2 no matter what sequence or timeline I am in, premier keeps crashing every time I try and do anything. I have plenty of memory on a brand new MAC computer but it continues to just crash. any help? anyone having the same issue?

Thanks for your reply. And sorry for the confusion. Here are the details:
1. Premier crashes every time I try and render a clip that I have modified the speed on. If I speed up the footage at all then try and rend it gives me an unknown error and then crashes when I try and render it. My sequence settings are at 24fps using gopro3+ footage I shot at 48fps.
2. I have tried it in different sequences but all at 24fps. I have tried DSLR, arri cinema and a few other settings in the sequence. I have posted a screenshot.
3. A different preview file format? Not sure how to do that.
4. exporting and encoding.
5. I disabled the GPU.
Thank you so much for your help!

Speedgrade 2014 crashing while scrolling timeline

Hi there,
I keep having issues with Speedgrade crashing randomly while scrolling timeline of videos.
I'm using the latest version on an iMac running OSX 10.9.5
It seems to be happening randomly, but so often it almost makes it unusable.

Hi,
I have the same poblem on iMac 27" late 2013 3,4 GHz i5 24 Gt 1600 MHz DDR3 NVIDIA GeForce GTX 775M. Same OSX 10.9.5.
Scrolling timeline causes the crashes randomly. Using direct link or not doesn't seem to affect this.
Br,
Samuli

AE CC 2014 crashed while rendering scatter fx

Similar Messages

Maybe you are looking for