Download Fast Mocap Free 3
Berry Spitsberg
My guess is the Character Object uses a rig that is slightly different in control scheme than the rig in the tutorial. Unfortunately I have little idea about how to proceed. At this point it may be quicker for me just to hand animate and use the mocap data I have as a reference. Is there a tutorial somewhere that explains the integration of mocap data with the Character Object rig? Any help is appreciated.
I have to see all these IK retargeting tutorials on Cineversity, but, would be great to have access to many diferent aproaches to mocap use on C4D.
Usually, one have to apply very fast solutions for some projects. ( other projects allow for more time )
An easy, fast and clear workflow for mocap animation on C4D, is a very important thing today.
Also, besides tutorials, would be great to have some additional materials available.
The creation or addition of new mocap rigs to the character object, would be great.
( maybe made available on Cineversity, even with an additional payment ? )
All this could be done without updating Cinema4D. Just by making some files available to the community,
maybe a script that prepares the file sizes, orientation, and maybe doing a tutorial applying
the mocap motion clips, and the IK animated ones ( maybe just baked ? ),
to show all this working togheter.
Motion capture animation (also known as mocap) is the process of tracking a real person's movements, transforming that movement into animation data, and then retargeting that data onto CG characters. Motion capture can be used to track a real actor's movements, do facial capture, and animate fingers. There are two main types of motion capture that you need to know about:
Optical motion capture is more suited towards hyper-realistic animated films, AAA game development or Hollywood-style feature films due to both higher requirements in mocap accuracy and large available budgets.
In most cases, retargeting the animation data to your character will require that your rig be compatible with the mocap suit. This compatibility is driven by the current industry standard of rigging and requires some IK joints.
The time it takes to clean up the data entirely depends on your system, personal preference, rig quality, and length of performance capture. Minor clipping or rotational issues can be caused by a difference in shape between your live actors and the character design. Animation corrections are usually made on top of the mocap data and require minimal effort. This video goes into more detail.
Most assets created by the motion capture industry are made with video games in mind. They tend to focus on looping actions for game characters like walk, jump, and various fighting stances. Depending on your project, it might be possible to find the pre-recorded animation you need. Click here to get 100 free motion capture assets when you download Rokoko Studio. One of the most interesting lessons from how the game industry uses motion capture animation is real-time previs. More and more motion capture studios have been using Unreal Engine to capture live performances for virtual production projects.
The videos shown below use the Rokoko Smartsuit Pro to record quality animation data and use it in their work as a creative agency. Looking to give motion capture a try? Our team of Product Specialists gives out free advice on nimation pipelines and will show you how Rokoko tools work in real-time over a zoom call. Book a free demo here.
World renowned creative studio Fustic.Studio has made a mark with its unique digital visual expressions. Read about their creative process and how they added Rokoko mocap tools to their workflows here.
Compact design for low profile integration.
Flex 3 cameras can be discreetly integrated into small installations, or allow you to optimize desktop capture volumes for tracking different types of objects.
OptiTrack systems are modular, reducing your initial investment in motion tracking technology. Start with a 6 camera bundle for under $7k, and as your tracking needs or budget expands, add more cameras or new software applications to increase the capabilities of your system.
Precision
Similar to Object processing, but sends selective grayscale images of markers to the PC for calculation of object data. Provides the most verbose marker information, but requires more CPU resources than Object processing.
MJPEG compression
Unique to OptiTrack cameras, on-camera MJPEG compression consumes 1/10th the bandwidth of uncompressed video while still enabling real-time grayscale video at full resolution and full frame rate.
It's more than just cameras. In addition to the essentials to which you've grown accustomed, you'll also discover several new software features that will make you wonder how you ever got along without them. Enjoy innovations like our Continuous Calibration, where a wand wave is required on first installation only, then calibrates automatically just by using the system. No longer does the calibration degrade over time, temperature change, or after cameras are bumped
Fast, precise, and efficient capture
The Flex 3 is capable of capturing fast moving objects with its global shutter imager and 100 FPS capture speed. By maximizing its 640 480 VGA resolution through advanced image processing algorithms, the Flex 3 can track markers with repeatable accuracy.
Interchangeable M12 lenses. The Flex 3 can be optimized for a variety of applications with custom-designed, interchangeable M12 lenses. Choose between 3.5mm and 4.5mm EFL lenses to adapt your cameras to your ideal capture volume. Both feature a special spring focus assist, very low distortion, and fast F#1.6 apertures for increased tracking distance. Typical applications utilize 3.5mm for capture volumes in smaller spaces, 4.5mm for larger capture volumes and camera counts.
Unobtrusive infrared light. Flex 3 cameras emit 850nm IR light, which is nearly invisible, for inconspicuous illumination that prevents the vision fatigue and unwanted attention to your capture rig caused by cameras that emit visible spectrum light.
OEM & computer vision Integration. Incorporate Flex 3 cameras into OEM tracking or computer vision applications via the free SDK, a C/C++ interface for control of and access to raw camera frames, image processing modes, camera settings, 2D object data, camera synchronization and all 3D data.
I am seeking assistance regarding the movie capture extension for my robotics application. My goal is to capture the real-time robot movements, but I have encountered significant variations in the results. Specifically, I have noticed that the simulation appears to run faster in the RTX-Real-Time video compared to the Path Tracing version.
What caught my attention is that the path-tracing version takes approximately 1 minute and 30 seconds to render, while the real-time version takes 7 minutes, both with 10,000 tsps. Could the path-tracing version be skipping physics steps?
Furthermore, I noticed that the Frame rate attribute only affects the encoding. As an example, I have captured the same scene as above using path-tracing for 50 frames, but with a frame rate of 60fps:
In this case, instead of observing half of the movements as expected, the simulation appears to be sped up (since only the encoding, not the simulation itself, is affected by the change in frame rate). Is this intentional?
Hi @axel.goedrich - The difference in simulation speed between the RTX-Real-Time and Path Tracing versions is likely due to the difference in computational complexity between the two rendering methods. Path Tracing is a more computationally intensive method that simulates the physical behavior of light, which can result in more realistic images but at the cost of longer rendering times. On the other hand, RTX-Real-Time rendering is optimized for speed and can produce high-quality images much faster, but it may not be as accurate in terms of light simulation.
If you want to capture the real-time movements of the robot, you might need to synchronize the simulation time with the video time. This could involve adjusting the simulation step size or the simulation speed to match the frame rate of the video. However, this can be a complex task that requires a good understanding of both the simulation and the video encoding process.
The difference in simulation speed between the RTX-Real-Time and Path Tracing versions is likely due to the difference in computational complexity between the two rendering methods. Path Tracing is a more computationally intensive method that simulates the physical behavior of light, which can result in more realistic images but at the cost of longer rendering times. On the other hand, RTX-Real-Time rendering is optimized for speed and can produce high-quality images much faster, but it may not be as accurate in terms of light simulation.
I get that for the viewport, but I was hoping that the Movie Capture-extension would step the simulation so that all physics steps are executed and the frame rate is the same as defined.
For example, if I set the simulation time steps per second (tsps) attribute to 1000 and the frame rate to 25, I would expect that the simulation would execute 40 physics steps, then one render update, another 40 physics steps, one render update, and so on. 25 frames should then equal one second of simulation time (just for clarification, the time that is passed in the simulation, not the time needed to calculate it).
If this were the case, the choice between path-tracing or rtx-realtime would only affect the look and rendering/calculation time to generate the video, not the simulation speed.
Interestingly, contrary to your description and my expectations, the video rendering was actually faster with path-tracing than with rtx-realtime. Maybe this is just a glitch caused by the high number of tsps (10000) and some skipping of physics steps:
7fc3f7cf58