HDV looks great, but can be a bear in post production. HDV is typically not frame accurate, which makes batch capture difficult. HDV is also a long-GOP frame structure, which makes it CPU intensive and susceptible to rapid image degradation. Some workarounds:
Most intensive NLE applications are closely tied to the versions of various software installed on the machine. Typically this is at the OS level, but also can encompass such third party applications as Quicktime. This bottleneck can be remedied by creating a dual boot system – something developers have been doing for years.
The RED camera system has revolutionized the industry, however, with every revolution there are speed bumps. Decoding the REDCODE file (natively, or utilizing the camera generated wavelet proxy files) can be a lengthy process. A solution is to bring the bleeding edge down to cutting edge. Merge old with the new.
By following the diagram above, much of the data utilized in your RED filename can be deciphered by simply understanding the information contained within the filename. Many times, your NLE will simply parse the information found in the filename, and populate the appropraite columns in your Bin/Browser. This information can also be used if the link between the offline and online media is lost, and the files need to be located manually. Graphic Courtesy of avid.com
Current harddrives and storage solutions are available containing terrabytes of space. While the computer itself can support that much space, after 250+GB of storage has been taken up with media, the Avid begins to lose its way when dealing with Media DataBases.