Haha thanks Andy. My "recovery" has completed now that my facility installed 2024.5 today!! So excited to use it on real jobs and not just demo material!
Thanks! And that makes sense. I THINK if I'm not mistaken, if your PC and Mac are both using a centralized storage, and both are looking at the same project directory, then you can possibly set up the shot in Flame and then just open the SynthEyes project on the Windows machine, but that does take some somewhat specific setup. The User Manual talked about that use-case but yeah definitely simpler if you just do all in one on a Mac!
Hey Kyle, thanks a lot for all your videos! I’ve been learning Flame for about eight weeks now, and I’m curious why I should use SynthEyes instead of Flame’s 3D camera tracking. Also, I’ve noticed you use Mocha Pro frequently, and I’m still trying to understand why. So far, I’ve been fine using Flame’s 3D camera tracker, GMask Tracer, and motion vectors. Is there a reason I should consider using Boris FX tools instead? Am I missing out on something important? Thanks for your insights!
Thanks Moons! I’m having an awesome time making these videos. Great question! Simply put, it is another tool for the tool chest. Another option to add to the list of options. When one option fails, it’s important to be able to quickly adapt to another option, and for me, that’s where Mocha and SynthEyes fit in. Whether it’s the right tool to add for YOU depends on the kinds of shots you’re working on, the specific circumstances of those shots, as well as comfort level with the tools in question (and budget I suppose! But all the companies I’ve worked for have conveniently already had a subscription so that’s never been a thing for me fortunately) Regarding Mocha, since it is a dedicated tracking program with what I would argue is a proven history of impressive results, it is better than Flame’s planar tracker. Do I use it for all of my planar tracking? No. But if I know I have a shot where the planar tracking I need to do is not all that simple, based on my personal experience and comfort with Mocha (since I was using Mocha as a Flame Assistant before I was using Flame to work on shots) I will use Mocha. The big standout features for me are the general ease of use for setting up hold-out-mattes, the ability to track multiple masks at once, and the option to escalate to a mesh warp for deformation surfaces when you want to try to avoid motion vectors. Regarding SynthEyes, it is pretty obscenely fast. And with this new integration, the time it takes to send the shot to SynthEyes, do simple tracking, and get that data back into Flame is (depending on the resolution of your shot) most likely faster than it takes to calculate the motion vectors used in the Flame camera tracker. I was working on a job relatively recently where I needed to smooth out the camera in something like 25 shots. In the end, some shots Flame’s camera tracker worked perfectly. Others, it failed completely. On the shots Flame’s camera tracker failed, sometimes SynthEyes would have no issues whatsoever. On some shots, SynthEyes would fail and Flame’s camera tracker worked wonders. On some shots, both tools failed and I had to resort to other options. It’s another tool for the tool chest and the better you get at it, the more seamless it is to use.
@@JeffKyleFlame Oh wow, thanks so much for your comprehensive and detailed reply. This helps a lot, and now I understand why it makes sense. I guess I need to gain more experience with the possibilities and limitations of all these trackers and will try them out. Appreciate your insights, Kyle!
For sure! And yes! To be honest with you I have NOT been using it very long, but in the last year, it's turned into a really invaluable tool in the toolbox. This integration just makes it that much more useful with how quick it can be to get in and out.
@@vahegiragol9953 I know!! I did just made this tutorial so I'm not exactly unbiased but taking a step back I totally agree- it is super reasonably priced all around considering it's the industry standard.
HUGE update. Thanks for being so clear and thorough on the demos!
Agreed! It's huge!! Thanks for the kind words Jack 😄
Sold! Very nice, used the basic one added to mocha. This seems very nicely done. def going to give it a whirl.
Agreed! They really did a great job with it. Reach out if you have questions!
Game changing! 🎮
Yes sir! 🎉🥳
Agreed 🖱️
@@bvaccaro2959 Begun, the mouse wars have.
@@JeffKyleFlamenever underestimate the power of the Tablet……
Very nice Kyle. Hope your "recovery" is going on well. Thx for the nice tutorial.
Haha thanks Andy. My "recovery" has completed now that my facility installed 2024.5 today!! So excited to use it on real jobs and not just demo material!
That's awesome ! Now I need to start using SynthEyes on Mac more , I always run on PC because 3D software I use .
Thanks! And that makes sense. I THINK if I'm not mistaken, if your PC and Mac are both using a centralized storage, and both are looking at the same project directory, then you can possibly set up the shot in Flame and then just open the SynthEyes project on the Windows machine, but that does take some somewhat specific setup. The User Manual talked about that use-case but yeah definitely simpler if you just do all in one on a Mac!
Hey Kyle, thanks a lot for all your videos! I’ve been learning Flame for about eight weeks now, and I’m curious why I should use SynthEyes instead of Flame’s 3D camera tracking. Also, I’ve noticed you use Mocha Pro frequently, and I’m still trying to understand why. So far, I’ve been fine using Flame’s 3D camera tracker, GMask Tracer, and motion vectors. Is there a reason I should consider using Boris FX tools instead? Am I missing out on something important? Thanks for your insights!
Thanks Moons! I’m having an awesome time making these videos.
Great question! Simply put, it is another tool for the tool chest. Another option to add to the list of options. When one option fails, it’s important to be able to quickly adapt to another option, and for me, that’s where Mocha and SynthEyes fit in. Whether it’s the right tool to add for YOU depends on the kinds of shots you’re working on, the specific circumstances of those shots, as well as comfort level with the tools in question (and budget I suppose! But all the companies I’ve worked for have conveniently already had a subscription so that’s never been a thing for me fortunately)
Regarding Mocha, since it is a dedicated tracking program with what I would argue is a proven history of impressive results, it is better than Flame’s planar tracker. Do I use it for all of my planar tracking? No. But if I know I have a shot where the planar tracking I need to do is not all that simple, based on my personal experience and comfort with Mocha (since I was using Mocha as a Flame Assistant before I was using Flame to work on shots) I will use Mocha. The big standout features for me are the general ease of use for setting up hold-out-mattes, the ability to track multiple masks at once, and the option to escalate to a mesh warp for deformation surfaces when you want to try to avoid motion vectors.
Regarding SynthEyes, it is pretty obscenely fast. And with this new integration, the time it takes to send the shot to SynthEyes, do simple tracking, and get that data back into Flame is (depending on the resolution of your shot) most likely faster than it takes to calculate the motion vectors used in the Flame camera tracker. I was working on a job relatively recently where I needed to smooth out the camera in something like 25 shots. In the end, some shots Flame’s camera tracker worked perfectly. Others, it failed completely. On the shots Flame’s camera tracker failed, sometimes SynthEyes would have no issues whatsoever. On some shots, SynthEyes would fail and Flame’s camera tracker worked wonders. On some shots, both tools failed and I had to resort to other options. It’s another tool for the tool chest and the better you get at it, the more seamless it is to use.
@@JeffKyleFlame Oh wow, thanks so much for your comprehensive and detailed reply. This helps a lot, and now I understand why it makes sense. I guess I need to gain more experience with the possibilities and limitations of all these trackers and will try them out. Appreciate your insights, Kyle!
Great!!!! 👍👍👍👍
🎉🎉🎉
Thanks for the demo! Now i need to get syntheyes 😂
For sure! And yes! To be honest with you I have NOT been using it very long, but in the last year, it's turned into a really invaluable tool in the toolbox. This integration just makes it that much more useful with how quick it can be to get in and out.
@@JeffKyleFlame Absolutely. I was expecting sticker shock but it is very reasonably priced for a perpetual license as well!
@@vahegiragol9953 I know!! I did just made this tutorial so I'm not exactly unbiased but taking a step back I totally agree- it is super reasonably priced all around considering it's the industry standard.