[Ben Insler]

Also, I’m not sure if this is what your’e saying, but if you’re using a Depth Matte embedded in your image, I believe that depth mattes are not anti-aliased, so when you use them to apply DOF, the edges of your in focus objects may seem blocky as they overlap the blurred area. I’ve never tried it, but I would think that if you have the time to render your frame size larger, you should be able to apply DOF and then scale down to your target resolution, thus minimizing the amount of aliased blur through downscaling the final render with DOF applied (like decreasing the size of a low res photo that is blocky). I’ve never tried it, and it might not even be what you’re talking about, but it’s the solution in my mind that I’ve always wanted to try, and it might save you from having to buy other software if it’s really expensive…

Best,

Ben

[Ben Insler]

sweet!

thanks.

[Ben Insler]

sweet!

thanks.

[Ben Insler]

Kev,

I have the same problem. However, I know that on a newer system running AE 6.5 that I’ve used, quicktime was upgraded from 6 (free) to 7 (pro) and it does recognize it, although to be honest it looks like the quality of exporting using the DV codec has gotten worse. Anyway, my current guess is that since QT7 just came out, AE doesn’t have the capability to tap into QT7 and encode using the new QT7 codecs without having pro (probably would have to be an upgrade, or more realistically built into the next version of AE) But I have run into the same problem and I hear your pain.

Best of luck,

Ben

[Ben Insler]

Honestly…I’m still laughing out loud at myself… the loop expressions cycle over next or previous key, not frames… right?

Thanks Dan.

Ben Insler
Editor
Telemark Films

[Ben Insler]

Honestly…I’m still laughing out loud at myself… the loop expressions cycle over next or previous key, not frames… right?

Thanks Dan.

Ben Insler
Editor
Telemark Films

[Ben Insler]

as of Macworld in boston three weeks ago, this had not been fixed in 5.

Ben Insler
Editor
Telemark Films

[Ben Insler]

Go to the FCP menu and open User Prefrences. On the right side of the window, make sure that you []Abort capture on dropped frames is turned off and that your action On Timecode Break is set to “Warn After Capture.” This may have NOTHING to do with this problem at all, but it has helped us out with capturing 24p footage – sometimes FCP flips out when there are little timecode issues that it can actually deal with, but it gets angry about them anyway – this could alleviate some stress…

It’s the only thing I can think of right now.

Ben Insler
Editor
Telemark Films

[Ben Insler]

John,

I just posted this for somoene else as well, but I’ll paste it here for you too.

——–
Hey Eli,

Have run into this numerous times when dealing with Offline/HDD crash issues resulting in recapturing and reconnecting. I was just at the Macworld FCP class and asked about this – the answer (word for word) : “You’re screwed.” Basically, you have to rebuild all your speed changes. I wish I had a better answer for you, but that’s what they told me and they were teaching the class in FCP 5.
———-

In terms of your color effects, those should work fine. I don’t know why you’re having a problem (I’m assuming that you’re using FCP filters for these effects).

Ben Insler
Editor
Telemark Films

[Ben Insler]

Hey Eli,

Have run into this numerous times when dealing with Offline/HDD crash issues resulting in recapturing and reconnecting. I was just at the Macworld FCP class and asked about this – the answer (word for word) : “You’re screwed.” Basically, you have to rebuild all your speed changes. I wish I had a better answer for you, but that’s what they told me and they were teaching the class in FCP 5.

Best of luck

Ben Insler
Editor
Telemark Films