<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapfrom="Sample video and project (dual depth sensor)" />
  </query-continue>
  <query>
    <pages>
      <page pageid="43" ns="0" title="Recording a video from a depth sensor">
        <revisions>
          <rev xml:space="preserve">Finally, after all these preparations completed, you are ready for performance.

=== Environment ===

For a single or dual depth sensor configuration, you need a minimum of 10 feet by 10 feet space (3 meters by 3 meters). At smaller space, actor simply won’t fit into view of cameras. 

It is convenient to put MS Kinect Sensor on a chair or a table. The picture below will help you to understand possible capture area and required space:
&lt;center&gt;&lt;table border=0&gt;&lt;tr&gt;
&lt;td&gt;[[Image:KSensor-scene-side-view.png|center|385px|Click to enlarge]]&lt;/td&gt;
&lt;td&gt;[[Image:KSensor-scene-top-view.png|center|394px|Click to enlarge]]&lt;/td&gt;
&lt;/tr&gt;&lt;tr&gt;
&lt;td&gt;&lt;center&gt;'''Side view'''&lt;/center&gt;&lt;/td&gt;&lt;td&gt;&lt;center&gt;'''Top view'''&lt;/center&gt;&lt;/td&gt;
&lt;/tr&gt;&lt;/table&gt;&lt;/center&gt;

{{:Actor Clothing Kinect}}

=== Recording Process ===

{{:iPi Recorder Description}}
&lt;!-- Please run '''iPi Recorder''' and choose “MS Kinect Sensor (OpenNI)” in Camera Selector dialog:
[[Image:PSensor-install-step9.png|center|250px|Click to enlarge]]

Using “Motor” slider, adjust direction of sensor so that you can see floor at the bottom and actor is fully visible (with hands up if needed):
[[Image:KSensor-recording-adjust-motor.png|center|457px|Click to enlarge]]

Set output directory for recorded video:
[[Image:KSensor-recording-dest-folder.png|center]]
--&gt;  

Please run '''iPi Recorder''' and complete setup and background recording steps following the instructions:

[[iPi Recorder Setup]] 

{{:Performance Kinect}}</rev>
        </revisions>
      </page>
      <page pageid="44" ns="0" title="Recording actor&#039;s performance">
        <revisions>
          <rev xml:space="preserve">=== Recommended layout of an action video ===

* Enter the actor. 
* Strike a T-pose.
* Action

&lt;table border=&quot;0&quot;&gt;&lt;tr&gt;
&lt;td&gt;[[Image:T-pose.png]]&lt;/td&gt;
&lt;td&gt;[[Image:Action.png]]&lt;/td&gt;
&lt;/tr&gt;&lt;/table&gt;

=== T-pose ===

It is preferable to have actor strike a “T-pose” before the actual action. The software will need T-pose for building actor appearance model during tracking. If you make several takes of one actor you do not need to re-record T-pose before each take.

When using the depth sensors, it is recommended to face the palms down, as it corresponds to the default orientation of the model's hand bones.
When using color cameras, it is recommended to face the palms forward, as it helps the software in determining the right color for the model's hands.

=== Takes ===

[http://en.wikipedia.org/wiki/Take Take] is a concept originating from cinematography. In a nutshell, take is a single continuous recorded performance. 

Usually it is a good idea to record multiple takes of the same motion, because a lot of things can go wrong for purely artistic reasons. 

=== Iterations ===
 
A common problem with motion capture is “clipping” in resulting 3D character animation. For example, arms entering the body of animated computer-generated character. Many CG characters have various items and attachments like a bullet-proof vest, a fantasy armor or a helmet. It can be easy for an actor to forget about the shape of the CG model. 

For this reason, you may need to schedule more than one motion capture session for the same motions. Recommended approach is:
* Record the videos
* Process the videos in iPiStudio 
* Import your target character into iPiStudio and review the resulting animation 
* Give feedback to the actor
* Schedule another motion capture session if needed

=== Ian Chisholm's hints on motion capture ===

Ian Chisholm is a [http://en.wikipedia.org/wiki/Machinima machinima] director and actor and the creator of critically acclaimed [http://www.clearskiesthemovie.com/ Clear Skies] machinima series. Below are some hints from [http://www.ipisoft.com/forum/viewtopic.php?f=3&amp;t=5421 his motion capture guide] based on his experience with motion capture for Clear Skies III.

==== Three handy hints for acting out mocap: ====

# Don’t weave and bob around like you’re in a normal conversation – it looks terrible when finally onscreen.  You need to be fairly (but not completely) static when acting.

# If you are recording several lines in one go, make sure you have lead in and lead out between each one, i.e. stand still!  Otherwise, the motions blend into each other and it’s hard to pick a start and end point for each take.

# Stand a bit like a gorilla – have your arms out from your sides: &lt;br&gt; [[File:Gorilla.jpg]] &lt;br&gt; Well, obviously not quite that much.  But anyway, if you don’t, you’ll find the arms clip slightly into the models and they look daft.

If you have a lot of capture to do, you need to strike a balance between short and long recordings.  Aim for 30 seconds to 2 minutes.  Too long is a pain to work on later due to the fiddlyness of setting up takes, and too short means you are forever setting up T-poses.

==== Takes ====

Because motion capture is not a perfect art, and neither is acting, it’s best to perform multiple takes.  I found that three was the best amount for most motion capture.  Take less if it’s a basic move, take more if it’s complex and needs to be more accurate.  It will make life easier for you in the processing stage if you signal the break between takes – I did this by reaching out one arm and holding up fingers to show which take it was.

==== Naming conventions ====

As it’s the same actor looking exactly the same each and every time, and there is no sound, and the capture is in lowres 320*200, you really need to name the files very clearly so that you later know which act, scene, character, and line(s) the capture is for.

My naming convention was based on act, scene, character, page number of the scene, line number, and take number.  You end up with something unpleasant to read like A3S1_JR_P2_L41_t3 but it’s essential when you’ve got 1500 actions to record.</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>