User Questions on the MediaStorm Post-Production Workflow

Marius asks: I’ve previously bought your complete workflow and recently the Field Guide (so much good information guys!!). But I have a question. In the folder structure section you usually create an Z_Version folder and Z_Transcription. What do you put in these folders and why is it a Z? Let me begin by explaining the purpose of the version and transcription folders. At MediaStorm, we transcribe every interview. It’s the only way to make sure that no good bite gets left behind. It’s almost impossible to connect responses from the first minute of an interview with those spoken at the end unless they’re written down. So before we create a multi-camera sequence, we export an audio file of each interview for transcription. These audio files are exported to the Z_Transcription folder and can be deleted at the end of production as they won’t be used directly in the final project. The Z_Versions folder is used…

Continue ReadingUser Questions on the MediaStorm Post-Production Workflow

MediaStorm Introduces Asset Parser for Final Cut Pro 7 and Premiere Pro 6

  • Post author:

Today we are releasing our Asset Parser for public use. This free online tool created by the MediaStorm production and development staff generates a list of all image, video and audio files used in a project. When it's time to color correct photography, rather than scanning the timeline for image names, we use the Asset Parser to create a quick list. These file names can then be copy-and-pasted into Apple’s Aperture or a similar application to locate the necessary photographs. Here's an example of an asset list generated by the parser. In addition to speeding up your color correction workflow, this list can be used as a guide for other tasks, such as manually archiving your work. The Asset Parser works with both Final Cut Pro 7 and Premiere Pro 6. Try using the Asset Parser with your project at player.mediastorm.com/tools/asset-parser.

Continue ReadingMediaStorm Introduces Asset Parser for Final Cut Pro 7 and Premiere Pro 6

MediaStorm Guide to Final Cut Pro 7 Autosave Vault

Final Cut Pro’s Autosave Vault is your insurance policy against crashes, lost work and just about any other mishap. In short, it will save your bacon. The vault works by saving an entire copy of your Final Cut Pro project file at a regular, user-determined interval. This post will explain how to set up your Autosave Vault, copy items from a backup to your working project as well as replace your FCP file with a backup file. Setting Up the Autosave Vault From the Final Cut Pro menu choose System Settings (Shift-Q). Click the Autosave Vault: Set... button. Select a directory to save your backup files. It’s important to set your backups to a different drive than your actual assets. That way, if your media drive dies you still have access to these files. Next, from the Final Cut Pro menu choose User Preferences (Option-Q). On the General tab, check the Autosave…

Continue ReadingMediaStorm Guide to Final Cut Pro 7 Autosave Vault

Final Cut Pro X, it was good while it lasted.

This is the last in our series of MediaStorm producers responding to the new FCP X. If you missed them, you can check out Eric Maierson's thoughts here, and Tim McLaughlin's here. FCP X, it was good while it lasted. After working in FCP X for a week, I left on a Friday buoyed by the speed and efficiency at which the program runs. I had blazed through a weeks worth of work in just three days. But on Monday morning, my work was gone. I spent an hour on the phone with Apple. They asked me to run some tests. Several times I opened the project, made some changes, and closed it. Each time I reopened the file, it behaved differently. Think Memento. Sometimes the program “remembered” the changes correctly. Other times it reverted to a previously saved version. Other times it combined two previously saved versions to create a third!…

Continue ReadingFinal Cut Pro X, it was good while it lasted.

FCP X – Initial Reactions

This is the second in our series of MediaStorm producers responding to the new FCP X. If you missed the first response, from Eric Maierson, you can check that out here. Well it's amazing how much difference a day makes.  Yesterday I had prepared a blog post about my qualified, yet upbeat first impression of FCP X.  Of that blog post, here's what I'll include; "I've been working in FCP X since it launched, and I've tried to approach it for what it is. A new piece of software that will have significant limitations, like all version 1 software.  In doing this, I've come to see the potential of the program. It's a young buck, but as it matures, I think we're going to be surprised at how robust it is.  Using metadata to organize and find assets is amazing. It's fast and efficient. I've been able to organize content quicker than…

Continue ReadingFCP X – Initial Reactions