Paul Jay
Forum Replies Created
-
Change the frame size in quicktime properties to 1024×576 and save.
-
Composting/Editing with H264 will give you loads of crap sooner or later.
I’ve seen H264 performance in CS5 and it’s pretty good, but you can do so much more with i-frame codecs. Even in Premiere.
I-frame codecs are far more reliable and give faster rendering in a production pipeline. -
Don’t ever let FCP scale down your footage. Just don’t.
Convert your HDV files in Compressor to SD ProRes.
Make sure you use Frame Controls. Resize filter to BEST.
This will work great in most cases. -
When you put 25 fps footage in a 30 frame timeline. FCP will create 5 new double frames every second.
This will look bad on moving things.
When you put 30 fps footage in a 25 frame timeline. FCP will remove 5 frames every second.
This will look bad on moving things.Jes Deinterlacer is a great free tool for standards conversion. It’s not always a miracle worker, but it’s a great tool.
If you still have a choice. Shoot and edit same framerates.
-
FCP 7.03 had lots of good bugfixes.
-
You’re shooting HDV interlaced and 5D progressive. That’s never an ABC 😉
-
Indeed. Editing ProRes HD will run fine on an iMac with a good FW800 drive, but grading on a glossy high contrasy iMac monitor is not recommended.
-
AJA rocks! They know service and support. They always do.
-
I had exactly your USB connecting problem. The calibrating software clearly says No Snow Leopard support.
But it does work great if you boot in 32 bit Snow Leopard. Hold 23 during boot.
After calibrating you can boot in 64 bit again.
-
When you test a harddrive system with the Decklink or AJA system test. it give you MB/s
When you do a Read/Write test with a Decklink or AJA system test it’s gives you MegaBytes/s
A 100 Mb/s video codec will need 12.5 MB/s datarate for one stream.
When you say my SATA raid does 300 Mb/s, you probably mean 300 MB/s.