-
GoPro Workflow problem
Hi,
I’m wondering if anyone can help me out with an AVID GoPro workflow problem. We’re working on a reality series in which there are a significant amount of GoPro’s running constantly (10+ gopros running 12 hours a day). Most of the footage is discarded unless some action happens on them in which case they get clipped out on set by the field producer/PA using Quicktime7 (in and outs marked, save as self contained movie – maintaining gopro h264 QT’s). The problem is that this seems to screw with the header and I-frames in the file (maybe?) and sometimes (50/50) gives us weird FPS values (shooting 25p but it gives us 23.9, 22.6 or even weird 656fps) and loses our TOD timecode. AMA Transcoding any of these weird framerate clips gives us unusable interpolation artefacts, however regular importing the clip does not but TOD is still lost. Importing takes at least twice as long as AMA and with the amount of gopro’s we use it would be a huge time saver in post if we could AMA transcode somehow.
We managed last season with these limitations, but really pushing for a solution before the next season starts. However, time and budget limit us from the simple solution of hiring an extra person to transcode, log and clip the gopro’s properly in post, it has to be done on location. I’ve been testing out AME, Cineform, Compressor but nothing seems to be able to do the quick truncating of a clip that quicktime does, they all want to re-encode the clip which takes too long on location and we’d rather have AVID do our only transcoding.
So it’s a fairly unique workflow but has anyone encountered this with their gopro files? Are there any other workarounds? preferably software that doesn’t mess with the fps? or a workaround in Avid. Any help would be greatful.
thanks,
Micah
Running Media Composer 6.5.0.1 but should get updated to 6.5.4 before next season starts.
Note: FCP and Ae both see the weird frame rates too.