This content has been marked as final. Show 5 replies
Please call Adobe's support via phone, local numbers are available at: http://adobe.coom/support/
Trying to solve this kind of issues via a web forum is almost impossible, but first make sure you've tried all the tips at:
- Jonas Hummelstrand
Well, then, does it work with multiprocessing off? Some CoDecs are simply not safe to use with MP. Short of that, simply render an image sequence, assemble it in another program like QT Pro. For further advise, please provide some info about your computer and the version of Quicktime as well as what source footages you are using. The issue might not be related to the compression at all, but when attempting to decode a source file...
The error didn't happen when I was rendering to a quicktime movie export with animation codec. It seems to only happen now when I have rendering more frames at once. I don't want to render output to frames if I can help it as that's an entirely additional step if I have to go that route. No one has ever heard of a problem with bee.dll?
When rendering using the animation codec should I be trying to render multiple frames at once? I've got a Dell t3400 tower with a quad core processor and 3gb of ram (with switch to use in Xp 32bit)
Or is better to use all the processors to render a single frame together? Does it work like that?
I'm using cs3 AE 8.0.2 and QuickTime Pro - 7.4.5
Any help or guidance is appreciated!
Rule 1: Always use the render Queue and only resort to "Export..." if you need to few options that aren't available in the RQ.
AE always uses all processors to render a single frame. Only if you enable "Render multiple frames simultaneously" will AE launch several background processes to work on several frames at the same time.
- Jonas Hummelstrand
>Or is better to use all the processors to render a single frame
>together? Does it work like that?
Well, as Jonas said, AE will always use all processors even without MP enabled. That's what's called multithreading. However, multithreading is limited to 2 simultanous threads in many cases, so it's no longer yielding maximum performance on today's multicore machines. Hence the multiple frame rendering.