[Peter Litwinowicz]

What version of FCP are you using?

Pete LItwinowicz
RE:VIsion Effects, Inc.

[Peter Litwinowicz]

You can also use our SmoothKit Gaussian Per Pixel (SmoothKit is $119). It has a mode to blur using the “Gradient Magnitude” as a compound blur control (“gradient Magnitude” is a fance word for “edges”).

To see the control map that the plugin is using, you can set the Process Mode to “Show Control Maps”. Then set AE to view the Blue channel and you’ll see the size control displayed (white== max blur, black==no blur).

https://www.revisionfx.com/products/smoothkit/
Pete Litwinowicz
RE:Vision Effects, Inc.

[Peter Litwinowicz]

You’ll see that if you put another layer below the one with the morph that the morph is not on top of black… the black areas are, in fact, transparent areas that you can see through…and if you don’t put another layer below the morph, then AE defaults to putting black there.

We can’t keep the blue, because as parts of the original keyed images are overlayed on top of each other then you’d see blue. So what we do is morph the two transparent images (or layers), and leave those areas completely transparent.

So since you keyed out the blue, RE:FLex knows that and then keeps the transparent areas transparent.

pete
RE:Vision Effects, Inc.

[Peter Litwinowicz]

You’ll see that if you put another layer below the one with the morph that the morph is not on top of black… the black areas are, in fact, transparent areas that you can see through…and if you don’t put another layer below the morph, then AE defaults to putting black there.

We can’t keep the blue, because as parts of the original keyed images are overlayed on top of each other then you’d see blue. So what we do is morph the two transparent images (or layers), and leave those areas completely transparent.

So since you keyed out the blue, RE:FLex knows that and then keeps the transparent areas transparent.

pete
RE:Vision Effects, Inc.

[Peter Litwinowicz]

Yes, I agree that turning up the shutter speed can make it look “wrong.”

But then you can often use our ReelSmart Motion Blur to add the motion blur back in. (of course i’m biased)… and many of our customer do just that with great success.

Pete Litwinowicz
RE:Vision Effects, Inc.

[Peter Litwinowicz]

By the way, there is a Cow tutorial by our trainer Lori Freitag that teaches you how to convert frame rates using Twixtor. And then you can resize after you retime (that’s how I would work… I wouldn’t resize before retiming, because you have the original info before resizing).

https://library.creativecow.net/articles/freitag_lori/twixtor-frame-rate-conversion.php

Free demo version of Twixtor here: https://www.revisionfx.com/products/twixtor/downloads/#ae_compatible_4
Pete LItwinowicz

[Peter Litwinowicz]

If the thread stays still, and it’s not more than a couple pixels (or so) wide, you can create a small black and white matte for where the thread is on the lens, then use our RE:FIll to fill back in the corrupted pixels.

There is a free demo version. Make sure to look for the manual that’s put on your disk when you install.

Overview: https://www.revisionfx.com/products/refill/
Demo version: https://www.revisionfx.com/products/refill/downloads/
Price: $99.95.

Cheers,
Pete LItwinowicz
RE:Vision Effects, Inc.
https://www.revisionfx.com

[Peter Litwinowicz]

First: I presume the frame rate converted footage doesn’t look jaggy, correct?

Sounds to me like Compressor marked the footage as interlaced when it should be marked progressive.

Take a look at the item properties for the footage. Right-click (or option-click) on the footage in the bin and select Item Properties->Format… Make sure it says “None” for “Field Dominance”. If it says Upper or Lower, right-clock where it says upper or lower, a menu will appear and choose “None”.

You’ll then need to drop your clip into a new sequence, so that the sequence and the clip within that sequence gets marked as “None” for Field Dominance. Apply twixtor again and set the speed to 120%.

If that isn’t your problem, send a 10 to 20 frame SOURCE (before Twixtor) clip to us at techsupport (at) revisionfx (dot) com, and and FCP project that shows the problem when Twixtor is applied.

Cheers,
Pete Litwinowicz

[Peter Litwinowicz]

First: I presume the frame rate converted footage doesn’t look jaggy, correct?

Sounds to me like Compressor marked the footage as interlaced when it should be marked progressive.

Take a look at the item properties for the footage. Right-click (or option-click) on the footage in the bin and select Item Properties->Format… Make sure it says “None” for “Field Dominance”. If it says Upper or Lower, right-clock where it says upper or lower, a menu will appear and choose “None”.

You’ll then need to drop your clip into a new sequence, so that the sequence and the clip within that sequence gets marked as “None” for Field Dominance. Apply twixtor again and set the speed to 120%.

If that isn’t your problem, send a 10 to 20 frame SOURCE (before Twixtor) clip to us at techsupport (at) revisionfx (dot) com, and and FCP project that shows the problem when Twixtor is applied.

Cheers,
Pete Litwinowicz

[Peter Litwinowicz]

if you want to see both fields on your external monitor from a RAM preview, you can use our FieldsKit product, which as a “REinterlacer” plugin that will time sample your 29.97 comp at each field time (that is, at each frame, and exactly between each frame) to create interlaced footage in the RAM preview. You simply select the “< Half Frame Rate" option within a 29.97 (25 in PAL) comp.. Select whether you want the output to be Lower Field First or Upper Field First within the plugin, and voila, you get a RAM preview as if you used AE"s rendering to disk to produce interlaced material. https://www.revisionfx.com/products/fieldskit/

Free demo version: https://www.revisionfx.com/products/fieldskit/downloads/

Pete Litwinowicz
RE:Vision Effects, Inc.