Skip to main content
Participating Frequently
September 12, 2013
Question

ProRes codec options unavailable in AE render

  • September 12, 2013
  • 4 replies
  • 31483 views

I have FCP X, Motion and Compressor

Running Mountain Lion

New Mac Pro 12 core Xeon processors

And I'm using

Adobe CC

It works on my MacBook Pro laptop but not on my new desktop.

I repaired permissions, relaunched.

Only thing I can think of is that I migrated to a solid state drive using Carbon Copy Cloner and zeroed out the factory install of the OS.

Any help or ideas would be a great help and appreciated.

Thanks gang.

Scott

    This topic has been closed for replies.

    4 replies

    Inspiring
    June 16, 2015

    ‌has anybody on cc tried this:

    1.  move the quicktime components to a desktop folder, removing them from they system folder

    2.  hack-install the older quicktime components for prores

    3.  restart

    4.  open ae and render pro res,  check if settings button works

    5.  if settings button works, render a few seconds of footage and adjust settings as needed save close ae

    6.  move original qt components back to system folder, repeat the same render and atempt to adjust settings

    the theory here is that you can force ae to pick up the older api that will allow the settings to be changed.  if you have a pro app from apple, you already have license to the prores, and putting the older into your system is simply including an older version of the components for compatibility across your workflow.

    as for gamma shift...  some retina models produce this shift more heavily than others.  calibrate your monitors, and remember that the gamma of prores is tailored for an older color space and lower dpi.  remember that gamma shifts can occur if pro res detects that a transcode is coming from a format that it believes is using an older colorspace, even if its a newer version of the container.

    i dont have cc so i cannot test on my own.  but using only the freely available portion of the api seems like it limits access to key features of the api, even when the full one is licensed.  if there were a way to copy settings files from ame to ae this would mean less issue, but it would be better to simply use codecs registered with ame when they are not standard inclusion, and have people download settings for ame when they have the codec installed.  this worked prfect for CS6.  i didnt have to mess with it to get it to just work after importing the set.  it seems adobe and apple are experimenting way too much right now for me to try an upgrade.  im not paying evey month for software that acts like its still in beta.

    Inspiring
    May 8, 2014

    I have the same problem. It leads to a gamma shift in the exported video.

    Community Expert
    September 12, 2013

    Do you have Apple Pro video apps installed like Motion? Without the Apple pro apps no ProRez.

    Tim Kurkoski
    Adobe Employee
    Adobe Employee
    September 12, 2013

    Rick Gerard wrote:

    Do you have Apple Pro video apps installed like Motion? Without the Apple pro apps no ProRez.

    That's not true for After Effects CC (and Premiere Pro CC and AME CC) on Mac OS 10.8. On 10.8, the AE CC can render to ProRes codecs without needing to install Apple pro apps, because on 10.8 we can us the OS-native encoders.

    Apple pro apps are necessary for access to ProRes on 10.7 or when using CS6 on any version of Mac OS because they install the required QuickTime component files.

    Like Dave, I am suspicious that the cloned OS is causing the problem. Either that or you're using CS6 and haven't installed or properly licensed FCP on that machine.

    Participating Frequently
    September 12, 2013

    Thanks Tim,

    Actually, I think the cloning may be an issue too. I'm going to try a clean reinstall of everything. However, NOT using CS6. It's definitely CC, as I downloaded the programs from the cloud onto the system. Not an install DVD in site. And a double check of the install (after reading your suggestion, as I have done more boneheaded things in the past than installing the wrong version of software from the cloud) confirms that it is indeed CC.

    I think it may be the issue with the OS not playing nice with QT and After Effects. There are some threads about how there's trouble with the way Mountain Lion and After Effects interact. So I'm not sure.

    Can't wait to get this going though. I've been rendering off of the laptop and wow, is it getting tiresome!

    Thanks for taking the time to comment on this. All of you guys are great for helping out a stranger.

    I'll try the clean reinstall of the works and let you all know how it goes!

    Cheers,

    Scott B

    Dave_LaRonde
    Inspiring
    September 12, 2013

    Sounds like you need a clean install: OS and application software.

    There too many differences between a laptop and a desktop machine to rely on cloning a drive.

    Participating Frequently
    September 12, 2013

    Thanks for the response. I really appreciate it!

    Thing is, I don't think I was clear about the cloning. I didn't clone the laptop system. I cloned the factory install with no CC or FCP/Motion/Compressor, just Mountain Lion, from the 1TB standard drive to the new solid state hard drive. Then, I deleted the info on the factory install drive.

    So it's not that the system came from the laptop, it's just that I have the same set up on the laptop and it works great. However, the laptop OS is Lion, not Mountain Lion, as I read a lot of comments online that it was twitchy.

    Again, thank you for taking the time to consider this. I love this community and am always impressed by how eager people are to help strangers solve problems like this.

    Cheers!

    Scott Brown