What is the speed of your processor? When rendering a project like yours, GPU doesn't have an effect.
You should be able to key the .MTS file without first transcoding to a .MOV.
When you have "render multiple frames" enabled and AE crashes, is there any specific error message that appears?
Your disk setup is not ideal, reading and writing to the same disk. Any reason why you partitioned the drive? Are you reading/writing to a single partition? Unless your external HDD is USB3.0 or eSATA, it's probably not fast enough to use.
The drive came partitioned when I got it.
When I do keying with the .MTS file it renders like 800 frames quickly then adobe pops up an error that keylight crashed and at this point begins to render them as if "render multiple frames" has been unchecked.. it just goes really slow after the crash.
Ill have to reduplucate the problem and paste the exact error. Ill try to get to that soon.
My processor is the latest I7 processor (intel I7 4700MQ)
I am reading and writing to the same disk yes. I think my harddrive is 3.0. Should I have the MTS file on the main drive or should it be reading the MTS file from the hard drive and rendering to the main drive? How should I go about that?
When I read something about
((I'm attempting to reduplicate the problem but would you know it has rendered 2000+ frames of the .MTS file and still going strong O_0)) Jeez...
I can deal with this thing taking 7 hours to render the greenscreen straight off the MTS file and formatting it straight to h.264 as an .mp4.. I just cant deal with it crashing mid-way and taking 14 hours or so.
Can you tell me if .MTS file contains enough keyframes for after effects to work with, without crashing? I was thinking that was the whole problem so I was starting to format them as .MOV files as another article suggested. The rendering certainly goes much faster but the space is my only issue now... but hell if it wants to do what its doing RIGHT NOW , I dont care if I have to wait 6 hours.. this is easier than converting to different formats and stuff.
If it comes back up with the erorr I'll repost it .. most likely it will after I give up on it again and assume its going to work right ! Bah..
It's possible that "render multiple frames" won't work in Keylight with AVCHD. AVCHD footage is dependent on I-frames (what you're calling keyframes), and it's likely that Keylight works frame-by-frame and frames must be handled linearly in order. Also, AVCHD requires significant horsepower to decode.
So it makes sense that your QuickTime files key/export much more quickly. Considering the huge file sizes, your QT files are either uncompressed or losslessly compressed. So the overhead from the AVCHD format itself has been moved from happening before Keylight to conversion to the QT files.
At this point, I think things are working correctly. However, there are still some optimizations you can use to (hopefully!) speed things up.
How fast is your internal hard drive? Most laptop hard drives are very slow. If your external drive is USB3.0, it may be even faster than your internal one. Use ATTO Disk Benchmark to gauge this. I would store your source files on the faster drive, and export to the slower one.
Keylight (and any pro keying solution, really) requires horsepower. It has to analyze each frame, which takes time. If you can reduce the amount of frame Keylight has to analyze, it will speed things up considerably. Here's two methods of doing this:
- If the subject is fairly stationary, and let's say he's in the middle of the frame, mask out the left and right sides of the frame using the Pen tool. This will cut down the size of the frame Keylight has to process.
- Another option is to FIRST use a simple color key to key out everything but the outer edge around your subject. Then add Keylight, which will only have to key out this outer edge. For an example of this, see http://vimeo.com/34365256 at the 9-minute mark. BRILLIANT!
The first option is quicker to implement, but if your subject fills the frame there might not be enough area to mask out to improve render speed. The second option takes more time to set up, but should help significantly.
Let me know what you try and how it works for ya!