[John Kirkilis]

Thanks. I tried to install the 2.3.2 version yesterday and it failed. I’ll try 2.3.7.

So, if I transcode to DNxHD, split the media manually in the Vegas timeline, and render these “sub-clips” individually into their own files in DNxHD, will Vegas’ smart-render kick in and not try to recompress the media?

I’d answer my own question now, but I’m away from my computer.

John

[John Kirkilis]

I have about 500GB of 1080/24p AVCHD footage to log and edit. Most of the footage consists of interviews for a documentary. During the shoot, each question was not isolated as its own AVCHD clip. In addition, the Sony HDR-AX2000 split the clips along 2GB boundaries. The AVCHD metadata supposedly takes care of these 2GB boundries in savvy NLEs. After each day of shooting, the entire AVCHD directory from the camera’s memory card was uploaded to its own directory on a hard disk.

For reasons too long to go into here, I will need the flexibility to edit/render portions in both FCPX and VP. Each NLE appears to have different AVCHD workflows without an ability to share metadata on clips/sub-clips. My thought was to use VP to go through the AVCHD footage and render out physical media files that align with individual interview questions in a format that retains the 1080/24p quality and which can be ingested into both FCPX and VP11.

I realize that this would be a time consuming extra step, but it would allow me to get intimately familiar with the footage and add a layer of old-school, lowest common denominator metadata using file system directories and filenaming. FCPX’s and VP11’s logging and keywording could then be separately applied on top of the newly minted media files.

My questions are:

* Which format should I use to render out these intermediate files so that both FCPX and VP11 can log, edit, and render most easily?

* Is VP the best tool to perform this first phase, or is there a dedicated utility that performs these simple cuts.

System specs in profile.

Regards,

John