From the course: Cinema 4D R23 Essential Training: VFX

Using the Full Solve command - CINEMA 4D Tutorial

From the course: Cinema 4D R23 Essential Training: VFX

Start my 1-month free trial

Using the Full Solve command

“

- [Tutor] In the chapters that follow we'll dive deeper into working with the motion tracker object. But before we do, I wanted to bring the full solve method to your attention. Now this is as automatic as it gets. We need to do, is come over to the tracker menu, click on full solve, and we'll load in some footage and C-4D will just get to work. So what's happening behind the scenes? Well, we've got a motion tracker object here, and the footage is loaded in and then automatic tracking takes place. And then the 3D camera reconstruction will be calculated and you can see in the lower left status bar, the progress that we're making and we're looking for the deferred sold finished message. You can see now that we have all these green circles and a few red ones, and these are the tracked features. So we can play through this now. We can see that most of those are sticking on to where they should be. I'm noticing some issues as well, and we'll get to those a bit later on. But for the most part, if we actually come out of this camera, you can see that we've got a 3D representation of this shot and all these auto features are, what we're looking at here. Let's come back into this camera now and we'll click onto the motion tracker. And if you're happy with this, you come over to the 3D solve tab, lock your data, and then you could start to work with the tracker tags to add constraints, to scale and orient the scene. So this full solve command definitely removes a few manual steps. And by the end of it, the hope is that you get a decent track camera. It's worth noting that you can use the full solve command even if you've done a few of the steps that I mentioned. If we'd already created a motion tracker and loaded in the footage, you could still use the full solve command to take over the 2D tracking and 3D solve commands. The full self command is a good way of getting an easily trackable shot solved quickly but just bear in mind, you may need to come back and do some manual adjusting to get the best result. Let's just look at some things that we didn't do. Just playing through this shot, I can see that we're tracking a moving object which is no good. There's also some track features way in the distance. A non-reflective surfaces that would likely remove through refining the solve. If we come over to edit and choose project settings, our frames per second is at 30. I know I shot this at 24 frames per second. So this won't match up if we were to composite some 3D onto the live action blade. For coming to our render settings, it's worked out the width and the height of the image, which is fine, but the framework is still at 30 here too. So keep in mind if you're using an image sequence, like we are here, we'd need to set the frames per second manually beforehand. And that's just something to be aware of for working on future shots. It's really important to analyze a shot before diving in tracking and we're going to be looking at that next.

Contents