“Dominoes” CameraTracker and Cinema 4d Case Study – Day 1

“Dominoes” CameraTracker and Cinema 4d Case Study – Day 1

on Jan 10th 2012 with 10 comments
Tutorial Details
  • Requirements: After Effects, Cinema 4d, and CameraTracker
  • Difficulty: Intermediate
  • Run Time: Part 1 - 35:36 min, Part 2 - 48:51
Download Source Files

Final Product What You'll Be Creating

In this tutorial we’re going to go over the principle functionality of CameraTracker from The Foundry, learning basic workflow, optimizing results, aligning the ground plane and exporting this data from After Effects to Cinema 4d.

After exporting the data to Cinema 4d we will add some dynamic simulations that will interact with the background footage. I’ll show you how to light the scene with a self-made HDRI and render it out to composite back in After Effects.

Tutorial

Download Tutorial .m4v

File size: 73.8 MB

Tags: 3d to AE
 
Enjoyed this Post?

Subscribe to our RSS Feed, Follow us on Twitter or simply recommend us to friends and colleagues!

By

Rollover to read this author's bio or click through to see a full list of posts by this author.

I'm a 25 yr old Germany-based VFX Generalist, working in the industry since 2007 after school. I'm working as Senior Compositor and Matchmoving Supervisor at Haus&Gross Communications GmbH at the moment working on international TV commercials, music videos, TV Shows and movies using AE, Nuke, Cinema4d and Syntheyes, as well as AE Camtracker on a daily basis.  

Plus Premium
 
 
  • http://olivetty.daportfolio.com Oliver Banasiak

    Ty very much for this case study! :) Good job at explaining the different settings and why you do what you do. The only thing that is a little bit negative is that you really don’t know what to say before you say it, so the tutorial is draged out at least 5 minutes due to all the pauses you do when explaining. Write down keywords that line out the tutorial steps in advance and put it right beside your computer when recording a tutorial. This way you know what to say and the tutorial is much more smoother. This tutorial is 35 minutes, and could be surely 15 minutes tops, if you just would’ve know what to say in the first place. I realize also that english is not your first language, it isn’t my either, but that is no excuse :P

    But all that aside, thank you and I am looking forward to part 2! :)

  • NORMAN

    hello, i’m sorry, but dont understand this signage on time 14:09, i use OS Windows, someone can help me?

    • http://olivetty.daportfolio.com Oliver Banasiak

      That’s the symbol for “Enter” on a Mac :)

  • Niblet

    This tutorial is very relevant to my interests. Thanks man, i’ll have a go at it when i get time :)

  • Steve MacMillan

    Great tutorial, thanks.

    I wish the audio levels were a little hotter, though.

  • Dima

    Good tutorial.
    But it’s a bit too slow. Sounds like you think about every word you say.
    A bit difficult to percept info. Other than that good explenation.
    Thank you.

  • charlie

    Good tutorial, but your presentation just bored me out. Couldn’t watch it to the end. Please work on your verbal skills.

  • http://danfoznot.com Dan Foz

    Good info the flow of the tutorial was a little slow…

  • Marc

    Just wondering at 13mins in when the Solve per frame threshold is lowered why not do that before the initial tracking? Is there a reason to do it after the track?
    Thanks

  • Marc

    Give the guy a break with the negativity it’s obvious his english isn’t as fluent as it could be. This site is all about learning new stuff and gaining knowledge not having a go. Nobody is making you watch these tutorials.