Difference between revisions of "Motion Capture Demo"

esse quam videri
Jump to: navigation, search
Line 12: Line 12:
  
 
++Motion Capture Production (EVarts 5.04)
 
++Motion Capture Production (EVarts 5.04)
* Load a previous marker set (project file)
+
* Load a previous marker set (project (.prj) file)
* Calibration L-seed - switcxh to calibration tab
+
** Marker set will be visible in post-process tab
 +
** The number of markers will directly reflect the number of tracks in your track(.trc) file
 +
** this will translate to points on the skeleton rig
 +
** depending what your final destination for your Motion capture is, this may be dictate from the model being animated (if it is already created or not)
 +
** in either case, the data can be massaged later in the pipeline (better to have more)
 +
* Calibration L-seed - switch to calibration tab
 
**Turn on the cameras, put the L-device on the floor
 
**Turn on the cameras, put the L-device on the floor
 
* Mask out
 
* Mask out

Revision as of 16:04, 14 August 2008

++Overview

  • Motion Analysis hardware
  • optical motion capture
  • 10 Hawk cameras
  • EVarts 5.04 software

++Uses of Character Animation, pipeline overview

  • file formats
  • Autodesk MotionBuilder 7.5
  • marker sets
  • TGEA

++Motion Capture Production (EVarts 5.04)

  • Load a previous marker set (project (.prj) file)
    • Marker set will be visible in post-process tab
    • The number of markers will directly reflect the number of tracks in your track(.trc) file
    • this will translate to points on the skeleton rig
    • depending what your final destination for your Motion capture is, this may be dictate from the model being animated (if it is already created or not)
    • in either case, the data can be massaged later in the pipeline (better to have more)
  • Calibration L-seed - switch to calibration tab
    • Turn on the cameras, put the L-device on the floor
  • Mask out
  • wand, floor, ROM
  • Data output, capture
  • EVarts 5.04 Post production

++Autodesk MotionBuilder 7.5

  • inputting TRC data
  • cleaning up TRC data
  • animation
  • Output formats