{"id":109186,"date":"2023-07-11T09:32:40","date_gmt":"2023-07-11T16:32:40","guid":{"rendered":"https:\/\/www.backblaze.com\/blog\/?p=109186"},"modified":"2023-07-13T10:48:00","modified_gmt":"2023-07-13T17:48:00","slug":"free-your-premiere-pro-workflows-with-backblaze-cloud-storage","status":"publish","type":"post","link":"https:\/\/www.backblaze.com\/blog\/free-your-premiere-pro-workflows-with-backblaze-cloud-storage\/","title":{"rendered":"Free Your Premiere Pro Workflows With Backblaze Cloud Storage"},"content":{"rendered":"\n
\"A<\/figure>\n\n\n\n
<\/div>\n\n\n\n

Projects and technologies come and go, and with each new tool comes new workflow changes. But changing the way you move media around<\/a> can be tough. Maybe you\u2019ve always done things a certain way, and using a new tool feels like too much of a learning curve especially when you\u2019re pressed for time. But the way you\u2019ve always done things isn\u2019t always the best, easiest, or fastest way. Sometimes you need to change the status quo<\/a> to level up your media operations. <\/p>\n\n\n\n

As a freelance editor, I worked on a recent project that presented some challenges that demanded new approaches to media storage challenges you might also be facing. I solved them with the cloud\u2014but not an all-in-one cloud. My solution was a mix of cloud tools, including Adobe Premiere Pro<\/a>, which gives me customization and flexibility<\/a>\u2014the best of all worlds in media workflows<\/a>. <\/p>\n\n\n\n

Right Opportunity at the Right Time<\/h2>\n\n\n\n

Last year I had the opportunity to serve as a digital imaging technician (DIT) on the set of an indie film titled \u201cVengeance<\/a>\u201d produced by Falcon Pictures. The role of a DIT can vary. In many instances you\u2019re simply a data wrangler making backups of the data being shot. In others, you work in the color space of the project creating color corrected dailies on set. For \u201cVengeance\u201d, I was mostly data wrangling. <\/p>\n\n\n\n

\u201cVengeance\u201d was an 11-day shoot in the mountains of Northern California near Bass Lake. While the rest of the crew spent their days hiking around with equipment, I was stationed back at home base with my DIT cart. With a lot of free time, I found myself logging data as it came in. Logging clip names soon turned into organizing bins and prepping the project for editing. And, while I was not the editor on the project, I was happy to help edit while I was on set. <\/p>\n\n\n\n

The Challenge<\/h2>\n\n\n\n

A few months after my work as DIT ended, it became clear that \u201cVengeance\u201d needed a boost in post-production. The editing was a bit stuck\u2014they had no assistant editor to complete logging and to sound sync all the footage. So, I was asked to help out. The only problem: I needed to be able to share my work with another editor who lived 45 miles away.<\/p>\n\n\n

\n
\"A
Editing “Vengeance” in Adobe Premiere Pro.<\/figcaption><\/figure>\n<\/div>\n\n\n

Evaluating the World of Workflows and Cloud Tools<\/h2>\n\n\n\n

So we began to evaluate a few different solutions. It was clear that Adobe Premiere Pro would be used, but data storage was still a big question. We debated a few methods for sharing media:<\/p>\n\n\n\n

    \n
  1. The traditional route: <\/strong>Sharing a studio. With the other editor 45 miles away, commuting and scheduling time with each other was going to be cumbersome. <\/li>\n\n\n\n
  2. Email: <\/strong>We could email project files back and forth as we worked, but how would we keep track of versioning? Project bloat was a big concern. <\/li>\n\n\n\n
  3. Sharing a shuttle drive. <\/strong>Or what I\u2019m calling \u201cSneakernet<\/a> 2.0.\u201d This is a popular method, but far from efficient. <\/li>\n\n\n\n
  4. Google Drive or Dropbox: <\/strong>Another popular option, but also one that comes with costs and service limitations like rate limiting. <\/li>\n<\/ol>\n\n\n\n

    None of these options were great, so we went back to the drawing board. <\/p>\n\n\n\n

    The Solution: A Hybrid Workflow Designed for Our Needs<\/h2>\n\n\n\n

    To come to a final decision for this workflow, we made a list of our needs: <\/p>\n\n\n\n