-
Converting from H264 to ProRes resulting some small glitches
I shot all these footage from Canon 7D and converted all of it to pro res 422 HQ.
While editing the video, I across a few glitches in pro res files that I didn’t see in H264.
What’s the issue here?
-
5 Replies
-
How did you convert it?
-
Why transcode to ProRes 422HQ when 422 or 422 Proxy will give you smaller files. Remember that generic 422 is going to jump your file size 7-8x.
The glitches might be due to large files chewing up your CPU/GPU throughput.
Transcode one file which was giving you problems to 422 or 422 Proxy and see if the same glitches show up.
Did you back up all your original footage before transcoding? Hope so. Did you copy the entire folder contents from each card that came out of your camera and ingested into your external drive.
Jon Frost
meowmixmedia.net -
By using the compressor.
-
Of course I back up all of my footage. I follow the Murphy’s laws.
1. I copied the entire folder contents into my external HD. The contents are h.264 from CANON 7D. All the footage look clean.
2. I’ll try transcoding one file to 422 proxy. The reason why I converted them is someone suggested that I should to make them editable in FCP.
-
Glad you are following best practice and copying the whole file structure on your CF cards from the 7D. If you are using FCP, you need to transcode using Apple ProRes 422 in any flavor you choose. This is going to make your files up to 8x larger than the original files. ProRes422 is very edit friendly. Just send your original H.264 files through Log and Transfer using ProRes 422 and you will hopefully not have any artifacts. Let me know how this works for you.
Jon Frost
Reply to this Discussion! Login or Sign Up