Frame.io Process
We are now shifting from uploading our iterations from Google Drive to Frame.io. This is for us to provide feedback to the video editor and we can also use this to audit captions/subtitles.
Uploads
Upload RAW files in Frame.io (1.5 TB).
This will allow the project lead or Dennis to view the files easily and to check if the videos are complete or correct.
We still need to upload the RAW files to our google drive for backup which the assigned editor can do since they will have to download the RAW file for editing anyway.
File Management
Sort the folders per project. This will allow project leads to monitor tasks easily. We can organize it in this way
Project name Project tasks (micro course, why videos, how videos, what videos etc.), → RAW videos and edited videos
Version Management
Create Version Stacks to organize revisions of your clips rather than having multiple versions as individual files in your project.
See this for your reference
https://support.frame.io/en/articles/4431-version-stacking-and-comparison https://support.frame.io/en/articles/1110263-frame-io-webinars
Post Editing
Transfer all the final iterations to Google Drive
All RAW and edited videos should be deleted once the project is done to keep our frame.io storage at minimum. This is to be confirmed by Dennis or the project lead
Naming Convention before uploading in Google Drive
This should include the following:
Task name - to easily identify the content of the video
Date - to identify when the iteration was completed
Version Number - to identify the number of iterations.
Aspect ratio - this will somehow help us know what the video is for (FB, landing page, Ig, etc)
Eg:
Project name_iteration number_date_aspect ratio
Blitzacademy promo video_v1_07132020_16x9
Handling Local Businesses who purchased Packaged Bundle of Videos
Create a single to-do task in Basecamp
To speakers with several videos, create a sub-group to sort out their videos according to Why, How and What (no need to create a to-do thread for each videos)
Sort the videos in Frame.io according to the client/speaker’s Why, How and What.
All feedback will be placed in Frame.io for iteration
Once done, the final output will be uploaded in the project thread following our naming convention