AMediaProf.com / VideoEducator. net

The GO-HD pocket HD camcorder from Aiptek is an interesting and convenient little camera.  Unfortunately, the video files that it outputs onto SD memory cards work well on Mac computers with iMovieHD but are difficult to handle on PC's.  The output files are QuickTime files compressed with h.264 compression and AAC audio.  While Sony's Vegas Pro 8 will read such files, the particular ones from this unit will actually crash the application.  

The files must be quickly prepared before using them in Vegas Pro 8. 

It appears that the problem with using the GO-HD files in Vegas Pro 8 is in the audio stream.  Aiptek has been unable to confirm if the audio stream is anything unusual or if the problem is in the way the file header is written.  The file header does not show a bitrate for the audio stream when examined in GSpot or Vegas Pro.  (UPDATE The audio files are AAC LC which Vegas does not like.  AAC LR is the more supported audio and acceptable to Vegas. )

Thankfully the workaround is quick. You simply use QuickTimePro which reads the file to rewrite the audio with a bitrate.  The file then works in Vegas Pro.  The process is actually very quick.

Step 1

Open the file in QuickTime Pro.  Go to File|Export and select Movie to MPEG-4 as the export type. 

 Click on the Options button.

Step 2

For Video Format, select Pass through.

In the box above Video Format, now pull down the list and select Audio. 

Step 3 

 For the Audio Format choose AAC-LC and leave the defaults.

Select OK and then save the new movie.  The file will now have an .mp4 extension and Vegas will find a bitrate for the audio and be happy. 

 I am guessing, but I bet that fixes it for other NLE's that handle AVCHD as well. 

The other consideration when using the GO_HD files in Vegas is the frame rate.  The GO_HD files are true 30fps.  Most project anf output templates for Vegas are the traditional 29.97 fps.  Since this is also progressive video, Vegas interprolates the frame rate to 29.97 and that results in ghosted images.  The key is simply making sure that you set your project properties to 30fps instead of the 29.97 and then make sure that you render our to 30 fps formats on the other end.  Keeping it at 30fps will give you the best results.  One note here, rendering to interlaced DV at 29.97 and showing it on an NTSC monitor looks fine.  It is not noticable until you are looking at it on a progressive monitor.