You should always tell what kind of config you are using. OS< GPU<RAM<etc....Cs6? cs5.5? Creative 'lease me' Cloud?
MacBook Pro 17 early 2011, 16gb, Samsung 830 256gb ssd, i7 2.3ghz.
After Effects CC
Footage is only about 630 px wide....15 seconds. So it's small.
I dont think I am under-horsepowered. But I have searched and no one quotes this error. I am not sure if there are steps I need to take before I stabilize or if there are preferences that need to be set better.
Where did the movie come from? The codec may not be compatible. The first thing I would do is transcode the footage to a PhotoJpeg Quicktime. See if that helps.
It's an mp4 from a GoPro camera.
That's an odd size. I track gopro footage all the time. Did some last night, but it's usually HD or bigger.
Is the frame rate standard? That may be causing some issues. Is the footage cropped? That may also be causing some issues.
If you transcode the footage to a photojpeg QT and it still won't stabilize then maybe the shot is one that won't stabilize. Warp stabilizer will not work on all shots.
That's interesting. It wont work at any native GoPro sizes. I scaled it as a test. I dont know why someone hasn't posted that error before.
I dont know why someone hasn't posted that error before.
You are assuming/ implying that this is a regular occurance, which it obviously is not. Still, we're not any step closer to even guessing what's going on, since we don't know the exact footage specs. You could simply be making a mess of framerates or whatever...
It sounds as if you (both) are pointing me in the same direction: unacceptable footage specs. GoPro shoots everything at 60 fps and up. This was 1280x720 and I manually scaled it to 600+ px arbitrarily to see if that would "kick" it.
Now I am beginning to think it's the 60 fps.
I will downsample to 29.97 and bring it back in, then report back. With GoPro being so popular, I just assumed it would be a drag & drop.
Well, new test & same result.
Footage is downsampled to 29.97 and left at 1280x720. Comp matches footage. Re-imported new footage and did not scale this time.
Comp is 32 bit, as is Warp. Ran RAM Preview on it first in case this was a prerequisite.
Are there any multi processor preferences I should be aware of? I have Render Frames Simultaneously check off. I also noted in Preferences that I dont have GPU Rendering capability because it's CUDA only and I have the ATI 6750 on this MBP laptop. Still, I didn't think my video card was under capacity. Who knows?
Update: I rendered the file out as QT jpeg and reimported to a new comp.
Tried to analyze again and this time it ran 3 frames before it said "unable to aquire rendered frame." Almost sounds like a caching error.
Hi there! Got the same problem on mine mac. Did you found the solution to this problem?
I'm afraid not. No other forum has been able to shed light on this, so it will remain a mystery.
This has been a frustrating problem for me too. I was amazed how little information the is on this error on the internet. So I was beginning to think it was me. So, just for curiosity's sake I created another user on my Mac and by gosh the problem went away. No video renderer error. So now I need to find what extension is causing this error.
I had the same problem and by creating a new test user the problem disapears, too. So I disabled all startup items from my real user and the problem disapears also. After checking which program causes the problem I came up with PopClip which breaks AE. So, quitting PopClick fixed the bug on my Mac.
OSX 10.9.2, Adobe CC
Thanks for reporting back what worked for you.
Yup I am using that app too. The developer is pretty good at fixing bugs, so
we should both mention it to him.