For anyone interested I just put out a few new scripts for Mocha and Sammie Roto that auto imports the exports into Flame along with Logik Backdoor, a script that’s needed by both of these scripts to work.
With the Sammie Roto script options are added to the export video options to send renders to Flame after the export is done. Renders can be sent either to the current batch or into a library.
With the Mocha script, options are added to import the exported matte render, send the roto splines to batch as a gmask tracer node, or send power meshes as an Alembic file to an Action node in batch.
Both of these require that another new script called the Logik Backdoor to be installed and running. This should be installed first! This allows the scripts installed in either Mocha or Sammie Roto to “talk” to Flame to let it know what to import. The Logik Backdoor has “tools” that can be accessed by custom scripts to allow auto-importing from any app that allows for scripts to be executed on export along with a few other things.
The Mocha and Sammie Roto scripts have installers that have to be run to modify both apps. The Logik Backdoor script gets installed as a normal Flame Python script.
The Mocha and Sammie Roto scripts have only been tested on MacOS. They may or may not work on linux. The Mocha script works with both the OFX and Standalone versions of Mocha.
@MikeV!!! This is so cool! I can’t wait to try it out. I have been itching for something like this for a long time. Whenever I’m working on a job with tons of shots and I have to go into Mocha for each one, I think to myself: there has to be a better way. Surely we can script something to help. I half started a project like this a few times, but each time I walked away dismayed since it wasn’t too simple. I feel great knowing you tackled this. I’ll be putting this through its paces and I’ll let you know how it goes for me. Thanks so much as always.
Hey there Mike! I finally got to trying these all out today and wow! Fantastic on both fronts! The Sammie Roto integration was fantastic. I had to pump through tons and tons of mask creation for a film I’m grading where the Automatte didn’t cut it and this streamlined the workflow SIGNIFICANTLY. Super quick to get in and out and get through something like 20 shots in no time. Thanks a ton, no notes.
I tried out Mocha as well and it is equally mind blowing. I don’t use the rendered clips or shapes but I DO use the Data, and that working is an incredible incredible advancement in my day-to-day workflow. I can’t tell you how many seconds I’ve spent navigating file paths–once in Mocha to put it in the shot folder, and then again to pull it into Batch, navigating the same shot folders. This is wonderful.
I do believe I have found a bug for you though. Mocha Flame Export for the Gmask data- you can either choose the top 4 bubbles OR the bottom 2 bubbles, even though the two sets of options should be independent from one another. I wanted to pick Selected Layers AND Shape & Axis and one overwrites the other. Not a deal-breaker at all because if you don’t have a bubble selected it just falls back on bringing in all of the shapes which is also fine.
Okay, already back with a small laundry list of feature requests. Posted this after using Mocha on one shot, now that I’ve used it on 10 I have a few little things I want to add to the list if you’ll have them!
I use the Gmask export for 90% of my tracks, but 10% of the time I might need to use the Export Track Flame Point Stabilizer Data 2014. This is when I get a better track using Perspective, but a lot of the time turning on Perspective makes it so my Axes from a Gmask aren’t accurate anymore. Would be very much a nice to have to add that to the list of things in the button area.
I used a few Mesh tracker Alembic exports and I was missing the ability to specify the “Ref” frame if the one that was set up during tracking isn’t what you want.
…thanks…
