https://wiki.ipisoft.com/api.php?action=feedcontributions&feedformat=atom&user=MiniiPiSoft Wiki - User contributions [en]2026-07-07T12:54:27ZUser contributionsMediaWiki 1.18.5https://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2014-02-15T20:52:10Z<p>Mini: /* Blender */</p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|350px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|350px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). If you export animation to format different from format your target character was imported in, only rig will be exported. If you use the same format for export, skin will be exported as well.<br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|500px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|200px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters.<br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://vimeo.com/57823600 Maya HumanIK Mocap retarget with iPi Mocap Studio, by Wes McDermott]<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
* [http://www.youtube.com/watch?v=IP6AwFNkmm8 Humanik Maya 2012 Part 6]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX.<br />
<br />
=== Valve Source Filmmaker ===<br />
<br />
==== DMX ====<br />
<br />
First, you need to import your character (or its skeleton) into iPi Mocap Studio, for motion transfer.<br />
<br />
There are currently 3 ways of doing this:<br />
<br />
# You can import an animation DMX (in default pose) into iPi Mocap Studio. Since it has a skeleton, it should be enough for motion transfer. To create an animation DMX with default pose, you can add your character to your scene in Source Filmmaker and export DMX for corresponding animation node:<br />
#* open "Animation Set Editor Tab";<br />
#* click "+" -> "Create Animation Set for New Model";<br />
#* choose a model and click "Open";<br />
#* export animation for your model, in '''ASCII''' DMX format;<br />
#*: ''There is a checkbox named '''Ascii''' in the top area of the export dialog.''<br />
# Alternatively, you can just import an SMD file with your character into iPi Mocap Studio. For example, SMD files for all Team Fortress 2 characters can be found in your SDK in a location similar to the following (you need to have Source SDK installed): C:\Program Files (x86)\Steam\steamapps\<your steam name>\sourcesdk_content\tf\modelsrc\player\pyro\parts\smd\pyro_model.smd).<br />
# If you created a custom character in Maya, you should be able to export it in DMX model fromat. (Please [https://developer.valvesoftware.com/wiki/Maya see Valve documentation] on how to do this).<br />
<br />
Then you can import your model DMX into iPi Mocap Studio. Current version of iPi Mocap Studio cannot display character skin, but it should display the skeleton. Skeleton should be enough for motion transfer.<br />
<br />
To export animation in DMX, you should just use "General..." export menu item in iPi Mocap Studio and choose DMX from the list of supported formats. You may also want to uncheck "Export T-pose in first frame" option on the "Export" tab in iPi Mocap Studio.<br />
<br />
Now you can import your animation into Source Filmmaker. There will be some warnings about missing channels for face bones but you can safely ignore them.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_dmx_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_dmx_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_dmx_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_dmx_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_dmx_step5.png|thumb|400px|Step 5]]</td><br />
<td>[[Image:export_dmx_step6.png|thumb|400px|Step 6]]</td><br />
</tr></table><br />
<br />
==== Old way involving Maya ====<br />
<br />
This was used until [[iPi Mocap Studio]] got DMX support. And still may be useful in case of any troubles with DMX. Please see the following video tutorial series:<br />
<br />
http://www.youtube.com/playlist?list=PLD4409518E1F04270<br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format. For latest versions of Blender, you can use the MotionBuilder-compatible BVH export option. For Blender version 2.59 or older you can use the "Blender 2.59 or older" export option.<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg|700px]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
[http://wiki.secondlife.com/wiki/How_to_create_animations#Setting_up_Poser SecondLife documentation] contains a link to useful [http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/avatar_mesh.zip SL avatar files]. The ZIP file includes a BVH of the "default pose". Be sure to have that.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk</div>Minihttps://wiki.ipisoft.com/IPiStudio_System_RequirementsIPiStudio System Requirements2014-01-15T08:06:10Z<p>Mini: Redirected page to IPi Studio System Requirements</p>
<hr />
<div>#REDIRECT [[IPi Studio System Requirements]]</div>Minihttps://wiki.ipisoft.com/TroubleshootingTroubleshooting2014-01-15T08:04:16Z<p>Mini: </p>
<hr />
<div>=== Installation problems ===<br />
<br />
'''Potential problem:''' after installation, [[iPi Mocap Studio]] crashes on first start. <br />
<br />
'''Possible cause:''' very often, this is caused by incompatible video card. Another possible reason is broken .NET Framework installation or broken DirectX installation. <br />
<br />
'''Solution:''' check [[IPi Studio System Requirements | system requirements]] and make sure your operating system and .NET Framework is up to date.<br />
* You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features of your video card.<br />
<br />
<table border="0"><br />
<tr><td>[[Image:GPUz_example.gif|thumb|402px|]]</td></tr><br />
</table><br />
<br />
* Some systems (for example some laptops and older Mac Minis) have both integrated graphics and discrete graphics. You may need to disable integrated graphics when working with iPi Mocap Studio. To do this, please use tools offered by your discrete video card manufacturer (e.g. Nvidia or AMD).<br />
<br />
=== Two Kinects don't work together ===<br />
<br />
'''Potential problem:''' two Kinect sensors do not work togethter.<br />
<br />
'''Possible cause:''' Most probably, both Kinects were plugged into one USB controller. In this case 1 USB controller bandwidth is not enough to handle video from 2 Kinects.<br />
<br />
'''Solution:''' Each Kinect should be plugged into separate USB controller. Please refer to documentation [[User_Guide_for_Dual_Kinect_Sensor_Configuration#Software_Installation]]<br />
<br />
=== How to report bugs and issues ===<br />
<br />
When reporting bugs and issues, please specify the following info: <br />
* exact version of your operating system;<br />
* exact model of your video card (you can use [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-Z] to find out the model of your video card);<br />
* the number and models of your cameras.<br />
You can post your bug reports on our [http://www.ipisoft.com/forum/ User Forum] or send them to iPiSoft tech support email.<br />
<br />
=== How to send a video to iPiSoft tech support ===<br />
<br />
Sending your videos to iPiSoft tech support can be helpful if you experience a problem with iPiSoft's system. iPiSoft promises to use your video only for debugging and not to disclose it to third parties. <br />
<br />
To send a video, please upload it to some file sharing server like [http://www.filefactory.com/ filefactory.com] and send us the link. The other way is [[Huge Files Sharing Using uTorrent|using peer-to-peer technology]].<br />
<br />
If you cannot send a video because of its huge size, consider sending screenshots. Screenshots are less informative then video but still they are helpful for diagnosing various problems with tracking.</div>Minihttps://wiki.ipisoft.com/IPi_Mocap_Studio_System_RequirementsIPi Mocap Studio System Requirements2014-01-09T18:35:35Z<p>Mini: </p>
<hr />
<div>* Computer (desktop or laptop):<br />
** ''CPU:'' x86 compatible (Intel Pentium 4 or higher, AMD Athlon or higher), dual- or quad- core is preferable<br />
** ''Operating system:'' Windows 8, 7, XP SP3, Vista (x86 or x64)<br />
** ''Video card:'' Direct3D 10-capable (Shader Model 4.0) gaming-class graphics card<br />
*** '''Intel integrated graphics is not supported'''<br />
*** for more info see [[Cameras and accessories#Video_Card]]<br />
*** You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features of your video card.<br />
<br />
<table border="0"><br />
<tr><td>[[Image:GPUz_example.gif|thumb|402px|]]</td></tr><br />
</table></div>Minihttps://wiki.ipisoft.com/IPi_Mocap_Studio_System_RequirementsIPi Mocap Studio System Requirements2014-01-09T18:35:16Z<p>Mini: </p>
<hr />
<div>* Computer (desktop or laptop):<br />
** ''CPU:'' x86 compatible (Intel Pentium 4 or higher, AMD Athlon or higher), dual- or quad- core is preferable<br />
** ''Operating system:'' Windows 8, 7, XP SP3, Vista (x86 or x64)<br />
** ''Video card:'' Direct3D 10-capable (Shader Model 4.0) gaming-class graphics card<br />
*** '''Intel integrated graphics is not supported'''<br />
*** for more info see [[Cameras and accessories#Video_Card]]<br />
*** You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features on your video card.<br />
<br />
<table border="0"><br />
<tr><td>[[Image:GPUz_example.gif|thumb|402px|]]</td></tr><br />
</table></div>Minihttps://wiki.ipisoft.com/TroubleshootingTroubleshooting2014-01-09T18:34:03Z<p>Mini: </p>
<hr />
<div>=== Installation problems ===<br />
<br />
'''Potential problem:''' after installation, [[iPi Mocap Studio]] crashes on first start. <br />
<br />
'''Possible cause:''' very often, this is caused by incompatible video card. Another possible reason is broken .NET Framework installation or broken DirectX installation. <br />
<br />
'''Solution:''' check [[IPiStudio System Requirements | system requirements]] and make sure your operating system and .NET Framework is up to date.<br />
* You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features of your video card.<br />
<br />
<table border="0"><br />
<tr><td>[[Image:GPUz_example.gif|thumb|402px|]]</td></tr><br />
</table><br />
<br />
* Some systems (for example some laptops and older Mac Minis) have both integrated graphics and discrete graphics. You may need to disable integrated graphics when working with iPi Mocap Studio. To do this, please use tools offered by your discrete video card manufacturer (e.g. Nvidia or AMD).<br />
<br />
=== Two Kinects don't work together ===<br />
<br />
'''Potential problem:''' two Kinect sensors do not work togethter.<br />
<br />
'''Possible cause:''' Most probably, both Kinects were plugged into one USB controller. In this case 1 USB controller bandwidth is not enough to handle video from 2 Kinects.<br />
<br />
'''Solution:''' Each Kinect should be plugged into separate USB controller. Please refer to documentation [[User_Guide_for_Dual_Kinect_Sensor_Configuration#Software_Installation]]<br />
<br />
=== How to report bugs and issues ===<br />
<br />
When reporting bugs and issues, please specify the following info: <br />
* exact version of your operating system;<br />
* exact model of your video card (you can use [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-Z] to find out the model of your video card);<br />
* the number and models of your cameras.<br />
You can post your bug reports on our [http://www.ipisoft.com/forum/ User Forum] or send them to iPiSoft tech support email.<br />
<br />
=== How to send a video to iPiSoft tech support ===<br />
<br />
Sending your videos to iPiSoft tech support can be helpful if you experience a problem with iPiSoft's system. iPiSoft promises to use your video only for debugging and not to disclose it to third parties. <br />
<br />
To send a video, please upload it to some file sharing server like [http://www.filefactory.com/ filefactory.com] and send us the link. The other way is [[Huge Files Sharing Using uTorrent|using peer-to-peer technology]].<br />
<br />
If you cannot send a video because of its huge size, consider sending screenshots. Screenshots are less informative then video but still they are helpful for diagnosing various problems with tracking.</div>Minihttps://wiki.ipisoft.com/TroubleshootingTroubleshooting2014-01-09T18:33:24Z<p>Mini: </p>
<hr />
<div>=== Installation problems ===<br />
<br />
'''Potential problem:''' after installation, [[iPi Mocap Studio]] crashes on first start. <br />
<br />
'''Possible cause:''' very often, this is caused by incompatible video card. Another possible reason is broken .NET Framework installation or broken DirectX installation. <br />
<br />
'''Solution:''' check [[IPiStudio System Requirements | system requirements]] and make sure your operating system and .NET Framework is up to date.<br />
* You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features of your video card.<br />
<br />
<table border="0"><br />
<tr><td>[[Image:GPUz_example.gif|thumb|402px|]]</td></tr><br />
</table><br />
<br />
* Some systems (for example some laptops and older Mac Minis) have both integrated graphics and discrete graphics. You may need to disable integrated graphics when working with iPi Mocap Studio. To do this, please use tools offered by your discrete GPU video card manufacturer (e.g. Nvidia or AMD).<br />
<br />
=== Two Kinects don't work together ===<br />
<br />
'''Potential problem:''' two Kinect sensors do not work togethter.<br />
<br />
'''Possible cause:''' Most probably, both Kinects were plugged into one USB controller. In this case 1 USB controller bandwidth is not enough to handle video from 2 Kinects.<br />
<br />
'''Solution:''' Each Kinect should be plugged into separate USB controller. Please refer to documentation [[User_Guide_for_Dual_Kinect_Sensor_Configuration#Software_Installation]]<br />
<br />
=== How to report bugs and issues ===<br />
<br />
When reporting bugs and issues, please specify the following info: <br />
* exact version of your operating system;<br />
* exact model of your video card (you can use [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-Z] to find out the model of your video card);<br />
* the number and models of your cameras.<br />
You can post your bug reports on our [http://www.ipisoft.com/forum/ User Forum] or send them to iPiSoft tech support email.<br />
<br />
=== How to send a video to iPiSoft tech support ===<br />
<br />
Sending your videos to iPiSoft tech support can be helpful if you experience a problem with iPiSoft's system. iPiSoft promises to use your video only for debugging and not to disclose it to third parties. <br />
<br />
To send a video, please upload it to some file sharing server like [http://www.filefactory.com/ filefactory.com] and send us the link. The other way is [[Huge Files Sharing Using uTorrent|using peer-to-peer technology]].<br />
<br />
If you cannot send a video because of its huge size, consider sending screenshots. Screenshots are less informative then video but still they are helpful for diagnosing various problems with tracking.</div>Minihttps://wiki.ipisoft.com/TroubleshootingTroubleshooting2014-01-09T18:32:08Z<p>Mini: /* Installation problems */</p>
<hr />
<div>=== Installation problems ===<br />
<br />
'''Potential problem:''' after installation, [[iPi Mocap Studio]] crashes on first start. <br />
<br />
'''Possible cause:''' very often, this is caused by incompatible video card. Another possible reason is broken .NET Framework installation or broken DirectX installation. <br />
<br />
'''Solution:''' check [[IPiStudio System Requirements | system requirements]] and make sure your operating system and .NET Framework is up to date.<br />
* You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features of your video card.<br />
<br />
<table border="0"><br />
<tr><td>[[Image:GPUz_example.gif|thumb|402px|]]</td></tr><br />
</table><br />
<br />
* Some systems (for example laptops, Mac Mini, MS Surface) have both integrated graphics and discrete graphics. You may need to disable integrated graphics when working with iPi Mocap Studio. To do this, please use tools offered by your discrete GPU video card manufacturer (e.g. Nvidia or AMD).<br />
<br />
=== Two Kinects don't work together ===<br />
<br />
'''Potential problem:''' two Kinect sensors do not work togethter.<br />
<br />
'''Possible cause:''' Most probably, both Kinects were plugged into one USB controller. In this case 1 USB controller bandwidth is not enough to handle video from 2 Kinects.<br />
<br />
'''Solution:''' Each Kinect should be plugged into separate USB controller. Please refer to documentation [[User_Guide_for_Dual_Kinect_Sensor_Configuration#Software_Installation]]<br />
<br />
=== How to report bugs and issues ===<br />
<br />
When reporting bugs and issues, please specify the following info: <br />
* exact version of your operating system;<br />
* exact model of your video card (you can use [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-Z] to find out the model of your video card);<br />
* the number and models of your cameras.<br />
You can post your bug reports on our [http://www.ipisoft.com/forum/ User Forum] or send them to iPiSoft tech support email.<br />
<br />
=== How to send a video to iPiSoft tech support ===<br />
<br />
Sending your videos to iPiSoft tech support can be helpful if you experience a problem with iPiSoft's system. iPiSoft promises to use your video only for debugging and not to disclose it to third parties. <br />
<br />
To send a video, please upload it to some file sharing server like [http://www.filefactory.com/ filefactory.com] and send us the link. The other way is [[Huge Files Sharing Using uTorrent|using peer-to-peer technology]].<br />
<br />
If you cannot send a video because of its huge size, consider sending screenshots. Screenshots are less informative then video but still they are helpful for diagnosing various problems with tracking.</div>Minihttps://wiki.ipisoft.com/TroubleshootingTroubleshooting2014-01-09T18:26:13Z<p>Mini: </p>
<hr />
<div>=== Installation problems ===<br />
<br />
'''Potential problem:''' after installation, [[iPi Mocap Studio]] crashes on first start. <br />
<br />
'''Possible cause:''' very often, this is caused by incompatible video card. Another possible reason is broken .NET Framework installation or broken DirectX installation. <br />
<br />
'''Solution:''' check [[IPiStudio System Requirements | system requirements]] and make sure your operating system and .NET Framework is up to date.<br />
* You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features on your video card.<br />
<br />
<table border="0"><br />
<tr><td>[[Image:GPUz_example.gif|thumb|402px|]]</td></tr><br />
</table><br />
<br />
=== Two Kinects don't work together ===<br />
<br />
'''Potential problem:''' two Kinect sensors do not work togethter.<br />
<br />
'''Possible cause:''' Most probably, both Kinects were plugged into one USB controller. In this case 1 USB controller bandwidth is not enough to handle video from 2 Kinects.<br />
<br />
'''Solution:''' Each Kinect should be plugged into separate USB controller. Please refer to documentation [[User_Guide_for_Dual_Kinect_Sensor_Configuration#Software_Installation]]<br />
<br />
=== How to report bugs and issues ===<br />
<br />
When reporting bugs and issues, please specify the following info: <br />
* exact version of your operating system;<br />
* exact model of your video card (you can use [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-Z] to find out the model of your video card);<br />
* the number and models of your cameras.<br />
You can post your bug reports on our [http://www.ipisoft.com/forum/ User Forum] or send them to iPiSoft tech support email.<br />
<br />
=== How to send a video to iPiSoft tech support ===<br />
<br />
Sending your videos to iPiSoft tech support can be helpful if you experience a problem with iPiSoft's system. iPiSoft promises to use your video only for debugging and not to disclose it to third parties. <br />
<br />
To send a video, please upload it to some file sharing server like [http://www.filefactory.com/ filefactory.com] and send us the link. The other way is [[Huge Files Sharing Using uTorrent|using peer-to-peer technology]].<br />
<br />
If you cannot send a video because of its huge size, consider sending screenshots. Screenshots are less informative then video but still they are helpful for diagnosing various problems with tracking.</div>Minihttps://wiki.ipisoft.com/File:GPUz_example.gifFile:GPUz example.gif2014-01-09T18:25:02Z<p>Mini: </p>
<hr />
<div></div>Minihttps://wiki.ipisoft.com/TroubleshootingTroubleshooting2014-01-09T18:21:53Z<p>Mini: /* Installation problems */</p>
<hr />
<div>=== Installation problems ===<br />
<br />
'''Potential problem:''' after installation, [[iPi Mocap Studio]] crashes on first start. <br />
<br />
'''Possible cause:''' very often, this is caused by incompatible video card. Another possible reason is broken .NET Framework installation or broken DirectX installation. <br />
<br />
'''Solution:''' check [[IPiStudio System Requirements | system requirements]] and make sure your operating system and .NET Framework is up to date.<br />
* You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features on your video card.<br />
<br />
=== Two Kinects don't work together ===<br />
<br />
'''Potential problem:''' two Kinect sensors do not work togethter.<br />
<br />
'''Possible cause:''' Most probably, both Kinects were plugged into one USB controller. In this case 1 USB controller bandwidth is not enough to handle video from 2 Kinects.<br />
<br />
'''Solution:''' Each Kinect should be plugged into separate USB controller. Please refer to documentation [[User_Guide_for_Dual_Kinect_Sensor_Configuration#Software_Installation]]<br />
<br />
=== How to report bugs and issues ===<br />
<br />
When reporting bugs and issues, please specify the following info: <br />
* exact version of your operating system;<br />
* exact model of your video card (you can use [http://www.techpowerup.com/downloads/SysInfo/GPU-Z/ GPU-Z] to find out the model of your video card);<br />
* the number and models of your cameras.<br />
You can post your bug reports on our [http://www.ipisoft.com/forum/ User Forum] or send them to iPiSoft tech support email.<br />
<br />
=== How to send a video to iPiSoft tech support ===<br />
<br />
Sending your videos to iPiSoft tech support can be helpful if you experience a problem with iPiSoft's system. iPiSoft promises to use your video only for debugging and not to disclose it to third parties. <br />
<br />
To send a video, please upload it to some file sharing server like [http://www.filefactory.com/ filefactory.com] and send us the link. The other way is [[Huge Files Sharing Using uTorrent|using peer-to-peer technology]].<br />
<br />
If you cannot send a video because of its huge size, consider sending screenshots. Screenshots are less informative then video but still they are helpful for diagnosing various problems with tracking.</div>Minihttps://wiki.ipisoft.com/Main_PageMain Page2014-01-09T18:19:05Z<p>Mini: </p>
<hr />
<div><!-- Header --><br />
<table style="width: 100%; margin:1em 0 0 0; background:none; border-spacing: 0px;"><br />
<tr><td style="width: 59%; border:1px solid #ddd; background:#f9f9f9; vertical-align:top; color:#000; padding:0.2em"><br />
<br />
<center><table border=0 style="background:#f9f9f9; margin:.3em .5em; text-align:center"><tr><br />
<td colspan=3><div style="font-size:122%; padding-bottom:.8em; padding-top:.3em">'''iPi Motion Capture''' consists of two products:</div></td><br />
</tr><tr><br />
<td rowspan=2>[[Image:R-256.png|96px|link=iPi Recorder]]</td><br />
<td style="text-align:left; padding-left:.4em; padding-right:1.3em; vertical-align:top;"><br />
<div style="font-size:110%;">'''[[iPi Recorder|iPi RECORDER]]'''</div><br />
<div style="font-size:95%; color:#444444;">''free software for making records''</div><br />
</td><br />
<td rowspan=2>[[Image:S-256.png|96px|link=iPi Mocap Studio]]</td><br />
</tr><tr><br />
<td style="text-align:right; padding-left:1.3em; padding-right:.4em; vertical-align:bottom;"><br />
<div style="font-size:95%; color:#444444;">''paid software for processing records''</div><br />
<div style="font-size:110%;">'''[[iPi Mocap Studio|iPi MOCAP STUDIO]]'''</div><br />
</td><br />
</tr><tr><td colspan=3><br />
<div style="margin-top:1.2em; font-size:95%; border:1px dashed #aaaaaa;">[http://ipisoft.com/store Editions]&nbsp;([http://ipisoft.com/store/compare-editions compare])&nbsp;&nbsp;&nbsp;| &nbsp;&nbsp;&nbsp;[http://ipisoft.com/download '''Downloads''']&nbsp;&nbsp;&nbsp;|&nbsp;&nbsp;&nbsp;[[License|Licensing Policy]]</div><br />
</td></tr></table></center><br />
</td><br />
<br />
<td style="width: 2%"></td><br />
<br />
<td style="width: 39%; border:1px solid #F7D4C0; background:#FFFFF7; vertical-align:center; color:#000; padding:0.2em; text-align:center;"><br />
<center>[http://ipisoft.com/gallery/ Gallery of Demo Videos]</center><br />
<center>[http://ipisoft.com/pr/iPi_Motion_Capture_Brochure.pdf Product Brochure]</center><br />
<center>[[FAQ|Frequently Asked Questions]]</center><br />
<center><div style="width:50%; height:1px; border-top:1px solid #BC967E; margin:0.7em;"></div></center><br />
<center>[http://blog.ipisoft.com Monthly Competition: Win Standard License]</center><br />
<center><div style="width:50%; height:1px; border-top:1px solid #BC967E; margin:0.7em;"></div></center><br />
<center><span style="color:#BC967E; font-size:110%">f e a t u r e d &nbsp;&nbsp; a r t i c l e s :</span></center><br />
<center>[[Getting Started with Triple Depth Sensor Configuration|Triple Depth Sensor Conf.]]</center><br />
<center>[[Batch Processing]]</center><br />
<center>[[Multiple GPUs]]</center><br />
<center>[[Troubleshooting]]</center><br />
</td><br />
</table><br />
<br />
<br />
<center><font color="#444444">'''Possible Configurations:'''</font></center><br />
<br />
<!-- General --><br />
<table style="width: 100%; margin:1em 0 0 0; background:none; border-spacing: 0px;"><br />
<tr><td style="width: 49%; border:1px solid #cef2e0; background:#f5fffa; vertical-align:top; color:#000; padding:0.2em"><br />
<!-- Single Kinect --><br />
<h2 id="mp-tfa-h2" style="margin:3px 3px 12px 3px; background:#cef2e0; font-size:120%; font-weight:bold; border:1px solid #a3bfb1; text-align:center; color:#000; padding:0.2em 0.4em;">Single Depth Sensor Configuration</h2><br />
<center>[[Image:Kinect-small.png|150px|link=User Guide for Single Depth Sensor Configuration]]</center><br />
''<p style="font-size:95%; color:#444444; padding-left:0.4em; padding-right:0.4em; text-align:justify; margin:3px;">iPi Soft uses its own tracking algorithms that give much better accuracy than other [http://en.wikipedia.org/wiki/Kinect Kinect]/[http://www.asus.com/Multimedia/Motion_Sensor/Xtion_PRO_LIVE Xtion]/[http://www.primesense.com/get-your-sensor2/ Carmine]-based mocaps available in the market. This configuration is very easy to use, as it does not require calibration. For those who haven't had experience with mocap systems before, it is a good option to start from.</p>''<br />
* [[Quick Start Guide for Single Depth Sensor Configuration|Quick Start Guide]]<br />
* [[User Guide for Single Depth Sensor Configuration|User Guide]]<br />
* [[Sample video and project (single depth sensor)|Sample video and project]]<br />
* <font size="-2">[[iPi Recorder System Requirments for iPi MoCap with Single Depth Sensor|System Requirements for Recording]]</font><br />
* <font size="-2">[[iPi Studio System Requirements|System Requirements for Processing]]</font><br />
<br/><br />
<p style="margin:8px 3px; font-size:95%; border:1px dashed #a3bfb1; text-align:right; color:#006600; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/software/express-edition Express], [http://ipisoft.com/software/basic-edition Basic], [http://ipisoft.com/software/standard-edition Standard] '''[[Editions Comparison|(?)]]'''</p><br />
</td><td style="width: 2%"></td><td style="width: 49% ; height:100%; border:1px solid #cedff2; background:#f5faff; vertical-align:top; color:#000; padding:0.2em "><br />
<!-- Dual Kinect --><br />
<h2 id="mp-tfa-h2" style="margin:3px 3px 12px 3px; background:#cedff2; font-size:120%; font-weight:bold; border:1px solid #a3b0bf; text-align:center; color:#000; padding:0.2em 0.4em">Dual Depth Sensor Configuration</h2><br />
<center>[[Image:Kinect-small.png|130px|link=User Guide for Dual Depth Sensor Configuration]]&nbsp;&nbsp; [[Image:Kinect-small.png|130px|link=User Guide for Dual Depth Sensor Configuration]]</center><br />
''<p style="font-size:95%; color:#444444; padding-left:0.4em; padding-right:0.4em; text-align:justify; margin:15px 3px;">Dual-[http://en.wikipedia.org/wiki/Kinect Kinect]/[http://www.asus.com/Multimedia/Motion_Sensor/Xtion_PRO_LIVE Xtion]/[http://www.primesense.com/get-your-sensor2/ Carmine] configuration combines ease of use and flexibility of a single Kinect/Xtion/Carmine with power of multi-camera system. With two Microsoft Kinects, or ASUS Xtions, or PrimeSense Carmines animators can accurately capture complex motions including 360-degrees turns.</p>''<br />
* [[Quick Start Guide for Dual Depth Sensor Configuration|Quick Start Guide]]<br />
* [[User Guide for Dual Depth Sensor Configuration|User Guide]]<br />
* [[Sample video and project (dual depth sensor)|Sample video and project]]<br />
* [http://nycppnews.com/2012/02/12/joe-herman-reviews-ipi-softs-markerless-motion-capture-system Review by Joe Herman]<br />
* <font size="-2">[[iPi Recorder System Requirments for Two Depth Sensors|System Requirements for Recording]]</font><br />
* <font size="-2">[[iPi Studio System Requirements|System Requirements for Processing]]</font><br />
<div style="margin:8px 3px; font-size:95%; border:1px dashed #a3bfb1; text-align:right; color:#000066; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/software/basic-edition Basic], [http://ipisoft.com/software/standard-edition Standard] '''[[Editions Comparison|(?)]]''' </div><br />
</td></tr><br />
<tr style="height:1em"><td colspan=3> </td></tr><br />
<tr><td style="width: 49% ; height:100%; border:1px solid #ddcef2; background:#faf5ff; vertical-align:top; color:#000; padding:0.2em "><br />
<!-- Multiple MS Eye --><br />
<h2 id="mp-tfa-h2" style="margin:3px 3px 12px 3px; background:#ddcef2; font-size:120%; font-weight:bold; border:1px solid #ddcef2; text-align:center; color:#000; padding:0.2em 0.4em"> Multiple PS Eye Cameras Configuration </h2><br />
<center>[[Image:PSEye-small.png|80px|link=User Guide for Multiple PlayStation Eye Cameras Configuration]]&nbsp;&nbsp;[[Image:PSEye-small.png|80px|link=User Guide for Multiple PlayStation Eye Cameras Configuration]]&nbsp;&nbsp;[[Image:PSEye-small.png|80px|link=User Guide for Multiple PlayStation Eye Cameras Configuration]]</center><br />
''<p style="font-size:95%; color:#444444; padding-left:0.4em; padding-right:0.4em; text-align:justify; margin:15px 3px;">[http://en.wikipedia.org/wiki/PlayStation_Eye Sony PS Eye] cameras are recommended as they give very good quality of video at up to 60 fps. Other cameras like webcams or DirectShow-compatible USB or FireWire cameras may be used but are not recommended. The configuration with 3 to 8 [http://en.wikipedia.org/wiki/PlayStation_Eye Sony PS Eye] cameras is the most powerful option. It allows you to track very complex motions in a big capture area (up to '''20 by 20 feet''' or '''7 by 7 meters''').</p>''<br />
* [[Quick Start Guide for Multiple PlayStation Eye Cameras Configuration|Quick Start Guide]]<br />
* [[Cameras and accessories]]<br />
* [[User Guide for Multiple PlayStation Eye Cameras Configuration|User Guide]]<br />
* [[Sample_video_and_project_(four_PS_Eye)|Sample video and project]]<br />
* <font size="-2">[[iPi Recorder System Requirements for Multiple PlayStation Eye Cameras System|System Requirements for Recording]]</font><br />
* <font size="-2">[[iPi Studio System Requirements|System Requirements for Processing]]</font><br />
<div style="margin:8px 3px; font-size:95%; border:1px dashed #ddcef2; text-align:right; color:#330066; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/software/basic-edition Basic] <font size="-2">(up to 4 cams)</font>, [http://ipisoft.com/software/standard-edition Standard] <font size="-2">(up to 8 cams)</font> '''[[Editions Comparison|(?)]]'''</div><br />
</td><td style="width: 2%"></td><td style="width: 49%; border:1px solid #f2cee0; background:#fff5fa; vertical-align:top; color:#000; padding:0.2em" ><br />
<!-- Post processing --><br />
<h2 id="mp-tfa-h2" style="margin:3px 3px 12px 3px; background:#f2cee0; font-size:110%; font-weight:bold; border:1px solid #bfa3b1; text-align:center; color:#000; padding:0.2em 0.4em;">Integrated Clean-Up and Motion Transfer</h2><br />
<center>[[Image:ipi-motion-transfer-small.png|180px|link=Animation export and motion transfer]]</center><br />
''<p style="font-size:95%; color:#444444; padding-left:0.4em; padding-right:0.4em; text-align:justify; margin:15px 3px;">[[iPi Mocap Studio]] includes integrated animation clean-up and motion transfer. So you do not necessarily need expensive third-party software like [http://usa.autodesk.com/adsk/servlet/pc/index?id=13581855&siteID=123112 Motion Builder]. These tools are included in all [[Editions Comparison|editions]].</p>''<br />
<br />
* [[Clean-up]]<br />
<br />
* [[Animation export and motion transfer]]<br />
<br />
</td></tr><br />
</table><br />
<br />
<br />
<center><font color="#444444">'''Advanced Features:'''</font></center><br />
<br />
<table style="width: 100%; margin:1em 0 0 0; background:none; border-spacing: 0px;"><br />
<!-- The first row --><br />
<tr><td style="width:30%; vertical-align:top; background:#fcfcfc; border:1px solid #ddd; padding:8px;"><br />
<!-- Multiple Actors --><br />
<h2 style="border-bottom:1px solid #cacaca; background:white; font-size:120%; font-weight:500; text-align:center; color:#777777; padding:0.2em 0.4em; margin:-8px -8px 0px -8px;">Multiple Actors</h2><br />
<center><div style="padding:0.8em;">[[Image:multiple_actors_pic.png|link=Getting started with multiple actors]]</div></center><br />
<div style="padding:0.1em;"><br />
<center>&nbsp;</center><br />
<center>[[Getting started with multiple actors|User Guide]]</center><br />
<center>&nbsp;</center><br />
</div><br />
<div style="margin:8px 3px 0px 3px; font-size:90%; border:1px dashed #cacaca; text-align:right; color:#777777; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/software/standard-edition Standard] </div><br />
</td><td style="width:4%">&nbsp;</td><br />
<td style="width:30%; vertical-align:top; background:#fcfcfc; border:1px solid #ddd; padding:8px;"><br />
<!-- Motion Controllers --><br />
<h2 style="border-bottom:1px solid #cacaca; background:white; font-size:120%; font-weight:500; text-align:center; color:#777777; padding:0.2em 0.4em; margin:-8px -8px 0px -8px">Motion Controllers</h2><br />
<center><div style="padding:0.8em;">[[Image:motion_controllers_pic.png|link=Getting started with motion controllers]]</div></center><br />
<div style="padding:0.1em;"><br />
<center>[[Getting started with motion controllers|User Guide]]</center><br />
<center>[[Using motion controller for head tracking|Using for Head Tracking]]</center><br />
<center>[[Motion in Joy Installation|Motion in Joy]]</center><br />
</div><br />
<div style="margin:8px 3px 0px 3px; font-size:90%; border:1px dashed #cacaca; text-align:right; color:#777777; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/store All] </div><br />
</td><td style="width:4%">&nbsp;</td><br />
<td style="width:30%; vertical-align:top; background:#fcfcfc; border:1px solid #ddd; padding:8px;"><br />
<!-- Keyframing --><br />
<h2 style="border-bottom:1px solid #cacaca; background:white; font-size:120%; font-weight:500; text-align:center; color:#777777; padding:0.2em 0.4em; margin:-8px -8px 0px -8px">Keyframing</h2><br />
<center><div style="padding:0.8em;">[[Image:keyframing_pic.png|link=Getting started with hand keyframing]]</div></center><br />
<div style="padding:0.1em;"><br />
<center>&nbsp;</center><br />
<center>[[Getting started with hand keyframing|User Guide]]</center><br />
<center>&nbsp;</center><br />
</div><br />
<div style="margin:8px 3px 0px 3px; font-size:90%; border:1px dashed #cacaca; text-align:right; color:#777777; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/store All] </div><br />
</td></tr><br />
<!-- Separator --><br />
<tr><td colspan="5" style="height:1.5em;">&nbsp;</td></tr><br />
<!-- The second row --><br />
<tr><td style="width:30%; vertical-align:top; background:#fcfcfc; border:1px solid #ddd; padding:8px;"><br />
<!-- Multiple GPUs --><br />
<h2 style="border-bottom:1px solid #cacaca; background:white; font-size:120%; font-weight:500; text-align:center; color:#777777; padding:0.2em 0.4em; margin:-8px -8px 0px -8px;">Multiple GPUs</h2><br />
<center><div style="padding:0.8em;">[[Image:multiple_gpus_pic.png|link=Multiple GPUs]]</div></center><br />
<div style="padding:0.1em;"><br />
<center>[[Multiple GPUs|User Guide]]</center><br />
</div><br />
<div style="margin:8px 3px 0px 3px; font-size:90%; border:1px dashed #cacaca; text-align:right; color:#777777; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/software/standard-edition Standard] </div><br />
</td><td style="width:4%">&nbsp;</td><br />
<td style="width:30%; vertical-align:top; background:#fcfcfc; border:1px solid #ddd; padding:8px;"><br />
<!-- Batch Processing --><br />
<h2 style="border-bottom:1px solid #cacaca;background:white; font-size:120%; font-weight:500; text-align:center; color:#777777; padding:0.2em 0.4em; margin:-8px -8px 0px -8px;">Batch Processing</h2><br />
<center><div style="padding:0.8em;">[[Image:batch_pic.png|link=Batch Processing]]</div></center><br />
<div style="padding:0.1em;"><br />
<center>[[Batch Processing|User Guide]]</center><br />
</div><br />
<div style="margin:8px 3px 0px 3px; font-size:90%; border:1px dashed #cacaca; text-align:right; color:#777777; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/software/standard-edition Standard] </div><br />
</td><td style="width:4%">&nbsp;</td><br />
<td style="width:30%; vertical-align:top; background:#fcfcfc; border:1px solid #ddd; padding:8px;"><br />
<!-- Audio Recording --><br />
<h2 style="border-bottom:1px solid #cacaca; background:white; font-size:120%; font-weight:500; text-align:center; color:#777777; padding:0.2em 0.4em; margin:-8px -8px 0px -8px">Audio Recording</h2><br />
<center><div style="padding:0.8em;">[[Image:audio_recording_pic.png|link=Audio Recording]]</div></center><br />
<div style="padding:0.1em;"><br />
<center>[[Audio Recording|User Guide]]</center><br />
</div><br />
<div style="margin:8px 3px 0px 3px; font-size:90%; border:1px dashed #cacaca; text-align:right; color:#777777; padding:0.2em 0.4em;">'''Editions:''' [http://ipisoft.com/store All] </div><br />
</td></tr><br />
</table><br />
<br />
<br />
<br />
<br />
<font size="-2"><br />
<center><font color="#444444">'''Printable Documentation'''</font></center><br />
<br />
<center>[[User Guide for Single Depth Sensor Configuration (printable version)]]</center><br />
<center>[[User Guide for Dual Depth Sensor Configuration (printable version)]]</center><br />
<center>[[User Guide for Multiple PlayStation Eye Cameras Configuration (printable version)]]</center><br />
<br />
</font><br />
<br />
__NOTOC__ __NOEDITSECTION__ __NOTITLE__</div>Minihttps://wiki.ipisoft.com/IPi_Mocap_Studio_System_RequirementsIPi Mocap Studio System Requirements2014-01-09T18:16:11Z<p>Mini: </p>
<hr />
<div>* Computer (desktop or laptop):<br />
** ''CPU:'' x86 compatible (Intel Pentium 4 or higher, AMD Athlon or higher), dual- or quad- core is preferable<br />
** ''Operating system:'' Windows 8, 7, XP SP3, Vista (x86 or x64)<br />
** ''Video card:'' Direct3D 10-capable (Shader Model 4.0) gaming-class graphics card<br />
*** '''Intel integrated graphics is not supported'''<br />
*** for more info see [[Cameras and accessories#Video_Card]]<br />
*** You can use [http://www.techpowerup.com/gpuz/ GPU-z] and [http://www.cpuid.com/softwares/cpu-z.html CPU-z] to detect exact version and features on your video card.</div>Minihttps://wiki.ipisoft.com/Multiple_GPUsMultiple GPUs2013-06-27T15:48:42Z<p>Mini: /* Introduction to Multiple GPUs in iPi Mocap Studio */</p>
<hr />
<div>= Multiple GPUs in iPi Mocap Studio =<br />
<br />
== Introduction to Multiple GPUs in iPi Mocap Studio ==<br />
Starting with version 2.4, you can use multiple GPUs to speed up tracking in iPi Mocap Studio.<br />
You should be aware of the following limitations:<br />
* You can use only 1, 2 or 4 GPUs inside one PC. Other configurations (for example, 3 GPUs) are not supported.<br />
* Currently we recommend using only single-GPU video cards (e.g. NVidia GTX 780). iPi Soft never tested multi-GPU video cards like Nvidia GTX 690, and it is not known if there is a way to disable SLI/Crossfire for multi-GPU video card (to make it usable in iPi Mocap Studio).<br />
* For best efficiency, all GPUs must be of approximately the same performance. iPi Mocap Studio cannot balance load for multiple GPUs with different performance levels, so mixing low-end and high-end GPUs will result in very poor performance.<br />
* Due to synchronization overhead, performance scaling is not linear. Performance gain diminishes with the number of GPUs. Using second identical GPU will speed up tracking approximately by a factor of 1.6 (instead of factor of 2, as one might expect).<br />
* Performance gain is more noticeable for large number of cameras (for example, 8 cameras). If you are using just 1 kinect camera, you may experience negligible performance improvement from a multi-GPU configuration.<br />
* Combining multiple low-end GPUs makes little sense. You may achieve much better performance by upgrading to a single high-end gaming GPU like Nvidia GTX 780.<br />
<br />
== How to Configure Multiple GPUs ==<br />
To configure your multiple video cards for use in iPi Mocap Studio, you should perform the following steps:<br />
# Disable SLI or Crossfire (see example screenshot).<br />
# Extend Windows desktop to use additional video adapters. Go to the following path in Windows Control Panel: <blockquote>Control Panel\Appearance and Personalization\Display\Screen Resolution</blockquote> and select "Multiple displays: Extend this displays" for your additional video cards. Click "Apply".<br />
# Restart iPi Mocap Studio. Now it should be able to use your additional GPUs.<br />
<br />
[[Image:Disable_SLI.png]]<br />
<br />
[[Image:Extend_desktop.png]]</div>Minihttps://wiki.ipisoft.com/Multiple_GPUsMultiple GPUs2013-06-27T15:47:50Z<p>Mini: /* Introduction to Multiple GPUs in iPi Mocap Studio */</p>
<hr />
<div>= Multiple GPUs in iPi Mocap Studio =<br />
<br />
== Introduction to Multiple GPUs in iPi Mocap Studio ==<br />
Starting with version 2.4, you can use multiple GPUs to speed up tracking in iPi Mocap Studio.<br />
You should be aware of the following limitations:<br />
* You can use only 1, 2 or 4 GPUs inside one PC. Other configurations (for example, 3 GPUs) are not supported.<br />
* Currently we recommend using only single-GPU video cards (e.g. NVidia GTX 780). iPi Soft never tested multi-GPU video cards like Nvidia GTX 690, and it is not known if there is a way to disable SLI/Crossfire for multi-GPU video card (to make it usable in iPi Mocap Studio).<br />
* For best efficiency, all GPUs must be of approximately the same performance. iPi Mocap Studio cannot balance load for multiple GPUs with different performance levels, so mixing low-end and high-end GPUs will result in very poor performance.<br />
* Due to synchronization overhead, performance scaling is not linear. Performance gain diminishes with the number of GPUs. Using second identical GPU will speed up tracking approximately by a factor of 1.6 (instead of factor of 2, as one might expect).<br />
* Performance gain is more noticeable for large number of cameras (for example, 8 cameras). If you are using just 1 kinect camera, you may experience negligible performance improvement from a multi-GPU configuration.<br />
* Combining multiple low-end GPUs makes little sense. You may achieve much better performance by upgrading to a high-end gaming GPU like Nvidia GTX 780.<br />
<br />
== How to Configure Multiple GPUs ==<br />
To configure your multiple video cards for use in iPi Mocap Studio, you should perform the following steps:<br />
# Disable SLI or Crossfire (see example screenshot).<br />
# Extend Windows desktop to use additional video adapters. Go to the following path in Windows Control Panel: <blockquote>Control Panel\Appearance and Personalization\Display\Screen Resolution</blockquote> and select "Multiple displays: Extend this displays" for your additional video cards. Click "Apply".<br />
# Restart iPi Mocap Studio. Now it should be able to use your additional GPUs.<br />
<br />
[[Image:Disable_SLI.png]]<br />
<br />
[[Image:Extend_desktop.png]]</div>Minihttps://wiki.ipisoft.com/Multiple_GPUsMultiple GPUs2013-06-27T15:47:05Z<p>Mini: /* Introduction to Multiple GPUs in iPi Mocap Studio */</p>
<hr />
<div>= Multiple GPUs in iPi Mocap Studio =<br />
<br />
== Introduction to Multiple GPUs in iPi Mocap Studio ==<br />
Starting with version 2.4, you can use multiple GPUs to speed up tracking in iPi Mocap Studio.<br />
You should be aware of the following limitations:<br />
* You can use only 1, 2 or 4 GPUs inside one PC. Other configurations (for example, 3 GPUs) are not supported.<br />
* Currently we recommend using only single-GPU video cards (e.g. NVidia GTX 780). iPi Soft never tested multi-GPU video cards like Nvidia GTX 690, and it is not known if there is a way to disable SLI/Crossfire for multi-GPU video card (to make it usable in iPi Mocap Studio).<br />
* For best efficiency, all GPUs must be of approximately the same performance. iPi Mocap Studio cannot balance load for multiple GPUs with different performance levels, so mixing low-end and high-end GPUs will result in very poor performance.<br />
* Due to synchronization overhead, performance scaling is not linear. Performance gain diminishes with the number of GPUs. Using second identical GPU will speed up tracking approximately by a factor of 1.6 (instead of 2, as one might expect).<br />
* Performance gain is more noticeable for large number of cameras (for example, 8 cameras). If you are using just 1 kinect camera, you may experience negligible performance improvement from a multi-GPU configuration.<br />
* Combining multiple low-end GPUs makes little sense. You may achieve much better performance by upgrading to a high-end gaming GPU like Nvidia GTX 780.<br />
<br />
== How to Configure Multiple GPUs ==<br />
To configure your multiple video cards for use in iPi Mocap Studio, you should perform the following steps:<br />
# Disable SLI or Crossfire (see example screenshot).<br />
# Extend Windows desktop to use additional video adapters. Go to the following path in Windows Control Panel: <blockquote>Control Panel\Appearance and Personalization\Display\Screen Resolution</blockquote> and select "Multiple displays: Extend this displays" for your additional video cards. Click "Apply".<br />
# Restart iPi Mocap Studio. Now it should be able to use your additional GPUs.<br />
<br />
[[Image:Disable_SLI.png]]<br />
<br />
[[Image:Extend_desktop.png]]</div>Minihttps://wiki.ipisoft.com/File:Extend_desktop.pngFile:Extend desktop.png2013-06-27T15:45:03Z<p>Mini: uploaded a new version of &quot;File:Extend desktop.png&quot;: Extend Windows Desktop</p>
<hr />
<div>Extend Windows Desktop</div>Minihttps://wiki.ipisoft.com/File:Extend_desktop.pngFile:Extend desktop.png2013-06-27T15:40:21Z<p>Mini: Extend Windows Desktop</p>
<hr />
<div>Extend Windows Desktop</div>Minihttps://wiki.ipisoft.com/File:Disable_SLI.pngFile:Disable SLI.png2013-06-27T15:39:39Z<p>Mini: Disable SLI or Crossfire</p>
<hr />
<div>Disable SLI or Crossfire</div>Minihttps://wiki.ipisoft.com/Multiple_GPUsMultiple GPUs2013-06-27T15:38:38Z<p>Mini: </p>
<hr />
<div>= Multiple GPUs in iPi Mocap Studio =<br />
<br />
== Introduction to Multiple GPUs in iPi Mocap Studio ==<br />
Starting with version 2.4, you can use multiple GPUs to speed up tracking in iPi Mocap Studio.<br />
You should be aware of the following limitations:<br />
* You can use only 1, 2 or 4 GPUs inside one PC. Other configurations (for example, 3 GPUs) are not supported.<br />
* Currently we recommend using only single-GPU video cards (e.g. NVidia GTX 780). iPi Soft never tested multi-GPU video cards like Nvidia GTX 690, and it is not known if there is a way to disable SLI/Crossfire for multi-GPU video card (to make it usable in iPi Mocap Studio).<br />
* For best efficiency, all GPUs must be of approximately the same performance (e.g. all must be top-performing). iPi Mocap Studio cannot balance load for multiple GPUs with different performance levels, so mixing low-end and high-end GPUs will result in very poor performance.<br />
* Due to synchronization overhead, performance scaling is not linear. Performance gain diminishes with the number of GPUs. Using second identical GPU will speed up tracking approximately by a factor of 1.6 (instead of 2, as one might expect).<br />
* Performance gain is more noticeable for large number of cameras (for example, 8 cameras). If you are using just 1 kinect camera, you may experience negligible performance improvement from a multi-GPU configuration.<br />
* Combining multiple low-end GPUs makes little sense. You may achieve much better performance by upgrading to a high-end gaming GPU like Nvidia GTX 780.<br />
<br />
== How to Configure Multiple GPUs ==<br />
To configure your multiple video cards for use in iPi Mocap Studio, you should perform the following steps:<br />
# Disable SLI or Crossfire (see example screenshot).<br />
# Extend Windows desktop to use additional video adapters. Go to the following path in Windows Control Panel: <blockquote>Control Panel\Appearance and Personalization\Display\Screen Resolution</blockquote> and select "Multiple displays: Extend this displays" for your additional video cards. Click "Apply".<br />
# Restart iPi Mocap Studio. Now it should be able to use your additional GPUs.<br />
<br />
[[Image:Disable_SLI.png]]<br />
<br />
[[Image:Extend_desktop.png]]</div>Minihttps://wiki.ipisoft.com/Multiple_GPUsMultiple GPUs2013-06-27T15:33:36Z<p>Mini: Created page with "= Multiple GPUs in iPi Mocap Studio = == Introduction to Multiple GPUs in iPi Mocap Studio == Starting with version 2.4, you can use multiple GPUs to speed up tracking in iPi..."</p>
<hr />
<div>= Multiple GPUs in iPi Mocap Studio =<br />
<br />
== Introduction to Multiple GPUs in iPi Mocap Studio ==<br />
Starting with version 2.4, you can use multiple GPUs to speed up tracking in iPi Mocap Studio.<br />
You should be aware of the following limitations:<br />
* You can use only 1, 2 or 4 GPUs inside one PC. Other configurations (for example, 3 GPUs) are not supported.<br />
* Currently we recommend using only single-GPU video cards (e.g. NVidia GTX 780). iPi Soft never tested multi-GPU video cards like Nvidia GTX 690, and it is not known if there is a way to disable SLI/Crossfire for multi-GPU video card (to make it usable in iPi Mocap Studio).<br />
* For best efficiency, all GPUs must be of approximately the same performance (e.g. all must be top-performing). iPi Mocap Studio cannot balance load for multiple GPUs with different performance levels, so mixing low-end and high-end GPUs will result in very poor performance.<br />
* Due to synchronization overhead, performance scaling is not linear. Performance gain diminishes with the number of GPUs. Using second identical GPU will speed up tracking approximately by a factor of 1.6 (instead of 2, as one might expect).<br />
* Performance gain is more noticeable for large number of cameras (for example, 8 cameras). If you are using just 1 kinect camera, you may experience negligible performance improvement from a multi-GPU configuration.<br />
* Combining multiple low-end GPUs makes little sense. You may achieve much better performance by upgrading to a high-end gaming GPU like Nvidia GTX 780.<br />
<br />
== How to Configure Multiple GPUs ==<br />
To configure your multiple video cards for use in iPi Mocap Studio, you should perform the following steps:<br />
# Disable SLI or Crossfire (see example screenshot).<br />
# Extend Windows desktop to use additional video adapters. Go to the following path in Windows Control Panel: <blockquote>Control Panel\Appearance and Personalization\Display\Screen Resolution</blockquote> and select "Multiple displays: Extend this displays" for your additional video cards. Click "Apply".<br />
# Restart iPi Mocap Studio. Now it should be able to use your additional GPUs.</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2013-01-28T16:16:06Z<p>Mini: /* Maya */</p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|350px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|350px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|500px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|200px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters.<br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://vimeo.com/57823600 Maya HumanIK Mocap retarget with iPi Mocap Studio, by Wes McDermott]<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
* [http://www.youtube.com/watch?v=IP6AwFNkmm8 Humanik Maya 2012 Part 6]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX.<br />
<br />
=== Valve Source Filmmaker ===<br />
<br />
==== DMX ====<br />
<br />
First, you need to import your character (or its skeleton) into iPi Mocap Studio, for motion transfer.<br />
<br />
There are currently 3 ways of doing this:<br />
<br />
# You can import an animation DMX (in default pose) into iPi Mocap Studio. Since it has a skeleton, it should be enough for motion transfer. To create an animation DMX with default pose, you can add your character to your scene in Source Filmmaker and export DMX for corresponding animation node:<br />
#* open "Animation Set Editor Tab";<br />
#* click "+" -> "Create Animation Set for New Model";<br />
#* choose a model and click "Open";<br />
#* export animation for your model, in '''ASCII''' DMX format;<br />
#*: ''There is a checkbox named '''Ascii''' in the top area of the export dialog.''<br />
# Alternatively, you can just import an SMD file with your character into iPi Mocap Studio. For example, SMD files for all Team Fortress 2 characters can be found in your SDK in a location similar to the following (you need to have Source SDK installed): C:\Program Files (x86)\Steam\steamapps\<your steam name>\sourcesdk_content\tf\modelsrc\player\pyro\parts\smd\pyro_model.smd).<br />
# If you created a custom character in Maya, you should be able to export it in DMX model fromat. (Please [https://developer.valvesoftware.com/wiki/Maya see Valve documentation] on how to do this).<br />
<br />
Then you can import your model DMX into iPi Mocap Studio. Current version of iPi Mocap Studio cannot display character skin, but it should display the skeleton. Skeleton should be enough for motion transfer.<br />
<br />
To export animation in DMX, you should just use "General..." export menu item in iPi Mocap Studio and choose DMX from the list of supported formats. You may also want to uncheck "Export T-pose in first frame" option on the "Export" tab in iPi Mocap Studio.<br />
<br />
Now you can import your animation into Source Filmmaker. There will be some warnings about missing channels for face bones but you can safely ignore them.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_dmx_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_dmx_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_dmx_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_dmx_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_dmx_step5.png|thumb|400px|Step 5]]</td><br />
<td>[[Image:export_dmx_step6.png|thumb|400px|Step 6]]</td><br />
</tr></table><br />
<br />
==== Old way involving Maya ====<br />
<br />
This was used until [[iPi Mocap Studio]] got DMX support. And still may be useful in case of any troubles with DMX. Please see the following video tutorial series:<br />
<br />
http://www.youtube.com/playlist?list=PLD4409518E1F04270<br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg|700px]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
[http://wiki.secondlife.com/wiki/How_to_create_animations#Setting_up_Poser SecondLife documentation] contains a link to useful [http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/avatar_mesh.zip SL avatar files]. The ZIP file includes a BVH of the "default pose". Be sure to have that.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk</div>Minihttps://wiki.ipisoft.com/IPi_Mocap_Studio_ChangelogIPi Mocap Studio Changelog2013-01-19T08:57:38Z<p>Mini: </p>
<hr />
<div><div style="color:#222222; border:dashed 1px gray; padding:4pt; margin:0.5em; background-color:#FAFAFA"><br />
''Here you can find history of recent versions of [[iPi Mocap Studio]].''<br />
<br />
''[[iPi Mocap Studio]] has built-in auto update functionality. Auto update feature is configured so that checks for update are made once per day. It helps to reduce the start time of the application. If you want to update ASAP - you can use the '''Help''' -> '''Check for Update''' menu item.''<br />
<br />
''Note that both these features require Internet connection. Alternatively (in case of troubles with auto update), you can download and run the updated installation program from [http://files.ipisoft.com/iPiMocapStudioSetup.exe our website].''<br />
</div><br />
<br />
{{VersionShortInfo|2.2.1.145|Jan 18, 2013|http://files.ipisoft.com/iPiMocapStudioSetup.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Tracking improvements:<br />
** ''Much'' improved shoulder tracking.<br />
** Improved spine tracking.<br />
** Improved head tracking for RGB cameras (with support for head rotations around Y axis).<br />
*** ''Note that head tracking significantly slows down tracking speed. Head tracking is optional, you can turn it off in tracking options.''<br />
** New '''"Refine"''' functionality (useful for cleanup).<br />
* UI improvements:<br />
** Timeline zoom and scrolling.<br />
** Color picker tools for actor appearance items.<br />
** Additional capabilities in 3D Viewport navigation:<br />
*** Left mouse button drag &mdash; move view (the same as middle mouse button drag).<br />
*** <tt>Shift</tt> + right mouse button drag &mdash; rotate view around viewpoint.<br />
*** <tt>Ctrl</tt> + right mouse button drag &mdash; orbit view around selected bone (extremely helpful in case of fingers position editing).<br />
<br />
<center><table border=0><tr><td>[[Image:ipi-mocap-studio-refine-pass.png|thumb|300px|Refine Pass]]</td><td>[[Image:ipi-mocap-studio-color-picker-tools.png|thumb|300px|Color Picker Tools]]</td></tr></table></center><br />
<br />
<center><table border=0><tr><td>[[Image:ipi-mocap-studio-timeline-zoom.png|thumb|600px|Time Line Zoom]]</td></tr></table></center><br />
<br />
<br />
<br />
{{VersionShortInfo|2.2.0.144|Dec 13, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.2.0.144.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Support for '''hand/prop tracking''' using data recorded from motion controllers. See [[Getting started with motion controllers#Tracking|Getting Started]] guide.<br />
*: '''Warning.''' Projects with motion controller data cannot be open by previous versions of [[iPi Mocap Studio]].<br />
* Long-awaited '''Undo/Redo''' for manual editing and for automatic processing. Standard shortcuts <tt>Ctrl+Z</tt>, <tt>Ctrl+Y</tt> work.<br />
* Additional commands for working with pose (under menu '''Edit'''):<br />
** Copy pose of selected bone's children (and all descendants) only. Available only as menu item. Useful for copying hand poses (without rotation of hand's joint itself).<br />
** Paste pose to all frames within ROI (<tt>Ctrl+Shift+V</tt>).<br />
** Save pose to a file from the Clipboard (<tt>Ctrl+P</tt>). Using this and the following command, you can make a sort of a pose library.<br />
** Load pose from a file to the Clipboard (<tt>Ctrl+L</tt>).<br />
* Navigating through skeleton using the keyboard:<br />
** Go to parent bone (<tt>[</tt>)<br />
** Go to child bone (<tt>]</tt>). Moves selection to a first child. If there are no children, moves to a next sibling bone (or parent's sibling, etc). Makes a full walk around the skeleton.<br />
** Cycle through bones of the same level of hierarchy (<tt>Shift+[</tt>, <tt>Shift+]</tt>)<br />
* Improved skeleton visualization. Joint size and bone thickness are proportional to bone length. Now fingers are much easier to edit.<br />
* Improved calibration accuracy for dual depth sensor configuration.<br />
* Improved accuracy of feet tracking with PS Eyes.<br />
* Improved actor's model.<br />
* Menu item '''Help > Keyboard Shortcuts''' shows all keyboard shortcuts in one place. The same information is available as [[Keyboard_Shortcuts_(iPi_Mocap_Studio)|a wiki page]].<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Opening video causes ''Device does not support multi-level texture width and height values that are not powers of 2.'' error with some video cards.<br />
* Running calibration with ROI less than 8 frames crashes the app.<br />
<br />
<br />
{{VersionShortInfo|2.1.3.143|Nov 23, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.3.143.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* New items in '''Edit''' menu for coping parts of body position:<br />
** '''Copy Pose of Selected Bone''' - copies rotations for selected bone to Clipboard. For paste use '''Paste Pose''' menu item.<br />
** '''Copy Pose of Selected Bone with Children''' - copies rotations for selected bone and all its children to Clipboard. For paste use '''Paste Pose''' menu item.<br />
* If video from depth sensors like MS Kinect or ASUS Xtion has RGB channel then now you can colorize 3D point cloud using data from RGB camera. To turn on this feature please use '''View -> Color Point Cloud with RGB Data''' menu item.<br />
* Added <tt>iPiMocap:</tt> namespace only for MotionBuilder-optimized FBX output ('''Export -> For MotionBuilder (FBX, BVH)''' menu item).<br />
* Improved look and feel of Open and Save file dialogs for modern operating systems like Windows 7.<br />
<br />
<center><table border=0><tr><td>[[Image:color-point-cloud-with-rgb-data.png|thumb|400px|Color Point Cloud with RGB Data]]</td></tr></table></center><br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Incorrect import of characters with 3D MAX Biped bone naming conventions (in particular, CryEngine default characters).<br />
* Export as DMX produces incorrect DMX file if in windows localization setting coma is selected as decimal symbol.<br />
<br />
<br />
<br />
{{VersionShortInfo|2.1.2.142|Nov 08, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.2.142.exe}}<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Importing of some target characters doesn't work.<br />
* Version is not visible in About box.<br />
<br />
<br />
{{VersionShortInfo|2.1.2.141|Nov 07, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.2.141.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Added support for Valve [https://developer.valvesoftware.com/wiki/DMX '''DMX''' format] export/import for use with [http://www.sourcefilmmaker.com/ Source Film Maker].<br />
* Fixed the issue with bone naming in FBX (removed "iPi:" prefix).<br />
* Improved point cloud visualization for depth data from Kinect and Xtion sensors.<br />
* New default background color in 3D viewport.<br />
* Size of application files is significantly reduced (3x times) which saves disk space and improves speed of automatic updates.<br />
* Added ability to activate license key for all OS users (to know how please contact our support).<br />
* Minor UI improvements and bug fixes.<br />
<br />
<br />
{{VersionShortInfo|2.1.1.140|Oct 13, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.1.140.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Improved spine tracking. Removed the problem with unnatural spine position when stooping down<br />
* Improved jitter removal for torso and head<br />
* Precise bone selection using dropdown menu of '''Select''' toolbar button<br />
* MRU list for projects, available in menu and toolbar<br />
* Nice '''Check for update''' window with link to [[iPi Mocap Studio Changelog|changelog]]<br />
* Showing release notes at first launch of new version<br />
<br />
* Small UI improvements:<br />
** Current frame number made editable for quick goto<br />
** Merged '''Play''' and '''Pause''' buttons<br />
** Highlighting selected bones when editing motion transfer profile<br />
** Alphabetical sorting and removing of items in MRU lists<br />
** '''Export animation XXX''' menu items moved to submenu, '''Export animation XXX''' buttons merged to single dropdown button<br />
<table border="0"><tr><br />
<td>[[Image:Studio-140-select-bone.png|thumb|300px|Select bone]]</td><br />
<td>[[Image:Studio-140-MRU-projects-menu.png|thumb|300px|MRU project list]]</td><br />
<td>[[Image:Studio-140-merged-export-animation.png|thumb|300px|Export animation button]]</td><br />
</tr></table><br />
<br />
<br />
{{VersionShortInfo|2.1.0.139|Sep 30, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.0.139.exe}}<br />
<br />
[[File:IPi Studio new features-2.1.0.139.png|thumb|UI changes]]<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* '''Head tracking'''. Enabled by the '''Enable head tracking''' checkbox on the '''Tracking''' tab.<br />
:: '''''Note.''''' ''This version does not track face orientation, that is head rotation around Y axis.''<br />
* Switched places of '''Track Forward''' and '''Track Backward''' buttons. The new placement is more intuitive, but may cause confusion for existing users.<br />
* Improvements in '''Jitter Removal'''.<br />
* Simplified rules for auto-adjusting the '''Region of Interest'''. Now it's touched only if the tracking starts when the current position is outside the ROI.<br />
* More compact project files.<br />
:: '''''Note.''''' ''Projects saved by this version can not be opened by the previous releases.''<br />
* Bundled user guides are displayed within the new built-in viewer.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Error when running '''Jitter Removal''' while current position is outside of the '''Region of Interest'''.<br />
* Error on opening project in certain circumstances.<br />
* Installation program won't run on Windows XP x64.<br />
<br />
{{VersionShortInfo|2.0.1.138|Aug 04, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.1.138.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Refines in actor model including skeleton proportions.<br />
:: '''''Note.''''' ''Existing projects should be re-tracked with new model to take advantages of new version.''<br />
* Alignment of color video to depth point cloud for single and dual Kinect/Xtion projects. This alignment is based on internal calibration data from depth sensor and should work fine for various depth sensors. <br />
::'''''Note.''''' ''To turn off this alignment one can use '''View''' -> '''Align Color Video to Depth''' menu item.<br />
* Coloring of depth data in [[iPi Mocap Studio]] now is like coloring in [[iPi Recorder]].<br />
* For single and dual Kinect/Xtion projects background is hidden by default if color video is available.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.137|Jul 19, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.137.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Support for '''JPEG''' encoded Bayer tracks in video. Update of [[iPi Recorder]] with support for '''JPEG''' compression for PS Eyes will be published within a couple of days.<br />
* Improvements in '''FBX''' import concerning character skinning.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed error in clavicle retargeting.<br />
* Fixed issue in installer with .NET Framework installation on Windows Vista and later.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.135|Jul 03, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.135.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Experimental support for '''7-8''' color cameras. Auto detection of initial camera positions is not currently working well for these configurations, so it is disabled. This feature is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6132].<br />
* Improved unexpected errors handling.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed error in activation code. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6154] and [http://forum.ipisoft.com/viewtopic.php?f=5&t=6158].<br />
<br />
<br />
{{VersionShortInfo|2.0.0.134|Jun 30, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.134.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Support for any order of Euler angles in '''FBX''' export. This is especially useful for '''LightWave''' users. See this topic list for discussions about this problem.<br />
* Unexpected error dialog. If an unexpected error occurs in the application, this dialog appears just before the application is terminated. It presents you a debug information. If you provide us with this information when reporting an error, this could greatly help us in investigating your issue.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Decreased memory footprint during calibration (specifically, marker detection).<br />
<br />
<br />
{{VersionShortInfo|2.0.0.133|Jun 17, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.133.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Check for update from application. Press the '''Help''' -> '''Check For Update''' menu item. For details, see [[iPi Recorder Changelog#ver. 2.0.0.12]] release notes.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed rounding error causing incorrect value of frames per second. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6113].<br />
* Fixed incorrect background processing. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6115].<br />
* Fixed application failures when returning from logon screen and standby mode. This issue was primarily discussed by email. Partial discussion is in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6110].<br />
* Fixed ignoring the '''Export T-pose in first frame''' option and '''Recenter coordinate system on character in first frame''' checkboxes. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6117].<br />
<br />
<br />
{{VersionShortInfo|2.0.0.132|Jun 13, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.132.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* List of most recently used target characters along with motion transfer profiles.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed several issues in exporting/importing animations for 3D MAX and MotionBuilder.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.131|Jun 07, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.131.exe}}<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed coordinate system bug in tracking the left hand.<br />
* Fixed startup error occurring on some WinXP/Vista computers. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6077].<br />
<br />
<br />
{{VersionShortInfo|2.0.0.130|Jun 02, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.130.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Different menu item and toolbar button for creating new project ('''File''' -> '''New project…''' and '''New''' respectively).<br />
* '''File''' -> '''Open''' is renamed to '''File''' -> '''Open project…''' and now opens only project files.<br />
* '''File''' -> '''Import animation''' menu item is renamed to '''File''' -> '''Open animation…'''<br />
* Now visibility of tabs, toolbar buttons and menu items depends on project type.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Application installer is slightly updated (some users have experienced troubles with previous one).<br />
* Bug fix in behavior of '''Scene Scale''' slider for multi-camera calibration projects.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.129|Jun 01, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.129.exe}}<br />
<br />
First public release of [[iPi Mocap Studio|iPi Mocap Studio 2]].<br />
<br />
If you're user of '''iPi Studio 1.x''' then please visit [[Migration from v1.x to v2.0]] article.<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* New project file format, incompatible with old one. The new format has important changes required for support of multiple actor capture and props capture in future versions.<br />
* New character model with optimizations for female characters.<br />
* New skeleton.<br />
* New video format ([[.iPiVideo file extension|'''.iPiVideo''']]). Old videos can be converted to new format using [[iPi Recorder#Converter]].<br />
* '''New project''' wizard.<br />
* Improved foot tracking.<br />
* Improved shoulder tracking.<br />
<br />
[[Category:iPi Mocap Studio]]</div>Minihttps://wiki.ipisoft.com/IPi_Mocap_Studio_ChangelogIPi Mocap Studio Changelog2013-01-19T08:56:51Z<p>Mini: </p>
<hr />
<div><div style="color:#222222; border:dashed 1px gray; padding:4pt; margin:0.5em; background-color:#FAFAFA"><br />
''Here you can find history of recent versions of [[iPi Mocap Studio]].''<br />
<br />
''[[iPi Mocap Studio]] has built-in auto update functionality. Auto update feature is configured so that checks for update are made once per day. It helps to reduce the start time of the application. If you want to update ASAP - you can use the '''Help''' -> '''Check for Update''' menu item.''<br />
<br />
''Note that both these features require Internet connection. Alternatively (in case of troubles with auto update), you can download and run the updated installation program from [http://files.ipisoft.com/iPiMocapStudioSetup.exe our website].''<br />
</div><br />
<br />
{{VersionShortInfo|2.2.1.145|Jan 18, 2013|http://files.ipisoft.com/iPiMocapStudioSetup.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Tracking improvements:<br />
** ''Much'' improved shoulder tracking.<br />
** Improved spine tracking.<br />
** Improved head tracking for RGB cameras (with support for head rotations around Y axis).<br />
*** ''Note that head tracking significantly slows down tracking speed. Head tracking is optional, so you can turn it off.''<br />
** New '''"Refine"''' functionality (useful for cleanup).<br />
* UI improvements:<br />
** Timeline zoom and scrolling.<br />
** Color picker tools for actor appearance items.<br />
** Additional capabilities in 3D Viewport navigation:<br />
*** Left mouse button drag &mdash; move view (the same as middle mouse button drag).<br />
*** <tt>Shift</tt> + right mouse button drag &mdash; rotate view around viewpoint.<br />
*** <tt>Ctrl</tt> + right mouse button drag &mdash; orbit view around selected bone (extremely helpful in case of fingers position editing).<br />
<br />
<center><table border=0><tr><td>[[Image:ipi-mocap-studio-refine-pass.png|thumb|300px|Refine Pass]]</td><td>[[Image:ipi-mocap-studio-color-picker-tools.png|thumb|300px|Color Picker Tools]]</td></tr></table></center><br />
<br />
<center><table border=0><tr><td>[[Image:ipi-mocap-studio-timeline-zoom.png|thumb|600px|Time Line Zoom]]</td></tr></table></center><br />
<br />
<br />
<br />
{{VersionShortInfo|2.2.0.144|Dec 13, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.2.0.144.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Support for '''hand/prop tracking''' using data recorded from motion controllers. See [[Getting started with motion controllers#Tracking|Getting Started]] guide.<br />
*: '''Warning.''' Projects with motion controller data cannot be open by previous versions of [[iPi Mocap Studio]].<br />
* Long-awaited '''Undo/Redo''' for manual editing and for automatic processing. Standard shortcuts <tt>Ctrl+Z</tt>, <tt>Ctrl+Y</tt> work.<br />
* Additional commands for working with pose (under menu '''Edit'''):<br />
** Copy pose of selected bone's children (and all descendants) only. Available only as menu item. Useful for copying hand poses (without rotation of hand's joint itself).<br />
** Paste pose to all frames within ROI (<tt>Ctrl+Shift+V</tt>).<br />
** Save pose to a file from the Clipboard (<tt>Ctrl+P</tt>). Using this and the following command, you can make a sort of a pose library.<br />
** Load pose from a file to the Clipboard (<tt>Ctrl+L</tt>).<br />
* Navigating through skeleton using the keyboard:<br />
** Go to parent bone (<tt>[</tt>)<br />
** Go to child bone (<tt>]</tt>). Moves selection to a first child. If there are no children, moves to a next sibling bone (or parent's sibling, etc). Makes a full walk around the skeleton.<br />
** Cycle through bones of the same level of hierarchy (<tt>Shift+[</tt>, <tt>Shift+]</tt>)<br />
* Improved skeleton visualization. Joint size and bone thickness are proportional to bone length. Now fingers are much easier to edit.<br />
* Improved calibration accuracy for dual depth sensor configuration.<br />
* Improved accuracy of feet tracking with PS Eyes.<br />
* Improved actor's model.<br />
* Menu item '''Help > Keyboard Shortcuts''' shows all keyboard shortcuts in one place. The same information is available as [[Keyboard_Shortcuts_(iPi_Mocap_Studio)|a wiki page]].<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Opening video causes ''Device does not support multi-level texture width and height values that are not powers of 2.'' error with some video cards.<br />
* Running calibration with ROI less than 8 frames crashes the app.<br />
<br />
<br />
{{VersionShortInfo|2.1.3.143|Nov 23, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.3.143.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* New items in '''Edit''' menu for coping parts of body position:<br />
** '''Copy Pose of Selected Bone''' - copies rotations for selected bone to Clipboard. For paste use '''Paste Pose''' menu item.<br />
** '''Copy Pose of Selected Bone with Children''' - copies rotations for selected bone and all its children to Clipboard. For paste use '''Paste Pose''' menu item.<br />
* If video from depth sensors like MS Kinect or ASUS Xtion has RGB channel then now you can colorize 3D point cloud using data from RGB camera. To turn on this feature please use '''View -> Color Point Cloud with RGB Data''' menu item.<br />
* Added <tt>iPiMocap:</tt> namespace only for MotionBuilder-optimized FBX output ('''Export -> For MotionBuilder (FBX, BVH)''' menu item).<br />
* Improved look and feel of Open and Save file dialogs for modern operating systems like Windows 7.<br />
<br />
<center><table border=0><tr><td>[[Image:color-point-cloud-with-rgb-data.png|thumb|400px|Color Point Cloud with RGB Data]]</td></tr></table></center><br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Incorrect import of characters with 3D MAX Biped bone naming conventions (in particular, CryEngine default characters).<br />
* Export as DMX produces incorrect DMX file if in windows localization setting coma is selected as decimal symbol.<br />
<br />
<br />
<br />
{{VersionShortInfo|2.1.2.142|Nov 08, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.2.142.exe}}<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Importing of some target characters doesn't work.<br />
* Version is not visible in About box.<br />
<br />
<br />
{{VersionShortInfo|2.1.2.141|Nov 07, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.2.141.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Added support for Valve [https://developer.valvesoftware.com/wiki/DMX '''DMX''' format] export/import for use with [http://www.sourcefilmmaker.com/ Source Film Maker].<br />
* Fixed the issue with bone naming in FBX (removed "iPi:" prefix).<br />
* Improved point cloud visualization for depth data from Kinect and Xtion sensors.<br />
* New default background color in 3D viewport.<br />
* Size of application files is significantly reduced (3x times) which saves disk space and improves speed of automatic updates.<br />
* Added ability to activate license key for all OS users (to know how please contact our support).<br />
* Minor UI improvements and bug fixes.<br />
<br />
<br />
{{VersionShortInfo|2.1.1.140|Oct 13, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.1.140.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Improved spine tracking. Removed the problem with unnatural spine position when stooping down<br />
* Improved jitter removal for torso and head<br />
* Precise bone selection using dropdown menu of '''Select''' toolbar button<br />
* MRU list for projects, available in menu and toolbar<br />
* Nice '''Check for update''' window with link to [[iPi Mocap Studio Changelog|changelog]]<br />
* Showing release notes at first launch of new version<br />
<br />
* Small UI improvements:<br />
** Current frame number made editable for quick goto<br />
** Merged '''Play''' and '''Pause''' buttons<br />
** Highlighting selected bones when editing motion transfer profile<br />
** Alphabetical sorting and removing of items in MRU lists<br />
** '''Export animation XXX''' menu items moved to submenu, '''Export animation XXX''' buttons merged to single dropdown button<br />
<table border="0"><tr><br />
<td>[[Image:Studio-140-select-bone.png|thumb|300px|Select bone]]</td><br />
<td>[[Image:Studio-140-MRU-projects-menu.png|thumb|300px|MRU project list]]</td><br />
<td>[[Image:Studio-140-merged-export-animation.png|thumb|300px|Export animation button]]</td><br />
</tr></table><br />
<br />
<br />
{{VersionShortInfo|2.1.0.139|Sep 30, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.1.0.139.exe}}<br />
<br />
[[File:IPi Studio new features-2.1.0.139.png|thumb|UI changes]]<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* '''Head tracking'''. Enabled by the '''Enable head tracking''' checkbox on the '''Tracking''' tab.<br />
:: '''''Note.''''' ''This version does not track face orientation, that is head rotation around Y axis.''<br />
* Switched places of '''Track Forward''' and '''Track Backward''' buttons. The new placement is more intuitive, but may cause confusion for existing users.<br />
* Improvements in '''Jitter Removal'''.<br />
* Simplified rules for auto-adjusting the '''Region of Interest'''. Now it's touched only if the tracking starts when the current position is outside the ROI.<br />
* More compact project files.<br />
:: '''''Note.''''' ''Projects saved by this version can not be opened by the previous releases.''<br />
* Bundled user guides are displayed within the new built-in viewer.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Error when running '''Jitter Removal''' while current position is outside of the '''Region of Interest'''.<br />
* Error on opening project in certain circumstances.<br />
* Installation program won't run on Windows XP x64.<br />
<br />
{{VersionShortInfo|2.0.1.138|Aug 04, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.1.138.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Refines in actor model including skeleton proportions.<br />
:: '''''Note.''''' ''Existing projects should be re-tracked with new model to take advantages of new version.''<br />
* Alignment of color video to depth point cloud for single and dual Kinect/Xtion projects. This alignment is based on internal calibration data from depth sensor and should work fine for various depth sensors. <br />
::'''''Note.''''' ''To turn off this alignment one can use '''View''' -> '''Align Color Video to Depth''' menu item.<br />
* Coloring of depth data in [[iPi Mocap Studio]] now is like coloring in [[iPi Recorder]].<br />
* For single and dual Kinect/Xtion projects background is hidden by default if color video is available.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.137|Jul 19, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.137.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Support for '''JPEG''' encoded Bayer tracks in video. Update of [[iPi Recorder]] with support for '''JPEG''' compression for PS Eyes will be published within a couple of days.<br />
* Improvements in '''FBX''' import concerning character skinning.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed error in clavicle retargeting.<br />
* Fixed issue in installer with .NET Framework installation on Windows Vista and later.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.135|Jul 03, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.135.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Experimental support for '''7-8''' color cameras. Auto detection of initial camera positions is not currently working well for these configurations, so it is disabled. This feature is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6132].<br />
* Improved unexpected errors handling.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed error in activation code. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6154] and [http://forum.ipisoft.com/viewtopic.php?f=5&t=6158].<br />
<br />
<br />
{{VersionShortInfo|2.0.0.134|Jun 30, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.134.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Support for any order of Euler angles in '''FBX''' export. This is especially useful for '''LightWave''' users. See this topic list for discussions about this problem.<br />
* Unexpected error dialog. If an unexpected error occurs in the application, this dialog appears just before the application is terminated. It presents you a debug information. If you provide us with this information when reporting an error, this could greatly help us in investigating your issue.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Decreased memory footprint during calibration (specifically, marker detection).<br />
<br />
<br />
{{VersionShortInfo|2.0.0.133|Jun 17, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.133.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Check for update from application. Press the '''Help''' -> '''Check For Update''' menu item. For details, see [[iPi Recorder Changelog#ver. 2.0.0.12]] release notes.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed rounding error causing incorrect value of frames per second. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6113].<br />
* Fixed incorrect background processing. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6115].<br />
* Fixed application failures when returning from logon screen and standby mode. This issue was primarily discussed by email. Partial discussion is in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6110].<br />
* Fixed ignoring the '''Export T-pose in first frame''' option and '''Recenter coordinate system on character in first frame''' checkboxes. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6117].<br />
<br />
<br />
{{VersionShortInfo|2.0.0.132|Jun 13, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.132.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* List of most recently used target characters along with motion transfer profiles.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed several issues in exporting/importing animations for 3D MAX and MotionBuilder.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.131|Jun 07, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.131.exe}}<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Fixed coordinate system bug in tracking the left hand.<br />
* Fixed startup error occurring on some WinXP/Vista computers. This issue is discussed in [http://forum.ipisoft.com/viewtopic.php?f=5&t=6077].<br />
<br />
<br />
{{VersionShortInfo|2.0.0.130|Jun 02, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.130.exe}}<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* Different menu item and toolbar button for creating new project ('''File''' -> '''New project…''' and '''New''' respectively).<br />
* '''File''' -> '''Open''' is renamed to '''File''' -> '''Open project…''' and now opens only project files.<br />
* '''File''' -> '''Import animation''' menu item is renamed to '''File''' -> '''Open animation…'''<br />
* Now visibility of tabs, toolbar buttons and menu items depends on project type.<br />
<br />
&nbsp;B U G &nbsp;&nbsp; F I X E S:<br />
* Application installer is slightly updated (some users have experienced troubles with previous one).<br />
* Bug fix in behavior of '''Scene Scale''' slider for multi-camera calibration projects.<br />
<br />
<br />
{{VersionShortInfo|2.0.0.129|Jun 01, 2012|http://files.ipisoft.com/iPiMocapStudioSetup-2.0.0.129.exe}}<br />
<br />
First public release of [[iPi Mocap Studio|iPi Mocap Studio 2]].<br />
<br />
If you're user of '''iPi Studio 1.x''' then please visit [[Migration from v1.x to v2.0]] article.<br />
<br />
&nbsp;N E W &nbsp;&nbsp; F E A T U R E S:<br />
* New project file format, incompatible with old one. The new format has important changes required for support of multiple actor capture and props capture in future versions.<br />
* New character model with optimizations for female characters.<br />
* New skeleton.<br />
* New video format ([[.iPiVideo file extension|'''.iPiVideo''']]). Old videos can be converted to new format using [[iPi Recorder#Converter]].<br />
* '''New project''' wizard.<br />
* Improved foot tracking.<br />
* Improved shoulder tracking.<br />
<br />
[[Category:iPi Mocap Studio]]</div>Minihttps://wiki.ipisoft.com/Depth_Sensors_ComparisonDepth Sensors Comparison2012-11-29T18:54:22Z<p>Mini: /* Kinect for Xbox vs Kinect for Windows */</p>
<hr />
<div>Starting from version 1.8.0.81, [[iPi Recorder]] supports [http://www.asus.com/Multimedia/Motion_Sensor/Xtion_PRO/ ASUS Xtion] and [http://www.asus.com/Multimedia/Motion_Sensor/Xtion_PRO_LIVE/ ASUS Xtion Live] devices (and also PRO modifications for developers). They are similar to [http://en.wikipedia.org/wiki/Kinect Microsoft Kinect] sensor and can be used in the same way. But there are certain differences that you can take into account before making decision on which device to choose for use with [[iPi Mocap Studio|iPi Desktop Motion Capture]] (iPi DMC).<br />
<br />
<br />
<center><table border=0><br />
<tr><td width="30%"><center>[[Image:Kinect-small.jpg|thumb|MS Kinect for Xbox or Windows]]</center></td><br />
<td width="5%"></td><br />
<td width="30%"><center>[[Image:ASUS-Xtion.jpg|thumb|ASUS Xtion]]</center></td><br />
<td width="5%"></td><br />
<td width="30%"><center>[[Image:ASUS-Xtion-live.jpg|thumb|ASUS Xtion Live]]</center></td></tr><br />
</table></center><br />
<br />
<br />
<br />
== Kinect vs Xtion ==<br />
<br />
Both [http://en.wikipedia.org/wiki/Kinect Microsoft Kinect] and [http://www.asus.com/Multimedia/Motion_Sensor/Xtion_PRO_LIVE/ ASUS Xtion] sensors are based on the same [http://www.primesense.com PrimeSense] infra-red technology. So all basic characteristics critical for full-body motion capture are generally the same. But there are certain differences that you can take into account:<br />
<br />
{| class="wikitable" border="1"<br />
! Device !! Pros !! Cons<br />
|-<br />
| Microsoft Kinect || <br />
* High quality of device drivers <br />
* Stable work with various hardware models<br />
* Has motor that can be controlled remotely by [[iPi Recorder]] application:<br>this makes device positioning more convenient<br />
|| <br />
* Bigger size (12" x 3" x 2.5" against 7" x 2" x 1.5")<br />
* Higher weight (3.0 lb agains 0.5 lb)<br />
* Require ACDC power supply<br />
* Only 30 fps frame rate<br />
|-<br />
| ASUS Xtion || <br />
* More compact ( 7" x 2" x 1.5" against 12" x 3" x 2.5") <br />
* Lighter weight (0.5 lb agains 3.0 lb) <br />
* Does not require power supply except USB<br />
* Allow 60 fps frame rate (at 320 x 240 resolution only)<br />
||<br />
* Less popular device<br />
* Lower drivers quality<br />
* Does not work with some USB controllers<br />
* No motor, allow only manual positioning<br />
|}<br />
<br />
== Xtion Live vs Xtion ==<br />
<br />
* '''ASUS Xtion Live''' is recommendable because it includes RGB sensor. RGB image is currently not used for tracking, but it helps to operate the system<br />
* '''Note:''' [http://www.asus.com/Multimedia/Motion_Sensor/Xtion_PRO/ ASUS Xtion] and [http://www.asus.com/Multimedia/Motion_Sensor/Xtion_PRO_LIVE/ ASUS Xtion Live] are also available in PRO modification (for developers). But the hardware is the same for regular and PRO versions, the only difference is in the software supplied with the device, that you will not need for use with [[iPi Mocap Studio|iPi Motion Capture system]]<br />
<br />
== Kinect for Xbox vs Kinect for Windows ==<br />
<br />
* If you plan to use [http://en.wikipedia.org/wiki/Kinect Kinect] not only with [[iPi Mocap Studio|iPi Motion Capture]], but also to have fun with Xbox games, then you definitely need '''Kinect for Xbox'''<br />
* But if [[iPi Mocap Studio|iPi Motion Capture]] is all you need [http://en.wikipedia.org/wiki/Kinect Kinect] for, then '''Kinect for Windows''' has a couple of advantages over Kinect for Xbox<br />
** Kinect for Windows is officially licensed (by Microsoft) for commercial use (unlike Kinect for Xbox which is only licensed for personal gaming)<br />
** Since it is officially allowed to use with Windows, we may hope that drivers quality and support will be better<br />
** It has capability to track at low distance (from 40 cm). This is not useful for full-body motion capture, but may be helpful for other applications</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2012-11-23T12:25:18Z<p>Mini: /* Valve Source Filmmaker and DMX */</p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|350px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|350px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|500px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|200px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters.<br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
* [http://www.youtube.com/watch?v=IP6AwFNkmm8 Humanik Maya 2012 Part 6]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX.<br />
<br />
=== Valve Source Filmmaker and DMX ===<br />
<br />
First, you need to import your character (or its skeleton) into iPi Mocap Studio, for motion transfer.<br />
<br />
There are currently 3 ways of doing this:<br />
<br />
# You can import an animation DMX (in default pose) into iPi Mocap Studio. Since it has a skeleton, it should be enough for motion transfer. To create an animation DMX with default pose, you can add your character to your scene in Source Filmmaker and export DMX for corresponding animation node:<br />
#* open "Animation Set Editor Tab";<br />
#* click "+" -> "Create Animation Set for New Model";<br />
#* choose a model and click "Open";<br />
#* export animation for your model, in ASCII DMX format;<br />
# Alternatively, you can just import an SMD file with your character into iPi Mocap Studio. For example, SMD files for all Team Fortress 2 characters can be found in your SDK in a location similar to the following (you need to have Source SDK installed): C:\Program Files (x86)\Steam\steamapps\<your steam name>\sourcesdk_content\tf\modelsrc\player\pyro\parts\smd\pyro_model.smd).<br />
# If you created a custom character in Maya, you should be able to export it in DMX model fromat. (Please see Valve documentation on how to do this).<br />
<br />
Then you can import your model DMX into iPi Mocap Studio. Current version of iPi Mocap Studio cannot display character skin, but it should display the skeleton. Skeleton should be enough for motion transfer.<br />
<br />
To export animation in DMX, you should just use "General..." export menu item in iPi Mocap Studio and choose DMX from the list of supported formats. You may also want to uncheck "Export T-pose in first frame" option on the "Export" tab in iPi Mocap Studio.<br />
<br />
Now you can import your animation into Source Filmmaker. There will be some warnings about missing channels for face bones but you can safely ignore them.<br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg|700px]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
[http://wiki.secondlife.com/wiki/How_to_create_animations#Setting_up_Poser SecondLife documentation] contains a link to useful [http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/avatar_mesh.zip SL avatar files]. The ZIP file includes a BVH of the "default pose". Be sure to have that.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk<br />
<br />
=== Source Filmmaker ===<br />
<br />
Please see the following video tutorial series on how to use iPi Motion Capture with [http://sourcefilmmaker.com/ Source Filmmaker]:<br />
<br />
http://www.youtube.com/playlist?list=PLD4409518E1F04270</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2012-11-23T12:24:46Z<p>Mini: /* Valve Source Filmmaker and DMX */</p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|350px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|350px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|500px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|200px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters.<br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
* [http://www.youtube.com/watch?v=IP6AwFNkmm8 Humanik Maya 2012 Part 6]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX.<br />
<br />
=== Valve Source Filmmaker and DMX ===<br />
<br />
First, you need to import your character (or its skeleton) into iPi Mocap Studio, for motion transfer.<br />
<br />
There are currently 3 ways of doing this:<br />
<br />
# You can import an animation DMX (in default pose) into iPi Mocap Studio. Since it has a skeleton, it should be enough for motion transfer. To create an animation DMX with default pose, you can add your character to your scene in Source Filmmaker and export DMX for corresponding animation node:<br />
#* open "Animation Set Editor Tab";<br />
#* click "+" -> "Create Animation Set for New Model";<br />
#* choose a model and click "Open";<br />
#* export animation for your model, in ASCII DMX format;<br />
# Alternatively, you can just import an SMD file with your character into iPi Mocap Studio. For example, SMD files for all Team Fortress 2 characters can be found in your SDK in a location similar to the following: C:\Program Files (x86)\Steam\steamapps\<your steam name>\sourcesdk_content\tf\modelsrc\player\pyro\parts\smd\pyro_model.smd).<br />
# If you created a custom character in Maya, you should be able to export it in DMX model fromat. (Please see Valve documentation on how to do this).<br />
<br />
Then you can import your model DMX into iPi Mocap Studio. Current version of iPi Mocap Studio cannot display character skin, but it should display the skeleton. Skeleton should be enough for motion transfer.<br />
<br />
To export animation in DMX, you should just use "General..." export menu item in iPi Mocap Studio and choose DMX from the list of supported formats. You may also want to uncheck "Export T-pose in first frame" option on the "Export" tab in iPi Mocap Studio.<br />
<br />
Now you can import your animation into Source Filmmaker. There will be some warnings about missing channels for face bones but you can safely ignore them.<br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg|700px]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
[http://wiki.secondlife.com/wiki/How_to_create_animations#Setting_up_Poser SecondLife documentation] contains a link to useful [http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/avatar_mesh.zip SL avatar files]. The ZIP file includes a BVH of the "default pose". Be sure to have that.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk<br />
<br />
=== Source Filmmaker ===<br />
<br />
Please see the following video tutorial series on how to use iPi Motion Capture with [http://sourcefilmmaker.com/ Source Filmmaker]:<br />
<br />
http://www.youtube.com/playlist?list=PLD4409518E1F04270</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2012-11-23T12:21:13Z<p>Mini: </p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|350px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|350px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|500px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|200px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters.<br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
* [http://www.youtube.com/watch?v=IP6AwFNkmm8 Humanik Maya 2012 Part 6]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|400px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|400px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|400px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|400px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|400px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX.<br />
<br />
=== Valve Source Filmmaker and DMX ===<br />
<br />
First, you need to import your character (or its skeleton) into iPi Mocap Studio, for motion transfer.<br />
<br />
There are currently 3 ways of doing this:<br />
<br />
# You can import an animation DMX (in default pose) into iPi Mocap Studio. Since it has a skeleton, it should be enough for motion transfer. To create an animation DMX with default pose, you can add your character to your scene in Source Film Maker and export DMX for corresponding animation node:<br />
#* open "Animation Set Editor Tab";<br />
#* click "+" -> "Create Animation Set for New Model";<br />
#* choose a model and click "Open";<br />
#* export animation for your model, in ASCII DMX format;<br />
# Alternatively, you can just import an SMD file with your character into iPi Mocap Studio. For example, SMD files for all Team Fortress 2 characters can be found in your SDK in a location similar to the following: C:\Program Files (x86)\Steam\steamapps\<your steam name>\sourcesdk_content\tf\modelsrc\player\pyro\parts\smd\pyro_model.smd).<br />
# If you created a custom character in Maya, you should be able to export it in DMX model fromat. (Please see Valve documentation on how to do this).<br />
<br />
Then you can import your model DMX into iPi Mocap Studio. Current version of iPi Mocap Studio cannot display character skin, but it should display the skeleton. Skeleton should be enough for motion transfer.<br />
<br />
To export animation in DMX, you should just use "General..." export menu item in iPi Mocap Studio and choose DMX from the list of supported formats. You may also want to uncheck "Export T-pose in first frame" option on the "Export" tab in iPi Mocap Studio.<br />
<br />
Now you can import your animation into Source Film Maker. There will be some warnings about missing channels for face bones but you can safely ignore them.<br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg|700px]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
[http://wiki.secondlife.com/wiki/How_to_create_animations#Setting_up_Poser SecondLife documentation] contains a link to useful [http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/avatar_mesh.zip SL avatar files]. The ZIP file includes a BVH of the "default pose". Be sure to have that.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk<br />
<br />
=== Source Filmmaker ===<br />
<br />
Please see the following video tutorial series on how to use iPi Motion Capture with [http://sourcefilmmaker.com/ Source Filmmaker]:<br />
<br />
http://www.youtube.com/playlist?list=PLD4409518E1F04270</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2012-05-04T20:54:48Z<p>Mini: /* Second Life */</p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|300px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|300px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|330px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|270px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|150px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters. <br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
* [http://www.youtube.com/watch?v=IP6AwFNkmm8 Humanik Maya 2012 Part 6]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX. <br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
Our user '''radiac''' published a tutorial about bringing animations to Blender (please note that this tutorial is a bit outdated as it does not take advantage of Blender-friendly export option): <br />
<br />
[http://www.ipisoft.com/forum/viewtopic.php?f=3&t=4748 Tutorial - iPi Export bvh-file in Blender]<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
[http://wiki.secondlife.com/wiki/How_to_create_animations#Setting_up_Poser SecondLife documentation] contains a link to useful [http://static-secondlife-com.s3.amazonaws.com/downloads/avatar/avatar_mesh.zip SL avatar files]. The ZIP file includes a BVH of the "default pose". Be sure to have that.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2012-05-03T20:59:13Z<p>Mini: </p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|300px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|300px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|330px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|270px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|150px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters. <br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
* [http://www.youtube.com/watch?v=IP6AwFNkmm8 Humanik Maya 2012 Part 6]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX. <br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
Our user '''radiac''' published a tutorial about bringing animations to Blender (please note that this tutorial is a bit outdated as it does not take advantage of Blender-friendly export option): <br />
<br />
[http://www.ipisoft.com/forum/viewtopic.php?f=3&t=4748 Tutorial - iPi Export bvh-file in Blender]<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2012-01-28T23:50:17Z<p>Mini: </p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|300px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|300px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|330px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|270px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|150px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters. <br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX. <br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
Our user '''radiac''' published a tutorial about bringing animations to Blender (please note that this tutorial is a bit outdated as it does not take advantage of Blender-friendly export option): <br />
<br />
[http://www.ipisoft.com/forum/viewtopic.php?f=3&t=4748 Tutorial - iPi Export bvh-file in Blender]<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU<br />
<br />
=== Jimmy|Rig Pro ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.origamidigital.com/typolight/index.php/home.html Jimmy|Rig Pro]:<br />
<br />
http://www.youtube.com/watch?v=wD1keDh3fCk</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2012-01-04T15:42:47Z<p>Mini: </p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
=== Default iPi Character Rig ===<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|300px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|300px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
=== Motion Transfer and Custom Rigs ===<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
=== MotionBuilder ===<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
=== 3D MAX Biped ===<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|330px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|270px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|150px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters. <br />
<br />
=== Maya ===<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
=== FBX ===<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
=== COLLADA ===<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
=== LightWave ===<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
=== SoftImage|XSI ===<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
=== Poser ===<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<br />
=== DAZ 3D ===<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== iClone ===<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Animeeple ===<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
=== Valve Source Engine SMD ===<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX. <br />
<br />
=== Blender ===<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
Our user '''radiac''' published a tutorial about bringing animations to Blender (please note that this tutorial is a bit outdated as it does not take advantage of Blender-friendly export option): <br />
<br />
[http://www.ipisoft.com/forum/viewtopic.php?f=3&t=4748 Tutorial - iPi Export bvh-file in Blender]<br />
<br />
=== Cinema4D ===<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
=== Evolver ===<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg]]<br />
<br />
=== Second Life ===<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
=== Massive ===<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233<br />
<br />
=== IKinema WebAnimate ===<br />
<br />
Please see the following video tutorial on how to use iPi Studio with [http://www.ikinema.com/webanimate IKinema WebAnimate]:<br />
<br />
http://www.youtube.com/watch?v=a-yJ-O02SLU</div>Minihttps://wiki.ipisoft.com/User_Guide_for_Multiple_PlayStation_Eye_Cameras_Configuration_(printable_version)User Guide for Multiple PlayStation Eye Cameras Configuration (printable version)2011-12-08T21:12:48Z<p>Mini: </p>
<hr />
<div>= Quick Start Guide =<br />
{{:Quick Start Guide}}<br />
<br />
= Cameras and accessories =<br />
{{:Cameras and accessories}}<br />
<br />
{{:USB controllers}}<br />
<br />
= Environment and actor clothing =<br />
{{:Environment and actor clothing}}<br />
<br />
= Video recording basics =<br />
{{:Video recording}}<br />
<br />
= Scene Setup =<br />
{{:Scene Setup}}<br />
<br />
= Calibration =<br />
{{:Calibration}}<br />
<br />
= Recording actor's performance =<br />
{{:Recording actor's performance}}<br />
<br />
= Processing video file in iPiStudio =<br />
{{:Processing video file in iPiStudio}}<br />
<br />
= Clean-up =<br />
{{:Clean-up}}<br />
<br />
= Animation export and motion transfer =<br />
{{:Animation export and motion transfer}}<br />
<br />
= Troubleshooting =<br />
{{:Troubleshooting}}</div>Minihttps://wiki.ipisoft.com/User_Guide_for_Single_Depth_Sensor_Configuration_(printable_version)User Guide for Single Depth Sensor Configuration (printable version)2011-12-08T21:11:11Z<p>Mini: </p>
<hr />
<div>== System Requirements ==<br />
* CPU: x86 compatible (Intel Pentium 4 or higher, AMD Athlon or higher), dual- or quad- core is preferable<br />
* Operating system: Windows 7 (x86 or x64), Windows Vista (x86 or x64), Windows XP SP3 (x86 or x64)<br />
* Video card: Direct3D 10-capable (Shader Model 4.0) gaming-class graphics card (GeForce GTS 250 or Radeon HD 4850 or better recommended)<br />
* Microsoft Kinect Sensor (“Depth Sensor”) with separate power adapter<br />
** ''If you bought "XBox 360 + Kinect" bundle then you need to [http://store.microsoft.com/microsoft/Kinect-Sensor-Power-Supply/product/9A4CFC08 order power adapter]''<br />
<br />
= Software installation (Express edition) =<br />
{{:Software installation (Express edition)}}<br />
<br />
= Recording a video from a depth sensor =<br />
{{:Recording a video from a depth sensor}}<br />
<br />
= Actor's performance =<br />
{{:Recording actor's performance}}<br />
<br />
= Processing a video from a depth sensor =<br />
{{:Processing a video from a depth sensor}}<br />
<br />
= Clean-up =<br />
{{:Clean-up}}<br />
<br />
= Animation export and motion transfer =<br />
{{:Animation export and motion transfer}}<br />
<br />
= Troubleshooting =<br />
{{:Troubleshooting}}</div>Minihttps://wiki.ipisoft.com/Recording_actor%27s_performanceRecording actor's performance2011-12-08T21:02:06Z<p>Mini: </p>
<hr />
<div>== Recommended layout of an action video ==<br />
<br />
* No actor at the start of the video<br />
* Enter the actor. <br />
* Strike a T-pose.<br />
* Action<br />
<br />
[[Image:No_actor.png|320px|Click to enlarge]][[Image:T-pose.png|320px|Click to enlarge]][[Image:Action.png|320px|Click to enlarge]]<br />
<br />
== “No actor at the start of the video” rule ==<br />
<br />
Remember to always record a few seconds without actor in view of cameras in the beginning of each video. This is very important. The software will need to see a couple of seconds of background of your scene (no actor) when processing the video. <br />
<br />
== T-pose ==<br />
<br />
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.<br />
<br />
== Takes ==<br />
<br />
[http://en.wikipedia.org/wiki/Take Take] is a concept originating from cinematography. In a nutshell, take is a single continuous recorded performance. <br />
<br />
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. <br />
<br />
== Iterations ==<br />
<br />
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. <br />
<br />
For this reason, you may need to schedule more than one motion capture session for the same motions. Recommended approach is:<br />
* Record the videos<br />
* Process the videos in iPiStudio <br />
* Import your target character into iPiStudio and review the resulting animation <br />
* Give feedback to the actor<br />
* Schedule another motion capture session if needed<br />
<br />
== Ian Chisholm's hints on motion capture ==<br />
<br />
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&t=5421 his motion capture guide] based on his experience with motion capture for Clear Skies III.<br />
<br />
=== Three handy hints for acting out mocap: ===<br />
<br />
# 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.<br />
<br />
# 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.<br />
<br />
# Stand a bit like a gorilla – have your arms out from your sides: <br> [[File:Gorilla.jpg]] <br> 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.<br />
<br />
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.<br />
<br />
=== Takes ===<br />
<br />
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.<br />
<br />
=== Naming conventions ===<br />
<br />
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.<br />
<br />
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.</div>Minihttps://wiki.ipisoft.com/File:Gorilla.jpgFile:Gorilla.jpg2011-12-08T20:57:52Z<p>Mini: </p>
<hr />
<div></div>Minihttps://wiki.ipisoft.com/Recording_actor%27s_performanceRecording actor's performance2011-12-08T20:57:22Z<p>Mini: </p>
<hr />
<div>== Recommended layout of an action video ==<br />
<br />
* No actor at the start of the video<br />
* Enter the actor. <br />
* Strike a T-pose.<br />
* Action<br />
<br />
[[Image:No_actor.png|320px|Click to enlarge]][[Image:T-pose.png|320px|Click to enlarge]][[Image:Action.png|320px|Click to enlarge]]<br />
<br />
== “No actor at the start of the video” rule ==<br />
<br />
Remember to always record a few seconds without actor in view of cameras in the beginning of each video. This is very important. The software will need to see a couple of seconds of background of your scene (no actor) when processing the video. <br />
<br />
== T-pose ==<br />
<br />
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.<br />
<br />
== Takes ==<br />
<br />
[http://en.wikipedia.org/wiki/Take Take] is a concept originating from cinematography. In a nutshell, take is a single continuous recorded performance. <br />
<br />
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. <br />
<br />
== Iterations ==<br />
<br />
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. <br />
<br />
For this reason, you may need to schedule more than one motion capture session for the same motions. Recommended approach is:<br />
* Record the videos<br />
* Process the videos in iPiStudio <br />
* Import your target character into iPiStudio and review the resulting animation <br />
* Give feedback to the actor<br />
* Schedule another motion capture session if needed<br />
<br />
== Ian Chisholm's hints on motion capture ==<br />
<br />
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&t=5421 his motion capture guide] based on his experience with motion capture for Clear Skies III.<br />
<br />
=== Three handy hints for acting out mocap: ===<br />
<br />
# 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.<br />
<br />
# 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.<br />
<br />
# Stand a bit like a gorilla – have your arms out from your sides: [[File:Gorilla.jpg]] 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.<br />
<br />
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.<br />
<br />
=== Takes ===<br />
<br />
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.<br />
<br />
=== Naming conventions ===<br />
<br />
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.<br />
<br />
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.</div>Minihttps://wiki.ipisoft.com/Recording_actor%27s_performanceRecording actor's performance2011-12-08T20:53:09Z<p>Mini: </p>
<hr />
<div>== Recommended layout of an action video ==<br />
<br />
* No actor at the start of the video<br />
* Enter the actor. <br />
* Strike a T-pose.<br />
* Action<br />
<br />
[[Image:No_actor.png|320px|Click to enlarge]][[Image:T-pose.png|320px|Click to enlarge]][[Image:Action.png|320px|Click to enlarge]]<br />
<br />
== “No actor at the start of the video” rule ==<br />
<br />
Remember to always record a few seconds without actor in view of cameras in the beginning of each video. This is very important. The software will need to see a couple of seconds of background of your scene (no actor) when processing the video. <br />
<br />
== T-pose ==<br />
<br />
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.<br />
<br />
== Takes ==<br />
<br />
[http://en.wikipedia.org/wiki/Take Take] is a concept originating from cinematography. In a nutshell, take is a single continuous recorded performance. <br />
<br />
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. <br />
<br />
== Iterations ==<br />
<br />
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. <br />
<br />
For this reason, you may need to schedule more than one motion capture session for the same motions. Recommended approach is:<br />
* Record the videos<br />
* Process the videos in iPiStudio <br />
* Import your target character into iPiStudio and review the resulting animation <br />
* Give feedback to the actor<br />
* Schedule another motion capture session if needed<br />
<br />
== Ian Chisholm's hints on motion capture ==<br />
<br />
Ian Chisholm is an acclaimed [http://en.wikipedia.org/wiki/Machinima machinima] director and actor and the creator of [http://www.clearskiesthemovie.com/ Clear Skies] machinima series. Below are some hints from his experience with motion capture for Clear Skies III.<br />
<br />
=== Three handy hints for acting out mocap: ===<br />
<br />
# 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.<br />
<br />
# 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.<br />
<br />
# Stand a bit like a gorilla – have your arms out from your sides: [[File:Gorilla.jpg]] 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.<br />
<br />
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.<br />
<br />
=== Takes ===<br />
<br />
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.<br />
<br />
=== Naming conventions ===<br />
<br />
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.<br />
<br />
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.</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2011-12-07T18:00:04Z<p>Mini: </p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
== Default iPi Character Rig ==<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|300px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|300px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
== Motion Transfer and Custom Rigs ==<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
== MotionBuilder ==<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
== 3D MAX Biped ==<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|330px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|270px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|150px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters. <br />
<br />
== Maya ==<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
== FBX ==<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
== COLLADA ==<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
== LightWave ==<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
== SoftImage|XSI ==<br />
<br />
Our user Eric Cosky published a tutorial on using iPiStudio with SoftImage|XSI:<br />
<br />
http://www.ipisoft.com/forum/viewtopic.php?f=13&p=9660#p9660<br />
<br />
== Poser ==<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<br />
== DAZ 3D ==<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
== iClone ==<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
== Animeeple ==<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
== Valve Source Engine SMD ==<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX. <br />
<br />
== Blender ==<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
Our user '''radiac''' published a tutorial about bringing animations to Blender (please note that this tutorial is a bit outdated as it does not take advantage of Blender-friendly export option): <br />
<br />
[http://www.ipisoft.com/forum/viewtopic.php?f=3&t=4748 Tutorial - iPi Export bvh-file in Blender]<br />
<br />
== Cinema4D ==<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
== Evolver ==<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg]]<br />
<br />
== Second Life ==<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
== Massive ==<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233</div>Minihttps://wiki.ipisoft.com/Animation_export_and_motion_transferAnimation export and motion transfer2011-12-07T15:29:59Z<p>Mini: </p>
<hr />
<div>Use “File->Export Animation” menu item to export all animation frames from within Region of Interest. <br />
<br />
To export animation for specific take, right-click on take and select “Export Animation” item from pop-up menu. <br />
<br />
== Default iPi Character Rig ==<br />
<br />
The default skeleton in iPi Studio is optimized for markerless motion capture. It may or may not be suitable as a skeleton for your character. Default iPi skeleton in T-pose has non-zero rotations for all joints. Please note that default iPi skeleton with zero rotations does not represent a meaningful pose and looks like a random pile of bones. <br />
<br />
<table border=0><tr><br />
<td>[[Image:default_rig.jpg|thumb|300px|Default rig]]</td><br />
<td>[[Image:default_rig_with_names.png|thumb|300px|Bone names]]</td><br />
</tr></table><br />
<br />
By default iPi Studio exports a T-pose (or a reasonable default pose for custom rig after motion transfer) in the first frame of animation. In case when it is not desired switch off "Export T-pose in first frame" checkbox.<br />
<br />
== Motion Transfer and Custom Rigs ==<br />
<br />
iPi Studio has integrated motion transfer technology. You can import your character into iPi Studio via “File->Import Target Character” menu item and your motion will be transferred to your character. You may need to assign bone mappings on the “Export” tab for motion transfer to work correctly. You can save your motion transfer profile to XML file for future use. iPi Studio has pre-configured motion transfer profiles for many popular rigs (see below). <br />
<br />
== MotionBuilder ==<br />
<br />
Use the “Export Animation for MotionBuilder” menu item to export your motion in MotionBuilder-friendly BVH format. MotionBuilder-friendly skeleton in T-pose has zero rotations for all joints, with bone names consistent with MotionBuilder conventions. This format may also be convenient for use with other apps like Blender. <br />
<br />
== 3D MAX Biped ==<br />
<br />
Use the “Export Animation for 3D MAX” menu item to export your motion in 3D MAX-friendly BVH format. <br />
<br />
Create a Biped character in 3D MAX (“Create->Systems->Biped”). Go to “Motion” tab. Click “Motion Capture” button and import your BVH file.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step1.png|thumb|330px|Step 1]]</td><br />
<td>[[Image:export_3dmax_step2.png|thumb|270px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_3dmax_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_3dmax_step4.png|thumb|150px|Step 4]]</td><br />
</tr></table><br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you work with Valve Source Engine characters. <br />
<br />
== Maya ==<br />
<br />
Latest versions of Maya (starting with Maya 2011) have a powerful biped animation subsystem called "HumanIK". Animations exported from iPiStudio in MotionBuilder-friendly format (the “Export Animation for MotionBuilder” menu item) should work fine with Maya 2011 and HumanIK. The following video tutorials can be helpful: <br />
<br />
* [http://www.youtube.com/watch?v=l1hV8BqsCEA Non-Destructive Live Retargeting — Maya 2011 New Features]<br />
* [http://vimeo.com/24351989 Motion Capture Workflow With Maya 2011]<br />
<br />
For older versions of Maya please see the [[#Motion Transfer and Custom Rigs]] section. Recommended format for import/export with older versions of Maya is FBX.<br />
<br />
== FBX ==<br />
<br />
iPi Studio supports FBX format for import/export of animations and characters. By default, iPiStudio exports animations in FBX 6.0 format using FBX SDK 2012. If your target character is in FBX 7.0 or newer format, iPiStudio will export retargeted animation in FBX 2012 format. <br />
<br />
Some applications do not use latest FBX SDK and may have problems importing newer version FBX files. In case of problems, your can use Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your animation file to appropriate FBX version. <br />
<br />
== COLLADA ==<br />
<br />
iPi Studio supports [http://collada.org COLLADA] format for import/export of animations and characters. Current version of iPi Studio exports COLLADA animations as matrices. In case if you encounter incompatibilities with other applications' implementation of COLLADA format, we recommend using Autodesk's free [http://usa.autodesk.com/adsk/servlet/pc/item?siteID=123112&id=10775855 FBX Converter] to convert your data between FBX and COLLADA formats. FBX is known to be more universally supported in many 3D graphics packages. <br />
<br />
== LightWave ==<br />
<br />
Recommended format for importing target characters from LightWave to iPi Studio is FBX. Recommended format for bringing animations from iPi Studio to LightWave is BVH or FBX. <br />
<br />
== Poser ==<br />
<br />
Export your poser character in T-pose in BVH format (File->Export). Import your Poser character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Poser character. Now you can use File->Export Animation to export your animation in BVH format for Poser.<br />
<br />
Poser 8 has a bug with incorrect wrists animation import. The bug can be reproduced as follows: export Poser 8 character in T-pose in BVH format; import your character back into Poser 8; note how wrists are twisted unnaturally as the result. <br />
<br />
A workaround for wrists bug is to chop off wrists from your Poser 8 skeleton (for instance using BVHacker) before importing Poser 8 target character into iPi Studio. Missing wrists should not cause any problems during motion transfer in iPi Studio if your BVH file is edited correctly. Poser will ignore missing wrists when importing resulting motion so the resulting motion will look right in Poser (wrists in default pose as expected).<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_poser_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_poser_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_poser_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_poser_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<br />
== DAZ 3D ==<br />
<br />
The workflow for DAZ 3D is very similar to Poser. Import your DAZ 3D character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your DAZ 3D character. Now you can use File->Export Animation to export your animation in BVH format for DAZ 3D.<br />
<br />
'''IMPORTANT''': You can use DAZ character in COLLADA (.dae) format for preview, but it is strongly recommended that you use DAZ character in BVH format for motion transfer. DAZ3D has a problem with COLLADA (.dae) format: DAZ3D Studio does not export all bones into COLLADA (.dae). In particular, the following bones are not exported: '''eyeBrow''', '''bodyMorphs'''. DAZ3D Studio does not use bone names when importing motions; instead, DAZ3D Studio just takes rotations from the list of angles as though it was a flat list with exactly the same positions as in DAZ3D internal skeleton. As the result, when you transfer the motion to a COLLADA character and import it back into DAZ3D, the motion will look wrong. iPiStudio displays a warning about this. To avoid this problem, import your DAZ target character in BVH format - DAZ3D Studio is known to export characters in BVH format correctly (with all bones).<br />
<br />
You can improve accuracy of motion transfer by doing some additional preparation of your DAZ 3D skeleton in BVH format. For DAZ 3D Michael 4.0 and similar characters, you may need to clamp thigh joint rotation to zero to avoid unnatural leg bending. For DAZ 3D Victoria 4.0, you may need to adjust foot joint rotation to change the default “high heels“ foot pose to a more natural foot pose. <br />
<br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_daz3d_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_daz3d_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_daz3d_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
== iClone ==<br />
<br />
Current version of iPi Studio can only export animation in iClone-compatible BVH format. The iMotion format is not supported as of yet. That means you will need iClone PRO to be able to import the motion into iClone. Standard and EX versions of iClone do not have BVH Converter and therefore cannot import BVH files. <br />
<br />
Workflow for iClone is straightforward. Export your animation using “Export Animation for iClone” menu item. Go to Animation tab in iClone and launch BVH Converter. Import your BVH file with Default profile, click “Convert” and save the resulting animation in iMotion format. Now your animation can be applied to iClone characters. <br />
<br />
iClone expects an animation sampled at 15 frames per seconds. For other frame rates, you may need to create a custom BVH Converter profile by copying Default profile and editing “Frame Rate” setting. <br />
<br />
BVH Converted in iClone 4 has a bug that causes distortion of legs animation. iPi Studio exports an iClone-optimized BVH correctly as can be verified by reviewing exported BVH motion in BVHacker or MotionBuilder or other third-party application. No workaround is known. We recommend that you contact iClone developers about this bug as it is out of control of iPi Soft.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_iclone_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_iclone_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_iclone_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
== Animeeple ==<br />
<br />
When importing motions into Animeeple, you may need to do the following adjustments:<br />
* Click “Set first frame” on the “TPose” tab in import dialog.<br />
* Assign bone mappings on the “Bones” tab:<br />
<center><table border="1"><br />
<tr><th>Segment</th><th>Bone</th></tr><br />
<tr><td>Hip</td><td>Hips</td></tr><br />
<tr><td>&nbsp;LowerSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;MiddleSpine</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;Chest</td><td>Torso</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;Neck</td><td>Neck</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head</td><td>Head</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;Head|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Clavicle</td><td>Collar</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Shoulder</td><td>Upper arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Forearm</td><td>Lower arm</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand</td><td>Hand</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Hand|Site</td><td>---</td></tr><br />
<tr><td>&nbsp;(R/L)Thigh</td><td>Upper leg</td></tr><br />
<tr><td>&nbsp;&nbsp;(R/L)Shin</td><td>Lower leg</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;(R/L)Foot</td><td>Foot</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe</td><td>Toe base</td></tr><br />
<tr><td>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;(R/L)Toe|Site</td><td>---</td></tr><br />
</table></center><br />
* Set the scale to 0.01 on the “Size” tab (by default, iPi Studio exports translations in centimeters for BVH files, while Animeeple expects translations in meters).<br />
* Set “Root position: Y:” to a correct value on the “TPose” tab, or click “Drop to floor”.<br />
<br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step1.png|thumb|300px|Step 1]]</td><br />
<td>[[Image:export_animeeple_step2.png|thumb|300px|Step 2]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step3.png|thumb|300px|Step 3]]</td><br />
<td>[[Image:export_animeeple_step4.png|thumb|300px|Step 4]]</td><br />
</tr></table><br />
<table border=0><tr><br />
<td>[[Image:export_animeeple_step5.png|thumb|300px|Step 5]]</td><br />
</tr></table><br />
<br />
== Valve Source Engine SMD ==<br />
<br />
Import .smd file for your Valve Source Engine character into iPi Studio via “File->Import Target Character” menu item. Your animation will be transferred to your character. Now you can use File->Export Animation to export your animation in Valve Source Engine SMD format.<br />
<br />
Our user '''Cra0kalo''' created an example [http://www.ipisoft.com/forum/viewtopic.php?f=2&t=4928 Valve Biped rig for use with 3D MAX]. It may be useful if you wish to apply more then one capture through MotionBuilder or edit the custom keyframes in MAX. <br />
<br />
== Blender ==<br />
<br />
iPiStudio can export animations in Blender-friendly BVH format (File->Export animation for Blender).<br />
<br />
Our user '''radiac''' published a tutorial about bringing animations to Blender (please note that this tutorial is a bit outdated as it does not take advantage of Blender-friendly export option): <br />
<br />
[http://www.ipisoft.com/forum/viewtopic.php?f=3&t=4748 Tutorial - iPi Export bvh-file in Blender]<br />
<br />
== Cinema4D ==<br />
<br />
If you have experience with Cinema4D please help to expand this Wiki by posting Cinema4D import/export tips to [http://www.ipisoft.com/forum/viewforum.php?f=3 Community Tutorials] section of our user forum. <br />
<br />
== Evolver ==<br />
<br />
iPi Studio supports importing of skinned [http://www.evolver.com Evolver] characters in COLLADA or FBX format. Import your Evolver character skeleton into iPi Studio (File->Import Target Character). Your animation will be retargeted to your Evolver character. Now you can use File->Export Animation to export your animation.<br />
<br />
Evolver offers several different skeletons for Evolver characters. Here is an example motion transfer profile for Evolver "Gaming" skeleton: [http://www.ipisoft.com/downloads/motion_transfer_profiles/evolver_game.profile.xml evolver_game.profile.xml]<br />
<br />
[[File:Evolver_example.jpg]]<br />
<br />
== Second Life ==<br />
<br />
Import your Second Life character skeleton into iPi Studio (File->Import Target Character). Your animation will be transferred to your Second Life character. Now you can use File->Export Animation to export your animation in BVH format for Second Life.<br />
<br />
See the discussion on our Forum for additional details: http://www.ipisoft.com/forum/viewtopic.php?f=2&p=7845<br />
<br />
== Massive ==<br />
<br />
Please see our user forum for a discussion of animation import/export for [http://www.massivesoftware.com/ Massive]: <br />
<br />
http://ipisoft.com/forum/viewtopic.php?f=12&t=3233</div>Minihttps://wiki.ipisoft.com/Video_recordingVideo recording2011-09-16T15:49:33Z<p>Mini: </p>
<hr />
<div>== iPiRecorder ==<br />
<br />
For multi-camera video, you should use Sony PlayStation Eye cameras (or other USB or Firewire cameras) and record a multi-camera video using iPiRecorder. Current release of iPi Desktop Motion Capture does not have other multi-camera options. <br />
<br />
iPiRecorder works with Sony PlayStation Eye cameras and DirectShow-compatible webcams (USB and FireWire).<br />
<br />
iPiRecorder is a stand-alone application and does not require a powerful video card. You may choose to install iPiRecorder on a notebook PC for portability. Since iPiRecorder is free, you can install it on as many computers as you need.<br />
<br />
== Framerate ==<br />
<br />
It is recommended that you record all videos at maximum available framerate. High framerate helps reduce motion blur and capture fine details of the motion. <br />
<br />
Maximum possible framerate for Sony PlayStation Eye camera is 60 frames per second. Sony advertises PlayStation Eye camera as capable of capturing at 120 frames per second but framerates over 60 FPS result in too much noise in PlayStation Eye camera sensor and are not usable for motion capture. <br />
<br />
Framerate lower than 30 frames per second is not recommended for motion capture.<br />
<br />
== 4 cameras at 320 by 240 resolution ==<br />
<br />
A dual-core CPU should be fast enough for recording a 4-camera video at 320 by 240 resolution at 60 frames per second.<br />
<br />
== 4 cameras at 640 by 480 resolution at 60 frames per second ==<br />
<br />
A quad-core CPU is recommended for recording at 640 by 480 resolution at 60 frames per second. If you have a dual-core CPU you may need to configure a lower framerate and/or lower compression quality to be able to record video at 640 by 480.<br />
<br />
== 6 cameras at 640 by 480 resolution at 60 frames per second ==<br />
<br />
A quad-core CPU clocked at 2.0 GHz (or better) is recommended for recording at 640 by 480 resolution at 60 frames per second. You will also need to get additional [[USB controllers|USB controller]]. <br />
<br />
== Raw Bayer Mode ==<br />
<br />
Sony PlayStation Eye camera supports special operation mode called “raw Bayer mode”. The name “raw Bayer mode” comes from the [http://en.wikipedia.org/wiki/Bayer_filter Bayer color filter array] used in PlayStation Eye camera (filter array being named after Eastman Kodak researcher Bryce E. Bayer).<br />
<br />
Raw Bayer mode is very efficient in terms of USB bandwidth usage and therefore is highly recommended.<br />
<br />
Videos captured in raw Bayer mode look like multiple monochrome image planes. This is normal. You should not have any problems opening raw Bayer mode videos in iPiStudio.<br />
<br />
== USB controllers == <br />
<br />
All modern computers (e.g. dual-core and better) based on Intel, AMD and Nvidia chipsets have two high-speed USB (USB 2.0) controllers on board. That should give you enough bandwidth to be able to record with 4 cameras at 640x480 (raw Bayer format) at 60 FPS, or 6 cameras at 640x480 (raw Bayer format) at 40 FPS. <br />
<br />
Under certain circumstances you may need to get additional [[USB controllers]].</div>Minihttps://wiki.ipisoft.com/Video_recordingVideo recording2011-09-16T15:48:55Z<p>Mini: </p>
<hr />
<div>== iPiRecorder ==<br />
<br />
For multi-camera video, you should use Sony PlayStation Eye cameras (or other USB or Firewire cameras) and record a multi-camera video using iPiRecorder. Current release of iPi Desktop Motion Capture does not have other multi-camera options. <br />
<br />
iPiRecorder works with Sony PlayStation Eye cameras and DirectShow-compatible webcams (USB and FireWire).<br />
<br />
iPiRecorder is a stand-alone application and does not require a powerful video card. You may choose to install iPiRecorder on a notebook PC for portability. Since iPiRecorder is free, you can install it on as many computers as you need.<br />
<br />
== Framerate ==<br />
<br />
It is recommended that you record all videos at maximum available framerate. High framerate helps reduce motion blur and capture fine details of the motion. <br />
<br />
Maximum possible framerate for Sony PlayStation Eye camera is 60 frames per second. Sony advertises PlayStation Eye camera as capable of capturing at 120 frames per second but framerates over 60 FPS result in too much noise in PlayStation Eye camera sensor and are not usable for motion capture. <br />
<br />
Framerate lower than 30 frames per second is not recommended for motion capture.<br />
<br />
== 4 cameras at 320 by 240 resolution ==<br />
<br />
A dual-core CPU should be fast enough for recording a 4-camera video at 320 by 240 resolution at 60 frames per second.<br />
<br />
== 4 cameras at 640 by 480 resolution at 60 frames per second ==<br />
<br />
A quad-core CPU is recommended for recording at 640 by 480 resolution at 60 frames per second. If you have a dual-core CPU you may need to configure a lower framerate and/or lower compression quality to be able to record video at 640 by 480.<br />
<br />
== 6 cameras at 640 by 480 resolution at 60 frames per second ==<br />
<br />
A quad-core CPU clocked at 3.0 GHz (or better) is recommended for recording at 640 by 480 resolution at 60 frames per second. You will also need to get additional [[USB controllers|USB controller]]. <br />
<br />
== Raw Bayer Mode ==<br />
<br />
Sony PlayStation Eye camera supports special operation mode called “raw Bayer mode”. The name “raw Bayer mode” comes from the [http://en.wikipedia.org/wiki/Bayer_filter Bayer color filter array] used in PlayStation Eye camera (filter array being named after Eastman Kodak researcher Bryce E. Bayer).<br />
<br />
Raw Bayer mode is very efficient in terms of USB bandwidth usage and therefore is highly recommended.<br />
<br />
Videos captured in raw Bayer mode look like multiple monochrome image planes. This is normal. You should not have any problems opening raw Bayer mode videos in iPiStudio.<br />
<br />
== USB controllers == <br />
<br />
All modern computers (e.g. dual-core and better) based on Intel, AMD and Nvidia chipsets have two high-speed USB (USB 2.0) controllers on board. That should give you enough bandwidth to be able to record with 4 cameras at 640x480 (raw Bayer format) at 60 FPS, or 6 cameras at 640x480 (raw Bayer format) at 40 FPS. <br />
<br />
Under certain circumstances you may need to get additional [[USB controllers]].</div>Minihttps://wiki.ipisoft.com/LicenseLicense2011-07-20T19:14:42Z<p>Mini: </p>
<hr />
<div><html><br />
<b>License activation</b><br />
<ul><br />
<li>We use online license activation system</li><br />
<li>After installing the software the system will ask you to activate the license. This is done only once.</li><br />
<li>The system is checking your hardware configuration. So if you need to move your license to another computer, please deactivate it on computer you're currently using, install the system on a new computer and activate the key again.</li><br />
<li>We also have option of offline activation for those who do not have live Internet connection.</li><br />
<li>If your computer is out of order and you cannot deactivate the license, please send us request for manual deactivation to our technical support service.</li><br />
</ul><br />
iPiStudio <b>Licensing Policy</b>:<br />
<ul><br />
<li> License is not transferrable to other person or company. So you should not give your license key to a friend, collegue or business partner.</li><br />
<li>One license should be used on one computer. If you need to have the system on several computers, we offer <a href="http://www.ipisoft.com/sales.php">volume discounts</a>.</li><br />
<li>Free trial can be used only once and only for 30 days. Setting computer clock to a point in time in the past or getting trial license to a different e-mail is a violation of license terms.<br />
<li>We reserve the right to ban license key if customer abuses license terms.</li><br />
<li>You can find detailed terms in EULA (End-User License Agreement) that comes with the software.</li><br />
</ul><br />
iPiRecorder <b>Licensing Policy</b>:<br />
<ul><br />
<li>iPiRecorder is a free application and you can run it on any number of computers.</li><br />
<li>See iPiRecorder EULA (End-User License Agreement) for details.</li><br />
</ul><br />
</html></div>Minihttps://wiki.ipisoft.com/LicenseLicense2011-07-20T16:22:47Z<p>Mini: </p>
<hr />
<div><html><br />
<b>License activation</b><br />
<ul><br />
<li>We use online license activation system</li><br />
<li>After installing the software the system will ask you to activate the license. This is done only once.</li><br />
<li>The system is checking your hardware configuration. So if you need to move your license to another computer, please deactivate it on computer you're currently using, install the system on a new computer and activate the key again.</li><br />
<li>We also have option of offline activation for those who do not have live Internet connection.</li><br />
<li>If your computer is out of order and you cannot deactivate the license, please send us request for manual deactivation to our technical support service.</li><br />
</ul><br />
Our <b>Licensing Policy</b> is:<br />
<ul><br />
<li> License is not transferrable to other person or company. So you should not give your license key to a friend, collegue or business partner.</li><br />
<li>One license should be used on one computer. If you need to have the system on several computers, we offer <a href="http://www.ipisoft.com/sales.php">volume discounts</a>.</li><br />
<li>Free trial can be used only once and only for 30 days. Setting computer clock to a point in time in the past or getting trial license to a different e-mail is a violation of license terms.<br />
<li>We reserve the right to ban license key if customer abuses license terms.</li><br />
<li>You can find detailed terms in EULA (End-User License Agreement) that comes with the software.</li><br />
</ul><br />
</html></div>Minihttps://wiki.ipisoft.com/LicenseLicense2011-07-20T16:20:14Z<p>Mini: </p>
<hr />
<div><html><br />
<b>License activation</b><br />
<ul><br />
<li>We use online license activation system</li><br />
<li>After installing the software the system will ask you to activate the license. This is done only once.</li><br />
<li>The system is checking your hardware configuration. So if you need to move your license to another computer, please deactivate it on computer you're currently using, install the system on a new computer and activate the key again.</li><br />
<li>We also have option of offline activation for those who do not have live Internet connection.</li><br />
<li>If your computer is out of order and you cannot deactivate the license, please send us request for manual deactivation to our technical support service.</li><br />
</ul><br />
Our <b>Licensing Policy</b> is:<br />
<ul><br />
<li> License is not transferrable to other person or company. So you should not give your license key to a friend, collegue or business partner.</li><br />
<li>One license should be used on one computer. If you need to have the system on sereral computers, we offer <a href="http://www.ipisoft.com/sales.php">volume discounts</a>.</li><br />
<li>Free trial can be used only once and only for 30 days. So changing computer clock or getting trial license to a different e-mail is not a good idea.<br />
<li>We have the right to ban license key if customer abuses license terms.</li><br />
<li>You can find detailed terms in EULA (End-User License Agreement) that is coming with the software.</li><br />
</ul><br />
</html></div>Minihttps://wiki.ipisoft.com/How-toHow-to2011-07-11T07:12:00Z<p>Mini: </p>
<hr />
<div>=== How do I change scene orientation? For example, what if I want my 3D character to stand in the coordinate system origin (0, 0, 0) and face Z-axis direction? ===<br />
<br />
Click the "Recenter Coordinate System on Character" button on "Scene" tab, or check the "Recenter coordinate system on character in first frame" option on "Export" tab.</div>Minihttps://wiki.ipisoft.com/How-toHow-to2011-07-11T07:09:38Z<p>Mini: Created page with '== How do I change scene orientation? For example, what if I want my 3D character to stand in the coordinate system origin (0, 0, 0) and face Z-axis direction? == Click the "Rec…'</p>
<hr />
<div>== How do I change scene orientation? For example, what if I want my 3D character to stand in the coordinate system origin (0, 0, 0) and face Z-axis direction? ==<br />
<br />
Click the "Recenter Coordinate System on Character" button on "Scene" tab, or check the "Recenter coordinate system on character in first frame" option on "Export" tab.</div>Minihttps://wiki.ipisoft.com/Main_PageMain Page2011-07-11T07:01:04Z<p>Mini: </p>
<hr />
<div><big>'''Welcome to iPi Soft Wiki!'''</big><br />
<br />
== General ==<br />
[[Gallery|Gallery of Demo Videos]]<br />
<br />
[[FAQ|Frequently Asked Questions]]<br />
<br />
[[Editions Comparison|Comparison of iPi MoCap Editions: Which Edition to Choose]]<br />
<br />
== iPi Desktop Motion Capture with MS Kinect Sensor ==<br />
<br />
[[Quick Start Guide with MS Kinect Sensor]]<br />
<br />
== iPi Desktop Motion Capture - Multi-camera Version - User Guide ==<br />
[[Quick Start Guide]]<br />
<br />
[[Cameras and accessories]]<br />
<br />
[[Environment and actor clothing]]<br />
<br />
[[Video recording]]<br />
<br />
[[Scene Setup]]<br />
<br />
[[Calibration]]<br />
<br />
[[Recording actor's performance]]<br />
<br />
[[Processing video file in iPiStudio]]<br />
<br />
[[Clean-up]]<br />
<br />
[[Animation export and motion transfer]]<br />
<br />
[[Troubleshooting]]<br />
<br />
== iPi Desktop Motion Capture - Reference ==<br />
<br />
[[iPiRecorder System Requirements]]<br />
<br />
[[iPiStudio System Requirements]]<br />
<br />
[[Single-camera (depth sensor/Kinect) Guide (printable version)]]<br />
<br />
[[Multi-camera Guide (printable version)]]<br />
<br />
[[How-to]]</div>Minihttps://wiki.ipisoft.com/User_Guide_for_Single_Depth_Sensor_Configuration_(printable_version)User Guide for Single Depth Sensor Configuration (printable version)2011-07-10T10:37:20Z<p>Mini: </p>
<hr />
<div>== System Requirements ==<br />
* CPU: x86 compatible (Intel Pentium 4 or higher, AMD Athlon or higher), dual- or quad- core is preferable<br />
* Operating system: Windows 7 (x86 or x64), Windows Vista (x86 or x64), Windows XP SP3 (x86 or x64)<br />
* Video card: Direct3D 10-capable (Shader Model 4.0) gaming-class graphics card (GeForce GTS 250 or Radeon HD 4850 or better recommended)<br />
* Microsoft Kinect Sensor (“Depth Sensor”) with separate power adapter<br />
** ''If you bought "XBox 360 + Kinect" bundle then you need to [http://store.microsoft.com/microsoft/Kinect-Sensor-Power-Supply/product/9A4CFC08 order power adapter]''<br />
<br />
= Software installation (Express edition) =<br />
{{:Software installation (Express edition)}}<br />
<br />
= Recording a video from a depth sensor =<br />
{{:Recording a video from a depth sensor}}<br />
<br />
= Processing a video from a depth sensor =<br />
{{:Processing a video from a depth sensor}}<br />
<br />
= Clean-up =<br />
{{:Clean-up}}<br />
<br />
= Animation export and motion transfer =<br />
{{:Animation export and motion transfer}}<br />
<br />
= Troubleshooting =<br />
{{:Troubleshooting}}</div>Minihttps://wiki.ipisoft.com/Software_installation_(Express_edition)Software installation (Express edition)2011-07-10T10:36:08Z<p>Mini: </p>
<hr />
<div>=== iPi Recorder ===<br />
::'''Note''' that even if you have used iPi Recorder before you will need to perform actions below anyway. Just letting iPi Recorder to be updated automatically will not work, because drivers for MS Kinect Sensor must be installed in addition.<br />
<br />
<br />
Before installation:<br />
* unplug MS Kinect Sensor from computer<br />
* deinstall libusb-win32 driver if it was used before (see http://ipisoft.com/forum/viewtopic.php?f=11&t=4932 for details)<br />
<br />
<br />
iPi Recorder is a tool for recording video from web cameras and depth sensors. Download the setup package of iPi Recorder latest version: http://ipisoft.com/downloads/iPiRecorderSetup.exe. Run it. In the following dialog window make sure that item “PrimeSensor Driver (psdrv3) Registration for MS Kinect Sensor” is selected:<br />
[[Image:PSensor-install-step1.png|center]]<br />
<br />
<br />
::'''Note''' that if you do not plan to use Sony PlayStation Eye cameras then you can deselect the appropriate item in the list.<br />
<br />
<br />
Click “Install” button to start the installation process. You’ll be asked about installation of “PrimeSensor Driver (psdrv3) Registration for MS Kinect”:<br />
[[Image:PSensor-install-step2.png|center]] <br />
<br />
Please read license agreement and accept it by checking the appropriate checkbox. Then press “Install” button. As soon as you get the Windows Security screen, please select “Install this driver software anyway”: <br />
[[Image:KSensor-install-step3.png|center]] <br />
<br />
At this point the driver will complete its installation and should not give any other errors:<br />
[[Image:PSensor-install-step4.png|center]] <br />
<br />
After that iPi Recorder itself will be installed:<br />
[[Image:KSensor-install-step5.png|center]]<br />
<br/><br />
[[Image:KSensor-install-step6.png|center]]<br />
<br />
<br />
After that, connect MS Kinect Sensor to your PC. Under Windows Vista and Windows 7 device initialization should be performed automatically and you’ll receive notification about it in the system tray area.<br />
Under Window XP you’ll be asked three times (for “Xbox NUI Motor”, “Xbox NUI Audio” and “Xbox NUI Camera”):<br />
* “Can Windows connect to Windows Update to search for software?”<br />
* “What do you want the wizard to do?”<br />
In all three cases answer “No, not this time” and “Install the software automatically (Recommended)” respectively:<br />
<table border=0><tr><br />
<td>[[Image:KSensor-install-step7.png|center|334px|Click to enlarge]]</td><br />
<td>[[Image:KSensor-install-step8.png|center|334px|Click to enlarge]]</td><br />
</tr></table><br />
<br />
<br />
Run iPi Recorder and make sure that there is “MS Kinect Sensor” in “Camera Selector” dialog:<br />
[[Image:PSensor-install-step9.png|center]] <br />
<br />
Select “MS Kinect Sensor (OpenNI)” and press “Ok” button. Make sure that you can see colored “depth video” from sensor, that actual frame rate is 30 fps, that frames drop is in range from 0 to 5 and that you can change motor position using appropriate slider:<br />
[[Image:KSensor-install-step10.png|center]] <br />
<br />
<br />
::'''Note''' that values of Tilt and Roll are updated with a time lag. During recording these values cannot be updated assuming that in this case sensor should be static.<br />
<br />
=== iPi Studio ===<br />
::'''Note''' that if you have used iPi Studio before and have Internet connection on your computer then you only need to let iPi Studio to automatically update:<br />
[[Image:IPiStudio-auto-update.png|center]] <br />
<br />
<br />
iPi Studio is a core software of iPi Desktop Motion Capture (iPi DMC) solution. It’s used to process pre-recorded video and export resulted animation into most popular formats. You can use 30 days free trial. <br />
To install iPi Studio please download and run setup program: http://ipisoft.com/downloads/iPiStudioSetup.exe. Then, follow instructions of the installation wizard.<br />
<br />
After successful installation iPi Studio will be launched. You will be prompted to activate 30-days free trial or enter a full license key.</div>Minihttps://wiki.ipisoft.com/Main_PageMain Page2011-07-10T10:31:58Z<p>Mini: </p>
<hr />
<div><big>'''Welcome to iPi Soft Wiki!'''</big><br />
<br />
== General ==<br />
[[Gallery|Gallery of Demo Videos]]<br />
<br />
[[FAQ|Frequently Asked Questions]]<br />
<br />
[[Editions Comparison|Comparison of iPi MoCap Editions: Which Edition to Choose]]<br />
<br />
== iPi Desktop Motion Capture with MS Kinect Sensor ==<br />
<br />
[[Quick Start Guide with MS Kinect Sensor]]<br />
<br />
== iPi Desktop Motion Capture - Multi-camera Version - User Guide ==<br />
[[Quick Start Guide]]<br />
<br />
[[Cameras and accessories]]<br />
<br />
[[Environment and actor clothing]]<br />
<br />
[[Video recording]]<br />
<br />
[[Scene Setup]]<br />
<br />
[[Calibration]]<br />
<br />
[[Recording actor's performance]]<br />
<br />
[[Processing video file in iPiStudio]]<br />
<br />
[[Clean-up]]<br />
<br />
[[Animation export and motion transfer]]<br />
<br />
[[Troubleshooting]]<br />
<br />
== iPi Desktop Motion Capture - Reference ==<br />
<br />
[[iPiRecorder System Requirements]]<br />
<br />
[[iPiStudio System Requirements]]<br />
<br />
[[Single-camera (depth sensor/Kinect) Guide (printable version)]]<br />
<br />
[[Multi-camera Guide (printable version)]]</div>Mini