Body.io Digicam to Cloud (C2C) is our model new, safe service that immediately connects your inventive groups and stakeholders to the cameras in your set, wherever on this planet they is perhaps. It removes legacy bottlenecks and optimizes your workflows in ways in which had been beforehand unattainable. And we’re simply getting began.
However earlier than we take a deep dive into what Body.io C2C presents, let’s check out a standard digital cinema workflow.
The previous approach
Conventional workflows are sequential. Which means step 2 can’t occur till step 1 is completed, and so forth. Let’s unpack that.
Day of manufacturing
On the set, the digicam information to digicam playing cards, that are despatched to the info or DIT cart. Sound is recorded concurrently to separate media, sometimes SSDs or SD playing cards, and these additionally head to the DIT cart. Whereas scenes are being shot, the script supervisor information efficiency notes and circle takes into their script report.
On the DIT cart, the digicam playing cards and SD playing cards from sound are offloaded utilizing a checksummed copy to an area RAID storage and a shuttle drive. The DIT additionally grades the picture out of the digicam for the cinematographer and the director, saving these grades as CDL recordsdata.
On the finish of the day, after the final digicam playing cards and SD playing cards are offloaded, the DIT provides their CDL recordsdata and knowledge studies to the shuttle drive. This drive and the paper digicam studies from the digicam staff are then handed off to a PA, who’s pushed to the dailies lab by a member of the transportation staff as soon as one is out there. The script supervisor then emails their script report back to the dailies lab and editorial as soon as it’s finalized.
In a single day
The dailies lab receives the shuttle drive from set and offloads the media to RAID storage. The drive contents are verified and manufacturing is notified if something is lacking from set. The dailies lab then begins syncing the footage based mostly on jam sync timecode and manually adjusting for drift or different jam sync points. And so they’ll additionally log the footage based mostly on the audio metadata, script studies, and digicam studies.
A dailies colorist then grades the footage based mostly on CDLs from set, balancing cameras and modifying the look additional. As soon as the colour is about, the dailies colorist pulls stills to ship to stakeholders.
Dailies for editorial and net evaluate are then transcoded from the unique digicam recordsdata to native storage. After transcoding, the dailies are inspected for accuracy and completion. And eventually, the dailies lab creates a bin for the editorial staff that incorporates the entire day’s dailies, organized by the specs supplied.
The subsequent day
On the finish of the dailies lab shift, which is early within the morning, the net dailies are uploaded to the net dailies platform and the editorial dailies are despatched to the editorial staff, normally utilizing a switch service like Aspera or MediaShuttle. The dailies lab additionally creates LTO tape archives of all of the digicam media, audio recordsdata, and picked up metadata.
Subsequent, the editorial staff receives the editorial dailies and dailies bins. The assistants undergo the dailies and carry out their very own QC, checking in opposition to the studies from the set and on the lookout for lacking scenes and takes.
As soon as every thing has been accounted for, the editorial staff releases the net dailies to a large group of recipients for evaluate. The editorial staff then begins organizing the footage, grouping cameras, and assembling scenes.
Lacking content material from the set is obtained by the dailies lab and processed accordingly. After processing is full, the lacking dailies are despatched to editorial and the net.
The brand new approach
Body.io C2C eases many of those inefficiencies by making most of the procedures parallel. Right here’s how.
Day of manufacturing
On the set, the digicam concurrently information to digicam playing cards and sends a video sign to a cloud-connected encoder field like a Teradek Dice. The encoder field receives scratch audio from the digicam or from a Comtek supplied by the sound mixer, and generates proxy recordsdata with digicam metadata because the digicam information.
As quickly because the digicam cuts, the proxy is uploaded to Body.io and is instantly accessible to view and obtain. Sound is recorded concurrently to a unique system like a Sound Units 8 sequence, which uploads WAV recordsdata to Body.io as they’re being written.
The second the recording stops, the editorial staff can obtain the proxies and might start organizing the footage, grouping cameras, and assembling scenes. Moreover, crew members not on set can watch takes as they’re being recorded. That is how Digicam to Cloud can elevate your workflow and what makes it a game-changer. Editorial groups now not want to attend till the subsequent day to start out their work. They’ll start reducing whereas the shoot remains to be occurring. Whereas Digicam to Cloud can dramatically improve your workflow, it additionally operates side-by-side to ensure you nonetheless have all of the assurances and safeguards you want and are used to.
The digicam playing cards are despatched to the DIT cart, together with the SD playing cards containing the sound recordsdata. Whereas scenes are being shot, the script supervisor information efficiency notes and circle takes into their script report.
As a result of they’ve entry to the recorded takes, editorial may give suggestions in realtime while manufacturing remains to be taking pictures, letting the staff know whether or not or not one thing has been captured. Different members of the crew, like producers, can even give suggestions in realtime. The on set crew can then seize and take motion on these notes earlier than the set or location is wrapped.
On the DIT cart, the digicam playing cards and SD playing cards from sound are offloaded utilizing a checksummed copy to native RAID storage and a shuttle drive. The DIT additionally grades the picture out of the digicam for the cinematographer and the director, and saves these grades as CDL recordsdata.
On the finish of the day, after the final digicam playing cards and SD playing cards are offloaded, the DIT additionally locations their CDL recordsdata and knowledge studies onto the shuttle drive. This drive and the paper digicam studies from the digicam staff are then handed off to a PA, who’s then both pushed to the dailies lab or ships the drive for in a single day supply. The script supervisor then emails their script report back to the dailies lab and editorial as soon as it’s finalized.
As soon as the editorial staff receives the script report, they’ll launch the proxy dailies with scratch audio to a bunch of recipients for evaluate.
In a single day
The dailies lab receives the shuttle drive from set and offloads the media to RAID storage. The contents are verified and manufacturing is notified if something is lacking from set. The dailies lab then begins syncing the footage based mostly on jam sync timecode and manually adjusting for drift or different jam sync points. And so they’ll additionally log the footage based mostly on the audio metadata, script studies, and digicam studies.
A dailies colorist then grades the footage based mostly on CDLs from set, balancing cameras and modifying the look additional. As soon as the colour is about, the dailies colorist pulls stills to ship to stakeholders.
Any “hero” dailies (ie, dailies with customized audio sync and a coloration cross) for editorial and net evaluate are then transcoded from the unique digicam recordsdata to native storage. After transcoding, the dailies are inspected for accuracy and completion. The dailies lab creates a bin for the editorial staff that incorporates the entire day’s dailies, organized by specs supplied by the editorial staff.
The subsequent day
On the finish of the dailies lab shift, which is early within the morning, the hero net dailies are uploaded to the net dailies platform and the hero editorial dailies are despatched to the editorial staff; on this case, they’ll each be uploaded to Body.io. If desired, the unique proxy dailies will be “versioned up” in Body.io to the hero dailies. This can seamlessly change them for the recipients. The dailies lab additionally creates LTO tape archives of all of the digicam media, audio recordsdata, and picked up metadata.
Subsequent, the editorial staff receives the hero editorial dailies and dailies bins. The hero dailies are relinked to the proxy dailies and are changed within the sequences created the day prior to this. Editorial can then work with footage coming in from set from the subsequent manufacturing day.
Additionally, as a result of Body.io helps it, the hero net dailies will be generated in HDR. So creatives and stakeholders can evaluate this content material in HDR on their cellular gadget, the day after taking pictures.
Any lacking content material from the set is obtained by the dailies lab and processed accordingly. As soon as processing is full, the lacking hero dailies are despatched to editorial and the net.
With a Body.io C2C workflow, editorial can transfer lots of their duties from the Subsequent Day to the Day of Manufacturing, which then permits dailies to be launched sooner and editorial to work extra shortly and extra precisely. Editorial’s suggestions additionally permits manufacturing to work extra effectively by avoiding reshoots and subsequent day pick-ups.
And right here’s what all of this seems to be like. (Purple is used to point processes that now happen earlier within the pipeline.)
How Body.io C2C Cloud Units work
Body.io C2C Cloud Units work by routinely importing new recordsdata immediately to Body.io. The second a brand new file turns into accessible, the gadget pushes it up right into a Body.io Challenge, utilizing easy, safe authorization to verify your recordsdata get there shortly and safely.
Earlier than we breakdown the on set workflow, let’s check out the way it’s constructed and the place every thing goes.
Setup
At a primary degree, there are two elements to a Body.io C2C workflow: {hardware} on set and Tasks on Body.io. A Body.io C2C Cloud Gadget on set both generates proxy recordsdata or takes unique recordsdata and uploads them into a chosen Body.io Challenge in your account by way of an web connection.
On set
Body.io C2C workflows begin on set, with {hardware} that connects on to a Challenge in your Body.io account. Body.io C2C Cloud Units will be paired by way of the Body.io iOS app by Workforce Managers and above.
As soon as linked, the {hardware} will routinely add recordsdata to the designated Challenge. This connection is made securely with a one-time pairing code displayed on the gadget display and entered into the Body.io iOS app by the consumer. Body.io checks the code and clears the gadget to add to the Challenge. The gadget can’t entry or do something in your Challenge or account aside from add recordsdata, which Body.io will routinely arrange.
Body.io C2C Cloud Units require an web connection to maneuver recordsdata to Body.io, and might want to both be linked to a WiFi community with web entry, or outfitted with an inner or exterior modem. This connection permits Body.io C2C Cloud Units to maintain anybody who’s not on set in sync with the manufacturing.
In conditions the place an web connection isn’t attainable the gadget can retailer the recordsdata regionally and routinely add them as soon as an web connection turns into accessible.
Ought to you should pause file transfers for any motive, you are able to do so individually or for all gadgets linked to a Challenge. Units will also be “forgotten” (requiring them to re-pair earlier than they’ll reconnect) with a single button push within the Body.io iOS app, and you may set an expiration date for gadgets.
As soon as set, the gadget can be faraway from the Challenge on the desired date and time.
Instance workflow
Right here’s what this seems to be like in a real-world instance.
A digicam on set sends a video sign over SDI to a Teradek Dice which has been linked to the designated Body.io Challenge by a licensed consumer on set (sometimes a member of the digicam staff or the DIT). When the digicam begins recording, it sends a begin flag by way of the SDI sign to the Dice, which responds by recording a proxy video file internally to the gadget.
The begin flag carries metadata, like clipname and timecode, which the Dice makes use of to make sure that the proxy has the identical filename and timecode because the in-camera clip.
As soon as stopped, the digicam sends a cease flag to the Dice, which then stops its personal recording and uploads it to Body.io.
Our sound is being recorded to a Sound Units 8 sequence, which uploads the unique WAVs on to Body.io after they’ve been saved.
On Body.io
On Body.io, Tasks in your account will be enabled as Body.io C2C Tasks after which paired with {hardware} on set. Solely Workforce Managers and above can flip this on (or off). As soon as enabled, and as soon as a tool is paired to the Challenge, recordsdata are written to a Cloud_Devices folder inside the Challenge. As soon as there, they are often considered, commented on, moved, copied, or shared similar to every other asset on Body.io.
In our workflow instance, our linked {hardware} uploads recordsdata to Body.io as quickly as they’re accessible, anybody with entry to the Body.io C2C Challenge can play these recordsdata again, anyplace on this planet, nearly instantly after “reduce” is named. No offloading, no transcoding, and any suggestions goes straight to the individuals on set.
In post-production
As soon as uploaded, recordsdata from Body.io C2C Cloud Units behave similar to every other asset on Body.io. This implies the edit-ready proxies will be downloaded utilizing the Frame.io Transfer App or imported immediately into your NLE by way of certainly one of our integrations.
In our instance workflow, which means an editorial staff can start importing proxies with scratch audio as quickly as they’re accessible. The Teradek Dice passes by way of the unique clipnames and timecodes, and because the Sound Units 8 sequence is importing the unique WAV recordsdata, these can each be imported immediately into the NLE. Which means these proxies will be relinked to each the unique digicam and sound recordsdata or greater high quality dailies later.
Instantly after wrapping a scene, the editorial staff can start reducing it. This enables them to provide sooner, extra actionable suggestions to the set, saving each money and time.
And because the proxies are viable dailies, productions can nonetheless course of the digicam and sound recordsdata by way of a standard dailies course of if customized coloration correction, geometry, framing, or refined sound sync is desired. The important thing distinction is that the editorial staff can now begin working a lot sooner, and, as a result of the Teradek passes by way of clipname and timecode, these newer dailies will be relinked to the Body.io C2C Cloud Units proxies at a later time, seamlessly, with out the editorial staff shedding any work.
Along with organizing, grouping, assembling, and reducing, the editorial staff can even start to filter by way of the proxies. Which means they’ll launch dailies to a distribution listing on the finish of the shoot day as an alternative of the subsequent morning. Creatives can go residence and see what they simply shot. These launched dailies will also be seamlessly “versioned up” to lab-produced dailies in a single day utilizing Frame.io’s Version Stacks.
How do I discover my recordsdata?
Body.io C2C workflows on Body.io will place your uploaded recordsdata in a dependable, anticipated Fastened Folder Construction, so that you’ll at all times know the place your recordsdata are going to be, even throughout manufacturing models. This folder construction is in a top-level folder in your Challenge, so it’s at all times simple to find and entry. However earlier than we break down the Fastened Folder Construction, let’s look at who in your account can entry Body.io C2C settings and recordsdata.
Body.io C2C Permissions
It’s essential to manage who can activate and off Body.io C2C entry and who can see Body.io C2C recordsdata. Right here’s a desk describing the totally different permission ranges on Body.io and what they’re allowed to do with Body.io C2C.
Collaborators
At present, Collaborators don’t have any Body.io C2C permissions. To let Collaborators see recordsdata from Body.io C2C Cloud Units within the Fastened Folder Construction, you’ll be able to both elevate them to Workforce Members or share the recordsdata by way of Overview Hyperlinks or Presentation Hyperlinks. Since Collaborators are sometimes distributors or exterior contributors to your manufacturing, it is sensible to dam them from probably delicate belongings.
Workforce Members
Workforce Members can see the Fastened Folder Construction, take motion on the belongings inside, and see what Body.io C2C Cloud Units are at present paired. Nonetheless, they’ll’t pair or overlook Body.io C2C Cloud Units or allow Body.io C2C Cloud Units workflows on a Challenge. Workforce Members ought to be a part of your inner staff and might sometimes be trusted to see recordsdata coming immediately from set, to allow them to share recordsdata to Collaborators by way of Overview Hyperlinks or Presentation Hyperlinks at their very own discretion.
Yow will discover out extra about Collaborators vs Workforce Members here
Workforce Managers
Workforce Managers and above (Admin and Account Proprietor) can pair or overlook particular person Body.io C2C Cloud Units in addition to pause or overlook all Body.io C2C Cloud Units. They’ll additionally allow or disable Body.io C2C Cloud Units workflows throughout a Challenge.
Nonetheless, since Admin and Account House owners have highly effective permissions on Body.io past Body.io C2C (like entry to billing, creating and modifying watermark templates, and staff creation), it’s endorsed crew members on set tasked with establishing Body.io C2C Cloud Units be given Workforce Supervisor permissions.
Fastened Folder Construction
Regardless of the title, the Body.io C2C Cloud Units Fastened Folder Construction permits your Body.io C2C Cloud Units workflows to be extra versatile.
Every Body.io C2C Cloud Gadget uploads into this construction, and Body.io makes positive every thing goes the place it belongs. As a result of the receiving folder construction is mounted, it permits you to have a number of several types of Body.io C2C Cloud Units (like sound and picture) and keep routinely organized on the similar time.
On the prime degree sits the mum or dad Cloud_Devices folder. This holds each uploaded file from all Body.io C2C Cloud Units and is created routinely when the primary file from a Body.io C2C Cloud Gadget is uploaded.
Contained in the Cloud_Devices folder, Body.io will create dated folders for brand spanking new uploads. The date relies on the timezone of the consumer who paired and authenticated the Body.io C2C Cloud Gadget. Body.io will then create a singular folder for every Body.io C2C Cloud Gadget that uploads throughout that date window. Every Body.io C2C Cloud Gadget will then add its recordsdata into that folder.
For instance, if there are a number of Teradek Cubes and one Sound Units 8 sequence recording on September 14th 2020, every of these gadgets could have a singular folder within the 2020_09_14 folder. If, nonetheless, on the subsequent day just one Teradek Dice and one Sound Units 8 sequence are getting used, then folders for less than these gadgets can be created. This enables the Body.io C2C Cloud Units storage location to be elastic and react to a specific day’s taking pictures setup and workflow.
A number of Taking pictures Items
Some productions could also be utilizing a number of taking pictures models and it could be troublesome to separate footage from one unit from the others. Moreover, some models might have totally different lists of customers with totally different entry. In these instances, your workflow will be separated into a number of Body.io C2C Tasks inside a Workforce, and even a number of Groups with further Tasks. This enables for even additional group and safety of content material coming from set.
Body.io Digicam to Cloud empowers filmmakers and content material creators with new methods of working and might dramatically enhance current workflows. From accessing your footage sooner to offering near-instant collaboration from distant crew members, to pushing the manufacturing cycle past yesterday’s obstacles, C2C retains your manufacturing on schedule, organized, and safe.
Body.io C2C is a big leap ahead for all of us. Body.io has at all times been the very best place to share your content material for evaluate and approval, however now you’ll be able to introduce all of those nice instruments into extra elements of your pipeline. We’re excited to listen to from the group about the way you’re utilizing C2C, and might’t wait to see what you create.
Body.io Digicam to Cloud will change into accessible in March 2021. In the meantime, you’ll be able to be taught extra and request early entry by way of our C2C beta program.
Leave a Reply