4gb is very little RAM for working with After Effects, especially something as demanding as the Warp Stabilizer effect, which uses a lot of RAM and CPU power.
Try working with a much shorter clip and see how that works.
That's what I thought. Although the problem occures right after I imported the .mov clip ( which is 4 seconds long btw) and create a new comp with it. AE crashes before I can do anything else.
I worked on 30+ layers animations with a 5 year old Intel Mac first Gen and 2G of RAM without having this kind of problem with CS4 ( t'was slow but it worked ^^). Maybe 5.5 is just more demanding.
I'll give it a shot with the RAM I should receive shortly. Can't wait to test warp goodness..
Thanks for the quick answer.
Here are some suggestions for troubleshooting QuickTime issues:
Try importing a QuickTime movie that uses a different codec, too.
I replaced QT X with 7. But I'm still having the problem with XDCAM format.
I tried with a Pro Res 4444 clip and it worked flawlessly.
Please submit a bug report and include a clip that is causing the problem so that we can see where the problem is.
(You won't be able to include an attachment using the web form, but we'll respond to the report with an email address that you can use to send attachments.)
Bug Report sent.
Thanks Todd I'm impressed with the speed all this is going.
> Thanks Todd I'm impressed with the speed all this is going.
Don't be too impressed until we've gotten to the bottom of the issue. ;-)
It may take a few days.
We're making progress on this bug, but we could really use another sample clip that's longer---at least 30 seconds. If you are able to send us such a clip, let me know, and I'll send you an email address. Or, even better, you could upload it to a file-sharing service and give us a link to download it.
Is it possible that the odd characters in the filepath have been causing errors? I try to never use spaces or especially colons, as it appears you are using. Can you try copying the file to your desktop temporarily, and working with that version to see if the problem persists?