Tim Kurkoski
Forum Replies Created
-
The most common cause of startup issues for AE7 is OpenGL. Try removing the OpenGL plug-in from the Plug-ins/Extensions folder.
If that works, update the drivers for your video card, then put the plug-in back. If it fails again after you put the plug-in back, you can either:
A) Get a new video card that supports OpenGL propertly.
B) Just live without the OpenGL plug-in. You won’t be missing anything other than OpenGL acceleration. -
To add to what Dave said…
You can get a list of what cameras the Adobe Camera Raw plug-in supports, and therefore are supported by After Effects CS3, from here:
https://www.adobe.com/products/photoshop/cameraraw.htmlAlso, when Adobe releases a new Camera Raw plug-in for Photoshop, you can download it and After Effects CS3 will benefit from the update. (This is different than AE7, which was stuck with a static version of the Camera Raw plug-in.)
-
Tim Kurkoski
October 3, 2007 at 4:31 pm in reply to: Is newest AE better performer than AE6.5 on Intel Mac?> apparently the render engine is busted for Macs.
Bogiesan, can you clarify? There’s a known problem with running the RE under Rosetta, but there’s a way fix the issue:
https://www.adobe.com/go/kb402510Or is there some other problem that you’re referring to?
-
-
If you’re using the trial version, Keylight won’t be there. Also, make sure that you selected to install all components, as the third-party content can be deselected.
But otherwise, as John said, Keylight and the other third-party stuff installs at the same time as AE.
-
Tim Kurkoski
July 23, 2007 at 5:23 pm in reply to: What’s Wrong? – AE CS3 displaying Effects incorrectlyThe Standard 3D compositing mode isn’t in AE CS3, which is why you’re getting the error. The Advanced 3D mode has been the default for the past couple of versions anyway.
Did the values on your effect change, or is it only the appearance? Depending on how you have the comp configured, there could be a visual difference between Standard 3D and Advanced 3D. My only advice for this type of pain is the same that comes up every time a new version appears- finish any work you started in the old version in that version. Use the new version for new work.
Regarding OpenGL, it isn’t a factor in this problem. And once Apple has fixed their side of the problems, Adobe should be producing an update to enable OpenGL on the Mac.
-
Check out the forums for AE CS3 on labs.adobe.com. Adolfo Rozenfeld, one of our fellow bovines in the Cow herd, is the moderator there and has been doing a great job of pointing out all the changes and improvements in CS3, both big and small.
-
How are you exporting to SWF?
It appears you have installed this:
https://www.wildform.com/and are selecting it. AE does not come with any Wildform software, some at some point you (or someone else) installed it.
AE’s built-in SWF export can be accessed by choosing File > Export > Macromedia Flash (SWF). If you’re clicking on something else, or going through the render queue, that’s probably how you’re getting to the Wildform exporter.
-
Try trashing the preferences file.
Mac:
Users//Library/Preferences/Adobe/After Effects/7.0/Adobe After Effects 7.0 Prefs Win:
C:\Documents and Settings\\Application Data\Adobe\After Effects\7.0\Adobe After Effects 7.0 Prefs.txt -
You need a codec that supports 16-bpc color. QuickTime doesn’t come with any 16-bpc codecs. (And I’m not aware that any 32-bpc codecs exists. All current 32-bpc workflows I’m familiar with use image sequences.)
Digital Anarchy offers the None16 codec for free. It’s an uncompressed, 16-bpc codec. Keep in mind that will chew up a LOT of disk space.
https://www.digitalanarchy.com/micro/micro_none16.htmlDA also makes a lossless compression version of the codec, Microcosm, that you can pay for.
https://www.digitalanarchy.com/micro/micro_main.html(FYI, when DA refers to None16 and Microcosm as 64-bit codecs, remember that they’re talking about 64 bits total: 16 bits per channel, Red, Green, Blue, and Alpha.)