Haha. Thanks for the comment. It's a good way to get consistent, non-planar information over to SynthEyes. It means less work on the other side too, when creating meshes or object tracks.
Thank you for the great tutorial! I found the section on adding 2D camera data to an already tracked scene a bit confusing, especially when it came to incorporating a moving object. I noticed there are Object001 and Object002, but I’m unsure which one I should click and drag the 2D camera data into. Additionally, if the 2D camera data isn’t associated with a moving object but is instead part of a wall or another static element, where should I drag the camera data? This might be obvious for professionals, but as a beginner, I feel like I’m running into numerous obstacles trying to figure it out.
Hopefully I can answer the question here. If it doesn't, then please consider joining our forum or Discord channel (www.borisfxdiscord.com/ ). To add those 2D trackers into your scene, use the Hierarchy view to click and drag them from the imported shot, into your original shot. You can then either delete or hide the empty shot. Now go back to the Solver and Refine or Solve with the new 2D trackers. This should give you the result you need.
There's a big gap from soft or out of focus footage, which can often be tracked with a slightly looser shape than normal, and real blurry footage caused by motion blur. One trick to this is to turn down the "Minimum % pixels used" parameter. This can help. If it is still producing a bad track, there is often no other option than to manually fix those bad frames and pick up the tracking when it's possible. This does sound like a great topic for a future tutorial though.
a new updated tutorial on 3d object tracking in syntheyes would be greatly appreciated. the old tutorials are impossible to understand.
Great suggestion. This is something we've got on our list. I'll pass your comment on.
I bought Syntheyes (best purchase ever) and now I’m working on acquiring Mocha Pro and Silhouette
Great to hear! Let us know if there's any specific tutorials or training we should be working on to help.
@@BorisFXco absolutely!
As a beginner, I can't even think of the benefits of doing this, but it seems like an amazing feature haha!
Haha. Thanks for the comment. It's a good way to get consistent, non-planar information over to SynthEyes. It means less work on the other side too, when creating meshes or object tracks.
Great Tip as always!
Glad you liked it! Thanks.
So the 2D power mesh data has become part of the 3D tracked camera solve in Synth eyes? thats extremly powerful
Exactly right.
@@BorisFXco wow! That's hugely exciting
Thank you for the great tutorial! I found the section on adding 2D camera data to an already tracked scene a bit confusing, especially when it came to incorporating a moving object. I noticed there are Object001 and Object002, but I’m unsure which one I should click and drag the 2D camera data into. Additionally, if the 2D camera data isn’t associated with a moving object but is instead part of a wall or another static element, where should I drag the camera data? This might be obvious for professionals, but as a beginner, I feel like I’m running into numerous obstacles trying to figure it out.
Hopefully I can answer the question here. If it doesn't, then please consider joining our forum or Discord channel (www.borisfxdiscord.com/ ). To add those 2D trackers into your scene, use the Hierarchy view to click and drag them from the imported shot, into your original shot. You can then either delete or hide the empty shot. Now go back to the Solver and Refine or Solve with the new 2D trackers. This should give you the result you need.
@@BorisFXco thank you! :)
insaneee!!!
Thank you!
What about extremely blurry footage, do you have tutorial for real blurry footage ?
There's a big gap from soft or out of focus footage, which can often be tracked with a slightly looser shape than normal, and real blurry footage caused by motion blur. One trick to this is to turn down the "Minimum % pixels used" parameter. This can help. If it is still producing a bad track, there is often no other option than to manually fix those bad frames and pick up the tracking when it's possible. This does sound like a great topic for a future tutorial though.
manyak bişi
🤪