-
h264 causing indigestion
I have h264-encoded movs of videogame footage captured with a Hauppauge HD PVR. Final Cut 6 and 7 both refuse to ingest them, though QT Pro will open and play just fine. So I transcoded with QT Pro to ProRes (HQ), but Final Cut still will not recognize the file. Has anyone else encountered this, or found a workaround for it?
-
9 Replies
-
is there any copy protection on the streams? What is the comment FCP is giving you when you try to import the ProRes files.
-
Here’s the error message:
File Error: 1 file(s) recognized, 0 access denied, 1 unknown.
-
What frame size and frame rate did you conform to?
-
1280×720, 59.94
-
OK, weirdly enough if I transcode to ProRes but drop the framerate to 30 (native is 720p 59.94) the footage will now import to both FCP 6 and 7. this is not ideal as it adds an extra step to the workflow and forces me to work at 30 fps instead of 60, but its a start. any ideas why this is happening?
-
I dont see how it’s an extra step of you have to transcode anyway.
-
The only reason I’m transcoding is that importing in their native format is failing. Otherwise, I wouldn’t be going to ProRes or changing the framerate.
-
FCP won’t edit that version of h264 natively.
-
I’ve contacted the folks who make the software for comment… in the meantime I’ve discovered a workaround that doesn’t require transcoding.
I can put the file into a Motion project, and then import the Motion project to FCP with no problems. WTF?I’m really baffled as to why some Quicktime-based programs (QT Pro, Motion) have no trouble with these files but Final Cut is rejecting them. Aren’t they all based on the same architecture?
If I get any more useful bits from the makers, I’ll post them.
Reply to this Discussion! Login or Sign Up