Hello!
I've gotten i shot that has some parse metadata and dynamic focus, which I've linked in the clip input node. And I can see if thru the scene but it dosen't seem to get collected when I export the scene. Neither when I export it as a .fbx or .usd file. Is it possible to have that in the file so the 3d department can use the focus distance?
Hi there, I'm super happy we have a community place where we can get help! I have a couple of handheld shots where I have to track the camera as well as a moving object, and also then line up the objects as close as possible.
I've done the camera and object tracking already.
What's the best workflow for stabilizing the shots?
Aside for a few CG elements, I'm gonna do most of the post in Fusion. I have an idea how to chain Fusion's native tracking to track and stabilize. I'm not really clear on how to stabilize the PFT imported camera, but that's a question for another forum, however since I'm doing both camera and object tracking in PFTrack, it would be convenient if I could also stabilise there and get it out of the way.
Any tips would be appreciated.
Cheers!
Hi,
I've tracked a shot in PFTrack and need to export the result as an FBX to open in C4D.
The shot starts at frame 1955497 and ends at 1955582.
When I use the Scene Export node, the FBX exports without any problems. However, when I open the file, the only camera keyframe is at F0.
The trackers export correctly.
I’ve tried adjusting the Frame Offset in both the Scene Export node and C4D, but the camera keyframes still don’t appear.
Hello Henrique, welcome to the community!
It could be you’re running into a frame-time mismatch between PFTrack and Cinema 4D. The FBX format is time-based, meaning it relies on the frame rate to correctly convert frame numbers into time values during export and import. If PFTrack and C4D are using different frame rates, your camera keyframes might end up in the wrong place.
Here are some things you can do:
Check that both applications use the same frame rate. Make sure your PFTrack project and C4D scene are set to identical FPS values.
Inspect the scene attributes window in C4D. After importing the FBX, open the Scene Attributes and look at the Time Min/Max and Preview Min/Max fields to confirm the frame range matches your shot.
Set the correct frame offset before export. If you want your exported FBX to start at time = 0, set the frame offset in PFTrack to the negative of your first frame number (for example, if your shot starts at frame 1001, set the offset to -1001).
Hi! I've asked something close to this but I'm getting an error when I've solved a part of a 360 camera, and selected some frames to use with a "match camera" node. does the "match camera" node only work when the survey shot has gone thru the "photo survey" node? I'm getting a really good solve when solving it with a "camera solve" and not a not so good solve when using the "photo survey" node.
But i can't initialize the "match camera" node if I've solve the track with the regular "camera node". Only when it's been matched with the "photo survey" node
Match Camera uses a point cloud to match features of your footage, not another camera. It depends on what you want to achieve with it. You have to first solve your 360 Footage using Spherical track, and then extract a view that you want to "match" to a different camera to using Survey Solver. You have to enable "Already solved" in the second input within the Survey Solver node.
Hi Milko, welcome to the community!
There isn’t a way to stabilise the plate in PFTrack, and it’s usually best not to run a stabilisation at this stage either before tracking or after solving. Doing so can cause alignment issues later, especially with STMaps or 3D data, because stabilising effectively translates the pixels, moving both the centre of projection and the lens distortion on each frame creating inconsistencies.
So the best workflow is: track your camera and object in PFTrack, export to Fusion, and handle any plate stabilisation there. That keeps your tracking and distortion data clean and your comp flexible.
I’m pretty sure you can import 2D trackers as a .txt to lock or smooth motion in the compositing system but maybe other users familiar with Fusion will be able to help with that?