Adobe Prelude: Logging media

Once you’ve ingested your media into Prelude, you can finally get started on what is the bread and butter of Adobe Prelude: logging content. This stage of the process is about adding extra information (metadata) to your clips, ranging from a description of the content, to the camera angle that was used.This is all in the name of making your life easier when you look for clips when you put your edit together. There are two ways to log content in Prelude: File Metadata, and markers. If you’re considering using Prelude, chances are it’s for the marker logging feature. But before we look into it, let’s see how that information can be of use once in Premiere.


Adobe Prelude: Ingesting media

Once you’ve created a Prelude project and before you can do anything useful with it, you need to add some content to your project. This is called the Ingest stage. In the world of video production, ingesting media is a basically a fancy term for importing your files from your memory cards or external hard drive into your editing suite. When working with Adobe Prelude however, it deserves its fancy name as it becomes more than ever an involved stage in the pipeline.


Adobe Prelude: Introduction and ingest strategies

Back in July, after filming my first interview for Back to the Source, I realised that managing all those files would rapidly become a headache. I asked around if there was any software designed to manage dailies and someone told me to take a look at Adobe Prelude. And so I did. And I’m glad. It’s a young product, but Prelude is an invaluable tool to use before you start on post-production, especially when you work on a project that’s not entirely scripted, such as a documentary.

This is the start of a series of articles regarding the use of Adobe Prelude in my documentary project. This is not supposed to show the one true way of using Prelude, but rather describe the various steps involved in using the software, the pipeline questions that one might ask themselves and my personal answers to those questions. Screenshots might sometimes seem inconsistent with what I’m writing, but that’s because my pipeline is evolving as I learn more about Prelude and I’m not going back to refactor my test project every time.