Double-system audio recordings go into a SOUND folder for that date and follow this same hierarchy for sound rolls. Media is located within the roll subfolder. Within the footage folder, my subfolder hierarchy becomes shoot date (MMDDYY), then camera (A-CAM, B-CAM, etc), and then camera roll (A001, A002, etc).
This means ripping media files out of their various camera subfolders. Since video cameras don’t use a standard folder structure on the cards, the next step is to reorganize the copied media in the footage folder according to date, camera, and roll. The back-up drives should be stored in a safe location on-premises or better yet, offsite. Once we have at least two copies of the media, these working SSDs can be reformatted for the next production. Theoretically, this is for a deep archive, which hopefully will never be needed.
#Post haste def portable
Once my copy is complete, those same SSDs are separately copied “as is” via Hedge to one or more Western Digital or Seagate portable drives. The first step is to copy that media “as is” into the source footage subfolder for that project on the editing RAID or NAS. I receive those SSDs and not the camera cards. Hedge is used to copy the cards, in order to provide checksum copy verification. Someone on location (DIT, producer, DP, other) has copied the camera cards to working SSDs, which will be reused on later productions. That’s often from two or three cameras, recorded in a variety of codecs at 4K/UHD resolution and 23.98fps. Most of the location shoots for my projects come back to me with around 1TB of media for a day’s worth of filming. The first thing you have to deal with on a new project is the source media. Typically, the master folder (and Premiere project) for a new job created through Post Haste will be labelled according to this schema: 9999_CLIENT_PROJECT_DATE.ĭealing with source footage, aka rushes or dailies.
#Post haste def pro
The same name is applied to the Premiere Pro project file. In order to track productions, each job is assigned a number, which becomes part of the name structure assigned within Post Haste. When each new set of folders is created, this Premiere file is also copied. A template Premiere Pro project file with my custom bin structure is contained within the Post Haste template. Using this template, Post Haste generates a new project folder with common subfolders. This provides a common starting point for each new project based on a template that I’ve created. Post Haste uses default or custom templates that can include Adobe project files. I use Post Haste to create a new set of project folders for each new project. That’s a main folder for the job, with subfolders for the edit project files, footage, audio, graphics, documents, exports, etc. Regardless of your NLE, it’s a good idea to create a project “silo” for each job on your hard drive, RAID, or networked storage (NAS).
#Post haste def windows
I work on Macs, but there are Windows versions or alternatives for each. For a day-to-day workflow, I rely on five standard applications: Post Haste, Hedge, Better Rename, DiskCatalogMaker, and Kyno. Whether you work as a solo editor or part of a team, having a plan for organizing your projects – along with a workflow for moving media though your system – will lead to success in being able to find and restore material when needed at a future date. Leading into the new year, it’s time to take a fresh look at a perennial subject.
0 kommentar(er)
