Different editing programs handle the long GOP MPEG-2 file format of HDV in different ways. The two main workflows today (and hopefully still in place by the time this magazine is printed and in your hands) consist of native HDV editing and non-native.

Native brings the long GOP I, B and P frames into the editing program unchanged. At this point, to cut in between most frames, a conversion process would have to take place. Some time after the cut and before output to tape, the GOP would have to be reconstructed (rendered). Though there is slight degradation of the image, proponents of native editing believe this to be the cleanest, not to mention quickest way to edit HDV footage. Only those GOPs that are altered need to be reconstructed at output.

Non-native HDV editing usually involves the use of an intermediary. The long GOP must be converted, or transcoded, into a group of I frames. Though a time consuming render is necessary when capturing footage and putting back out to tape, there is no interruption to the editing work flow during cutting, as all the frames are now all I frames, just as if it was DV footage. Some of the drawbacks here include the need for more hard drive space as the conversion from long GOP could take up to four times the space, generation loss on conversion and longer render time when capturing and outputting.

Of course, both camps claim their process produces both a better workflow and a better overall image.