Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums AJA Video Systems Kona Codec and DVCProHD

  • Kona Codec and DVCProHD

    Posted by Matt Silverman on November 12, 2007 at 10:35 pm

    If the AJA codecs are installed in OSX, DVCProHD clips captured via firewire are severely lifted when opened in After Effects. Black levels seem to have setup applied. Very odd… took us a while to figure out why our renders looked different on one machine from another. Is this only happening with the codec? If the hardware is installed do you have the same problem?

    -Matt

    Jordan Maltby replied 16 years, 3 months ago 4 Members · 6 Replies
  • 6 Replies
  • Jeremy Garchow

    November 13, 2007 at 1:09 am

    There’s that ugly gamma shift that happens to DVCPro HD. Are you saying if you remove the codecs that shift disappears or do you have to totally uninstall the hardware?

    What version of everything are you on? FCP, QT, Kona drivers, etc etc.

    Jeremy

  • Warren Eig

    November 13, 2007 at 6:58 am

    We got bit by this too in Color. Everything rendered DVCProHD in After Effects had a huge gamma shift when brought into Color. Looked great in FCP, just gamma shifted in Color. We’re working with Advance Apple Tech on this one.

    Warren

    Warren Eig
    O 310-470-0905
    C 310-560-6245

    email: warren@babyboompictures.com
    website: https://www.babyboompictures.com

    https://www.atomfilms.com/af/content/knitwits
    https://www.atomfilms.com/film/family_xmas.jsp

  • Jeremy Garchow

    November 13, 2007 at 2:38 pm

    This has been a problem since native DVCPro HD editing came to FCP. It’s not an AJA thing as way back in the day when I used Blackmagic products (way back, I’m talking back in Ought-4) this was a problem as well. I don’t know what it is. Perhaps an email to AJA support will set you straight.

  • Matt Silverman

    November 14, 2007 at 7:47 am

    I don’t have the hardware (which is why I didn’t call support). I should have phrased my question better… My initial question was whether this is a software only issue or does this happen when the hardware is installed?

    I did a project earlier this year which was captured with the Kona3 10 bit 4:4:4. I worked on the files with the software codecs, then forgot to remove them. We recently captured varicam shots firewire DVCProHD on another machine. I then comped and color corrected my shots in After Effects. We then set off renders on other machines and noticed substantial color differences. It took us a while to figure out that the Kona codecs were the culprit. We ended up putting the codec on all machines since the client bought off on the color.

    I have verified that this is happening with the latest AJA codecs on Intel with FCPStudio2.

  • Jeremy Garchow

    November 14, 2007 at 3:31 pm

    I think an email to support@aja.com is worth a shot.

    They offer those codecs for people just like you who don’t have hardware. They might be able to set you straight.

    Jeremy

  • Jordan Maltby

    October 29, 2008 at 3:02 am

    It might be an issue of turning Y’CbCr into RGB.

    Color works in RGB color space as does shake.

    i.e. if you give it Y’CrCb material it will render in RGB within the application.

    Final Cut Pro, on the other hand, works in Y’CrCb color space.

    in short: Quicktime movies encoded using an RGB codec (such as Apple Animation) are imported with an automatic gamma adjustment of Aprox. 1.22 into FCP. THE EXACT OPPOSITE happens when you import Y’CbCr codecs into RGB apps, such as Color or Shake.

    long story short:

    If the image is too dark try a 1.22 gamma shift

    If it is too bright try and .824 gamma shift

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy