Just installed AE CS5 and am frustrated to find that Apple ProRes 422 footage (all flavors: HQ, SQ, LT, 4x) does not display properly when the project is in 8bpc mode.
In 8bpc mode:
Same frame, in 16bpc mode:
This behavior does not occur with Uncompressed 10-bit Quicktimes. Only ProRes.
Obviously now that CS5 is 64-bit aware, switching to 16bpc mode isnt as much of a problem as it was in previous versions, but I often like to work in 8bpc mode for speed/performance reasons, so its a bummer that I cant do this with ProRes sources.
Is there a workaround for this (other than working in 16bpc all the time, of course)?
Hi. This is Dan R. from the After Effects team. I'm out of the office for the few weeks, so please excuse me if I don't respond as quickly as I should.
I'm not discounting what you're experiencing, but the behavior isn't typcial. On my machines, ProRes is working properly at all bit depths. Off the top of my head, I suspect a 3rd party Quicktime codec conflict. Regardless of what is causing your problem, we're committed to making sure this works correctly.
Do you have Final Cut Pro installed? Do you have any other 3rd party QT components installed? e.g., AJA, Blackmagic, Sheer, etc.
Please try the following:
Navigate to your Quicktime codec folder. It's found at harddisk/library/Quicktime and harddisk/username/library/Quicktime. Try dragging the entire contents from these two locations into a temporary location. I use a subfolder on my desktop. e.g. username/desktop/QuicktimeTemp
Restart After Effects and try using ProRes footage in all bit depths again. Does your problem go away? If so, it's likely an issue with one of the codecs that you have removed. You now should have enough information to isolate the codec that's causing your problems.
Thanks for your quick response Dan,
I went through all the QT codecs in the /Library/Quicktime folder, and pinned it down to the "AJAVideoOutputCodec.component" codec. Everything works fine once I drag this one out of the folder.
This component is from the latest AJA Kona3 drivers (v7.5.1), released 3/22/10. I did a clean uninstall & reinstall of the 7.5.1 drivers, but the problem persists, as long as this component is in the Quicktime folder. But I cant remove this component, as FCP wont work without it.
My system specs:
Mac OSX 10.6.2
16 GB system RAM
ATI Radeon X1900
AJA Kona3, latest firmware installed
AE CS5 OpenGL settings disabled
Final Cut Studio 3 (all latest updates installed)
I have AE CS4 installed on the same partition as CS5, but do not run them at the same time.
Glad to hear we're closer to a solution. I'll make sure we contact AJA on our end about this issue. Please report the issue with AJA directly. I've got a Kona3 card in my MacPro and it's possible the issue is hardware specific so your system *may* be a valuable piece of information for them.
Thanks for participating in the forums!
This may or may not be related, but After Effects CS5 does not recognize Alpha Channels with ProRes 4444 but does in CS4. The same for Premiere CS5 and CS4. I can create a ProRes 4444 RGB+Alpha out of CS5 but not import the same footage in and have it Interpret the footage correctly. I'm only using the trial version of CS5, but this basic level of functionality couldn't be missing like certain plug-ins (or hasn't been reported by Adobe as missing).
Any thoughts? ProRes is part of my RT FCP/AE workflow....
It's confirmed that this is AJA driver related for me. If you go into your video preview preference settings, and switch to "Computer Monitor Only," then quit and relaunch AE CS5, the same project will display properly.
Dan from the After Effects team again. I'm also able to reproduce this issue now in the latest CS5 dotfix. I've been told the latest AJA update(not yet released) fixes this, but I haven't yet tested this. Once I test this fix, I'll report back here when I've verified that everything is OK.
I am also having this issue with Kona LHi & all quicktimes. Turning off Monitor Preview and then restarting AE seems to temporarly fix the problem... have you heard of an ETA on the AJA Kona driver update???
I do expect the fix to come in the next AJA driver update, but unfortunately; I've been unsuccessfull getting a time estimate. I will post to this thread if I do get an estimate, or if the public driver is released.
Not that I have heard about. I simply work in 16 bit.
Date: Fri, 5 Nov 2010 07:11:07 -0600
Subject: Re: ProRes footage not displaying properly in AE CS5 at 8bpc ProRes footage not displaying properly in AE CS5 at 8bpc
Hi, any news about the fix for this ?
We need to use AJA for monitoring AND ProRes for ingest... so it's been a nightmare since this bug occured.
It's a shame for AJA and Adobe not fixing this...
And working in 16 bits for us isn't a "solution" as we work with HUGE projects and it almost double or triple render times...
Waiting desperately for an AJA update for it's drivers, OR Adobe update OR quicktime, whatever...
I tested the fix in a beta version. Adobe's work is done here. I've asked AJA for a rough estimate on when they will release this driver and they were unable to give me an answer. I'm not sure what to tell you besides contact AJA and pressure them to accelerate this fix.
8 Months, repeat 8 MONTHS!? have passed now and AjA released Drivers for LHi ONLY and that's huge Bollocks.
Anyway, dead end, AjA is not on my list anymore.
I'm about to boycot AjA products from now on. They already drove me nuts several times with poor driver updates and plugins.
They once were standing for quality but now this title is washing away.
I'll go back to Blackmagic Design Products and may take a look what Matrox has to offer.
If AjA is messing around with loyal customers, the customer will be gone.
I'll not recommend their products to anyone anymore! Basta!
AJA didn't just update the LHi only. They also updated the Kona3G and some of the other newer cards. I talked with their tech support last week and he assured me my Kona3 will have a driver update very soon. Check AJA's website again tomorrow. I think he told me Tue, but I don't want to quote someone wthout being 100% sure.
Europe, Middle East and Africa