Welcome to the Netflix Partner Help Center. Have a question or need help with an issue? Send us a ticket and we'll help you to a resolution.

TABLE OF CONTENTS

     Preparing The Folder Structure

     Uploading Footage to Workspaces

     Importing Footage

     Downloading a Report

Footage Backup allows a production to import production assets (Camera Rolls and Sound Roll) to Content Hub during the course of principal photography. We use the Asset Import Tool in Content Hub to import the assets. 

Any production wanting to opt into this workflow should consult with the production workflow specialist assigned to the project to ensure they’re fully informed of production requirements and tool capabilities. 

High Level Workflow Walkthrough

  1. Camera and sound rolls are offloaded and verified against the source on-set.
  2. Simultaneously MHLs per roll are created describing all files inside the original folder structure of each card and their  corresponding checksums.. 
  3. Camera and sound rolls are placed in the Netflix Recommended Folder Structure.
  4. All assets are uploaded to Content Hub workspaces. 
  5. Camera and sound rolls are imported into Content Hub and verified against the original MHL via the asset import tool for long term storage and use in other workflows. 

 

Preparing The Folder Structure

During this walkthrough we will be using the Netflix Recommended import profile on the asset import tool. The Netflix Recommended import profile uses the folder structure specified at the Production Assets: Folder and File Naming article on the Partner Help Center to be able to identify and correctly tag the camera and sound rolls in the files uploaded to workspaces. 

For this reason, it is very important that, before uploading the files to Content Hub Workspaces, the uploader ensures that the shoot day folder structure is organized using the Netflix recommended pattern. Organizing the assets in this way will minimize import errors during the import:

FootageBackup_folder.jpg

Figure A

Note: If your production folder structure has specific needs that differ from our Netflix Recommended folder structure please reach out to your production workflow specialist.

 

The below example matches our Netflix Recommended folder structure:

Folder_Structure_Green.png

Figure B

Reminder: Files on the camera card must not be changed. They must remain the same as they were on the actual camera and sound card. 

IMPORTANT: When following the Netflix Recommended folder structure, the Shoot Date format must match yyyyMMdd - if there are only 6 digits (yyMMdd) the Netflix Recommended import profile will not work.

IMPORTANT: When following the Netflix Recommended folder structure, the Asset Type folder is case-sensitive. Please use the following language exactly in bold: Camera_Media for Camera media, Sound_Media for Sound media. 

IMPORTANT: The MHL must be generated and placed inside the Camera/Sound roll folder on the destination drive at the offload stage. Example of correct MHL placement: 

Footage_Backup_1.png

Figure C

Uploading Footage to Workspaces

Log into Content Hub, navigate to your project, select the Workspaces tab, and click on the blue Upload button. A pop-up will appear where you can drag and drop, or select your files to upload.

Footage_Backup_3.gif
Figure D

This will kick off the upload via Aspera. After the files have completed uploading, you can check to ensure that all files were uploaded as intended. 

Footage_Backup_2.gif

Figure E

Importing Footage

Go to the Assets tab, select Source Materials, and click the blue Upload button at the bottom-right. 

Figure_F_NEW.gif

Figure F

Confirm that the correct Import Profile is selected. In this example we’ll select the default one  “Netflix Recommended” (located in the lower left drop down menu).  If a custom profile has been provided and you would like to set it as default on first load, please reference the Custom Default Import Profile User Guide.

Footage_Backup_5_Updated_Crop_Check.pngFootage_Backup_5_Updated_Shot_Crop_X.png

Figure G

Select the source folder you wish to import, the source folder is one level up from your shoot date and day folder.  Review the folders that you wish to import are checked, then click Review Import.

If the folder structure is correct, the correct source folder was selected, the MHL is correctly placed at the camera and sound roll level, and files match what is listed in the MHL; then, no error messages should appear, and you’ll see a list of all of the camera and sound rolls within that source folder. 

Click Import; the pop-up window will disappear and a confirmation message will pop-up on the bottom left corner.

Figure_H_NEW.gif

Figure H

A healthy, verified copy of your camera and sound rolls are now imported and safely stored in Content Hub.  Please confirm that your imported rolls match your workspace/local copy and that no rolls were missed on the import. You can do this by going to the Assets page, finding the day you imported and comparing the list of clips on the day against script and camera reports.

Footage_backup_7_Update.png

Figure I

Once you have confirmed that your footage has successfully imported navigate to Workspace. You can now move the imported day folders from the ‘SOURCE’ folder to an ‘IMPORTED’ folder. That way it will be easier for the user to identify what has already been imported and what is left to be imported. 

Footage_Backup_11.gif

Figure J

 

Downloading a Report

In addition you can download a report of all the imported footage that you can share with the rest of the production. After you’ve imported the desired Camera rolls, go to Footage Library / Camera Rolls.

Footage_Backup_8.gif

Figure K

Search for the three dots on the top right corner of the screen. And select Download Report (All)


Footage_Backup_9.gif

Figure L

Report example:

Report CSV

Screen Shot

Footage_Backup_10.png
Figure M

 

Bear in mind that currently, this is a report of the whole library. Downloading only a day is something not supported at this stage of the development.

RELATED RESOURCES

 

 

Was this article helpful?
0 out of 0 found this helpful
Powered by Zendesk