Mocap workflows in Shotgun

Hello :shotgun: Community! Just wanted to start a thread here specific to motion capture / performance capture workflows in Shotgun. I’ve seen a lot of them over the years, ranging from simple and effective to deeply complex and powerful, to a little bit crazy. :wink:

We have some built-in entities and templates around this sort of work, but I wanted to get some feedback from the community about how different studios have approached this challenge. Here are some specific questions to start the discussion, feel free to answer any or all of them based on your experience:

  1. Which of the built-in Mocap entities in Shotgun do you use or not use? Any changes you would like to see there, or parts of the default setup you feel are missing?

  2. How have you abstracted the concept of Mocap Shots from VFX or Cinematic Shots? Or do you treat them as the same thing and just evolve them over time as edits change? And is there any overlap with the concept of script or storyboard “Scenes” there?

  3. What Tasks or file outputs do you not track in Shotgun? Anything that has proven to be more trouble than it is worth?

  4. Have you setup any sort of “Shopping Cart” or ordering functionality within, or integrated with, Shotgun, that you can share?

  5. Do you do a lot of prep work for a shoot in SG? Are you able to use SG data to generate collateral like call sheets fairly easily?

  6. Do you use Shotgun live on set during a shoot, for tracking director’s notes, circle takes, etc.? Anything else that comes in handy on shoot day?

  7. What is the handoff like when your work is done, to internal or external clients? Does much of your metadata travel downstream with the finished capture data?

  8. Does your metadata live in the same SG site or Project as the downstream consumers of the capture data? Or do you have your own separate SG site or Project?

As a side note, we do have a blog post from a few years back profiling Animatrik, and how they use Shotgun to facilitate their mocap work. Great read!

Thanks in advance for sharing any thoughts or feedback here. This will not only help new teams adoption Shotgun in the mocap space, but will give our Product and Design teams some great insight into how we can support this critical industry segment even better in the future.

7 Likes

Some really great questions here. Can someone point me to examples use cases of how shotgun is used on set for mocap?

5 Likes

Hi @forcestatus, thanks for chiming in! Unfortunately as you can see, we haven’t gotten much feedback since I posted this last year. :frowning: I’ll bump it today and see if we can get a little more community input.

As for using :shotgun: onset, I’ve see a few different applications. Most often I think, something else is used to capture data onset, and then it is synced to :shotgun: later through a script of some sort, or a manual CSV import. A studio I used to work at had a bar code system that they used with all physical assets/props that went into the volume. They would be scanned and associated with each Take they were used for, then all that data would get added to :shotgun: in a post-shoot ingest via an API script.

I’ve also worked with capture teams who had :shotgun: running on a touch-screen on set, and had their capture software live-update Take info in :shotgun: via a custom API connection. They could then mark circle takes and add notes directly in :shotgun:, as each Take would show up in :shotgun: as soon as the capture finished. They would also setup Shot lists and Shoot Days ahead of time, so they could actually print call sheets directly from a Shotgun page. Cool stuff. :slightly_smiling_face:

I’ve also heard of studios exploring integrations between :shotgun: and bespoke on-set apps like Setellite, though not sure if any of those talks ever came to fruition. (If you are a studio that has done something like this and care to share, please chime in!)

I hope that’s helpful! And again, if any other clients are reading this and care to share some info with the community, it would be most appreciated. :partying_face:

5 Likes

Hi tommy,
Thanks for starting off this conversation.
At the moment our workflow is very manual and involes spreadsheets and a lot of note taking on the day. We time sinc everything and have witness refrence cameras to match up to the mocap data shoot. All this gets collected at the end of the day, on a good day and gets processed in excel and quad views processed out of premiere pro.
On the mocap side we need to record who’s wearing what suit and which take was the circle take. Sometimes we can get upto 8 actors playing a bunch of background performers within the same scene.
I’m a bit vague on all the detais it myself as I’m not fully accross it and I’m new to the team.
But I’ve watched and helpled out and know shotgun can help with all this to help inprove their pipline.
Yes this was helpful & I’ll get the team to have a read.

2 Likes

Oh boy…I would LOVE to see how folks have built call sheets in SHOTGRID and exporting to PDF that would be sent to folks via traditional email.