Content Hub: Upload Instructions
Netflix Content Hub: https://contenthub.netflix.com/
Support Questions? Email: firstname.lastname@example.org
- Logging In
- Browsing My Projects
- Browsing Assets
- Fulfill Requests (DI, Sound, and Non-Distribution Masters)
- Bulk Upload Assets
- Asset States
If you already have a Backlot account, you will be able to access the Content Hub at the URL above. If you do not yet have a Backlot account, ask your Netflix contact to help you in setting one up.
Once you have a Backlot login, accessing the Content Hub should bring you to the main view, which lists the projects you have access to. If you do not see any links to Netflix projects at this page, work with your Netflix contact to get set up with access to your projects.
When clicking on a project, you should be taken to a screen like this, which shows a list of 'Buckets' and the assets that are contained in the Bucket:
A project is made up of Buckets, which are groupings of assets based on the production or post-production department creating assets. For example, the Footage bucket will contain all Dailies from a project, including web-playable proxies as well as Camera RAW, Sound Rolls, and LUTs.
List of Buckets
- Footage (API only)
- Dailies Bins
- Sound Materials
- Final Sound (Request-based Fulfillment)
- Picture Deliverables (DI assets) (Request-based Fulfillment)
- Non-Distribution Masters (Request-based Fulfillment)
Selecting an individual bucket will take you to the Asset browse page, which you can use to find assets and filter by certain bucket-specific criteria.
For a video tutorial of request fulfillment, click here.
1. When in a project, you can use the Bucket filter to filter on specific buckets.
2. Click the Final Sound header to open the request view.
3. You can use the filter bar to narrow down to the just requests you want to deliver.
4. Select the requests to deliver by clicking the checkbox on the left side of the table, then press the Upload Assets button on the right-hand side of the page.
5. This will direct to the Source Delivery UI, which you can drag and drop files to upload.
6. Drag and drop the files to upload onto the drop-zone at the top of the page.
7. Associate the uploaded files to a specific request by selecting it in the Files to deliver dropdown.
8. For some request types, you may need to fill out additional metadata. In this case (a feature film), select the Reel that each file is associated with.
9. By selecting the requests to deliver, then clicking the DELIVER button, the Aspera transfer will be initiated.
10. On a successful upload, you will be redirected back to the Content Hub.
Files can be archived with the Bulk Upload tool, which allows anyone to upload assets into the Content Hub from their desktop, via Aspera.
1. Drag and Drop files onto a bucket. In this case, dragging and dropping onto the Music bucket.
2. Tag files with the correct metadata and upload. NOTE: it is possible to edit the metadata for files in bulk by selecting multiple files and selecting Edit under the BULK ACTIONS menu.
Assets can be in the following states.
- Failed Delivery
- In Progress
- Valid - the file was successfully uploaded
If an Asset is the Valid state, then the asset has been uploaded into the Content Hub successfully:
Content Hub is currently supported on the Google Chrome browser only.
For best results, please upload H.264 video. The fast start flag must be set in order to provide playback in the Content Hub player. Your encoding software or NLE should be able to add the Fast Start flag. See below for an example `ffmpeg` command to add the fast start flag from the command line:
Debugging Aspera Transfers
Please follow the following steps if you get an error message while uploading:
1. Take a look at the transfer window to make sure that uploaded file names show up in transfer queue. If they are not present, it means that the Aspera transfer was not successful. Restart the browser and try the upload again.
2. If the Aspera transfer view shows failures, go to this help page to troubleshoot the Aspera Connect issue.
3. If you are not able to troubleshoot using steps 1 and 2, please email the support team with a screenshot of the error in Content Hub and all the Aspera connect logs.
How to see the Transfer view and Aspera connect logs:
Use this help page and follow the steps. To get the show view, go to Window -> Transfers in menu item of Aspera Connect app.
Frame sequences (DPX stacks, camera rolls for file-per-frame clips) should be placed into the ZIP Archive with a checksum.txt file that lists out all of the md5 checksum of the archive’s contents. The ZIP file should be a flat listing of files, and not include sub directories.
The checksum.txt manifest should be included inside the ZIP. The required format for the checksum.txt file is a tab-delimited file with the following columns:
filename size(bytes or blocks) md5(checksum type) md5checksum
Example of a frame sequence with 5 files:
-rw-r--r-- 1 amargoline staff 6 Jan 23 14:47 1.exr
-rw-r--r-- 1 amargoline staff 2 Jan 23 14:48 5.exr
-rw-r--r-- 1 amargoline staff 22 Jan 23 14:48 4.exr
-rw-r--r-- 1 amargoline staff 12 Jan 23 14:48 3.exr
-rw-r--r-- 1 amargoline staff 10 Jan 23 14:48 2.exr
From within the sequence folder, create a checksum.txt file by using the following set of instructions:
Download and save c.py script and make sure c.py is executable.
In a command shell, step inside the folder with frame sequences and run:
python ~/c.py . | sort > checksum.txt
You should now have the checksum.txt with the rest of the frames. Example of checksum.txt (note spaces are TABs):
1.exr 8 md5 09f7e02f1290be211da707a266f153b3
2.exr 8 md5 ac4434fc6e7bb238e0349e018f3c96bf
3.exr 8 md5 abc7dc6ca1883b025ecf25af68eaba79
4.exr 8 md5 865471defd1407d20b72ca1550547555
5.exr 8 md5 b026324c6904b2a9cb4b88d6d61c81d1
Create the ZIP from *outside* (one folder above) of the sequence folder, which has included checksum.txt
zip sequenceName.zip -rj -0 yourFolder -x "*.DS_Store"
The ZIP will have a checksum.txt and all frames from 1-5.exr:
unzip -l sequenceName.zip