[Daniel Ramirez]

Hi Martin. We’re still willing to take a stab at it, but you’ll have to file a bug using this form if you’d like us to try and help.

https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

Cheers,
Dan Ramirez
AE QA Engineer

[Daniel Ramirez]

If you file a “bug” using this URL: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

I’ll look into it and might be able to help you get a decent key.
Cheers,
Dan Ramirez
Adobe After Effects
QA Engineer

[Daniel Ramirez]

If you have AJA hardware installed, it’s possible that Photo-JPEG and ProRes footage(8bpc only) will be corrupted(looks pink and blue) in the latest update of AE. I’ve verified this problem with the Kona3 on two Mac machines.

As far as I know, there are no workarounds at this moment. AJA is aware of this issue and I expect a fix in the next public driver update.

Unfortunately; I am unable to get a time estimate on when that driver will be available. If I get new information, or the driver becomes available; I’ll make sure to reply to this thread.
Thanks,
Dan Ramirez
After Effects
QA Engineer

[Daniel Ramirez]

Unfortunately, there is a known bug with alpha in ProRes4444 in CS5. We’re actively working to fix it in a future patch. In the meantime, here’s a workaround that will restore the ability to see the alpha channel in ProRes footage:
—–

If you are experiencing this problem on Mac, here is a temporary workaround(originally posted here: https://forums.adobe.com/thread/628662?decorator=print&displayFullThread=true) until this can be fixed in a future dot release:

1. Close any production premium apps (e.g. Ae, Pr)

2. Locate the MediaCoreQTCodecRulesCS5.xml file in your user Library/Preferences/Application Support/Adobe/Common folder

3. Make a duplicate copy of this file in case you need to roll back later

4. Edit the file and locate the ‘ap4h’, ‘mactel’ entries for both encode AND decode. Change the deepdecodefourcc to’ b64a’ to exactly match the following example lines:

5. Launch AE and try your footage again. Please note that exports to ProRes 444 in AE will also use the QT codec. Keep an eye out for possible differences in metadata content or embedded color profile.

On Windows, the fix is similar but the .xml file is located in your user AppData\Roaming\Adobe\Common\ directory and the entries for codec= ‘ap4h’ and platform=’windows’ need to be modified instead.

Dan Ramirez
After Effects
QA Engineer

[Daniel Ramirez]

Indeed, 2GB just isn’t enough for Dynamic Link.

Dan Ramirez
After Effects
QA Engineer

[Daniel Ramirez]

I just tried the following:

1. Import a 720p60 10bit uncompressed colorbar Quicktime movie into FCP
2. Export this file as DVCPROHD720p60 in FCP
3. Compare this file with the orignal source in FCP

Result: I get a gamma/color shift here. It’s very obvious

1. Import the original 720p60 uncompressed colorbar Quicktime movie into AE CS4
2. Export this same file as DVCPROHD720p60 in AE
3. Import this file into FCP and compare with the original 10bit source file

Result: No gamma or color shift
—

Is anyone else seeing that FCP can’t roundtrip with itself when ingesting an uncompressed source and exporting DVCPROHD? With an uncompressed source, I definitely wouldn’t recommend DVCPROHD as an intermediate editing codec because it looks like FCP has some issues there.

Now, I think the *real* issue here is when your original source is DVCPROHD and you want to roundtrip this with AE without a color shift.

If you’re working with 8bit, you should be able to RoundTrip ProRes just fine. QT-Anim is almost always a good choice, but as many have mentioned, it’s very big. QT-PhotoJPEG may be a better choice for smaller filesizes.

Is everyone experiencing this problem with DVCPROHD footage not rendered or captured in FCP? The fact that FCP can’t roundtrip uncompressed to DVCPROHD with itself is certainly problematic.

Dan Ramirez
After Effects
QA Engineer

[Daniel Ramirez]

Sorry for the short response, but I haven’t read the thread yet and wanted to at least let you guys know I’m going to look into it. Expect a response to this issue next week. (12/14-12/18)

Dan Ramirez
After Effects
QA Engineer

[Daniel Ramirez]

We’ve fixed this problem on our side here for future versions of AE, but unfortunately this won’t help the problem in CS3/CS4. Thanks for reporting this. We appreciate it.

Dan Ramirez
After Effects
QA Engineer

[Daniel Ramirez]

Sorry for the delay. I’m definitely able to reproduce from scratch. It appears to be frame rate related. I haven’t tested anything other than 29.97, but I think it’s isolated to that frame rate only.

Right now, the only workaround is to trim the first frame of your layer. We’re looking into a fix, but I don’t have any more information on that.

Dan Ramirez
After Effects
QA Engineer

[Daniel Ramirez]

I was able to reproduce your problem in CS3 and CS4 9.02. AE is duplicating the first frame and PR, and FCP are not. I’ll update soon with more information, but thanks for bringing up the issue.
Dan Ramirez
AE QA

Dan Ramirez
After Effects
QA Engineer