[Peter Litwinowicz]

Twixtor’s results are really dependent on the clips themselves. I will ask that you try the demo, and make sure to read the short manual that’s installed. At the bottom of the Twixtor manual is a lost of shots that may be problematic with Twixtor. There is also help with Twixtor, and with frame rate changes, here: https://library.creativecow.net/freitag_lori/twixtor-frame-rate-conversion/1

Cheers,
Pete Litwinowicz
RE:Vision Effects Tech Support Team

[Peter Litwinowicz]

Twixtor’s results are really dependent on the clips themselves. I will ask that you try the demo, and make sure to read the short manual that’s installed. At the bottom of the Twixtor manual is a lost of shots that may be problematic with Twixtor. There is also help with Twixtor, and with frame rate changes, here: https://library.creativecow.net/freitag_lori/twixtor-frame-rate-conversion/1

Cheers,
Pete Litwinowicz
RE:Vision Effects Tech Support Team

[Peter Litwinowicz]

I’ll focus on this question:

[Sean Warman] “The 29.97 sequence did not work nearly as well, specifically with the footage that was shot at 59.94. “

The reason for this is that FCP doesn’t let us know the internal clip is 59.94. It forces us to work at 29.97. So what’s happening in this case is that Twixtor is only working with 1/2 the number of frames than when you work with 59.94 footage in a 59.94 sequence. Simple as that. Rule of thumb: always work with footage at it’s native frame rate. If you need to change frame rates, you’ll want to conform the original sequence to the new frame rate first, using CInema Tools. You can follow this tutorial here: https://library.creativecow.net/freitag_lori/twixtor-fcp-frc/1

Your editing the 59.94 footage in a 29.97 sequence is basically a frame rate change, so you’d want to conform to 29.97 first.

[Sean Warman] “So, other then long renders and storage is there a problem with editing and exporting on a 59.94 sequence?
“

No, certainly no problem. HOwever, if you want to edit in 29.97 timeline, you can certainly do that by first conforming the footage you want to Twixtor to 29.97 first.

Pete
RE:Vision Effects, Inc.

[Peter Litwinowicz]

I’ll focus on this question:

[Sean Warman] “The 29.97 sequence did not work nearly as well, specifically with the footage that was shot at 59.94. “

The reason for this is that FCP doesn’t let us know the internal clip is 59.94. It forces us to work at 29.97. So what’s happening in this case is that Twixtor is only working with 1/2 the number of frames than when you work with 59.94 footage in a 59.94 sequence. Simple as that. Rule of thumb: always work with footage at it’s native frame rate. If you need to change frame rates, you’ll want to conform the original sequence to the new frame rate first, using CInema Tools. You can follow this tutorial here: https://library.creativecow.net/freitag_lori/twixtor-fcp-frc/1

Your editing the 59.94 footage in a 29.97 sequence is basically a frame rate change, so you’d want to conform to 29.97 first.

[Sean Warman] “So, other then long renders and storage is there a problem with editing and exporting on a 59.94 sequence?
“

No, certainly no problem. HOwever, if you want to edit in 29.97 timeline, you can certainly do that by first conforming the footage you want to Twixtor to 29.97 first.

Pete
RE:Vision Effects, Inc.

[Peter Litwinowicz]

Not sure why Twixtor or PP is freezing. Send us a clip and PP project as I suggested to you in email.
As to the red bar: also not sure, will take a look

However, for the problem where Twixtor starts at a different point depending on where the in/out point is trimmed, do the following: put the clip and Twixtor into a sub-sequence (a nested sequence). And replace the clip with Twixtor in your edit with this sequence. Then as you move the in point on the sequence, you should not see your images shift.

the reason for this is due to a limitation between Twixtor and Premiere Pro… as you change the in-point, Premiere Pro tells us a different starting point for the clip. by placing the clip with Twixtor into a nested sequence and changing the in-point on that sequence (rather than the clip with Twixtor applied), you should see stable output when you change the in-point on the sequence.

To recap: never change the in-point on a clip that has twixtor applied… wish we could avoid this problem, as I’m sure you do too. But nesting the sequence should solve the problem.
Pete
RE:Vision Effects

[Peter Litwinowicz]

Not sure why Twixtor or PP is freezing. Send us a clip and PP project as I suggested to you in email.
As to the red bar: also not sure, will take a look

However, for the problem where Twixtor starts at a different point depending on where the in/out point is trimmed, do the following: put the clip and Twixtor into a sub-sequence (a nested sequence). And replace the clip with Twixtor in your edit with this sequence. Then as you move the in point on the sequence, you should not see your images shift.

the reason for this is due to a limitation between Twixtor and Premiere Pro… as you change the in-point, Premiere Pro tells us a different starting point for the clip. by placing the clip with Twixtor into a nested sequence and changing the in-point on that sequence (rather than the clip with Twixtor applied), you should see stable output when you change the in-point on the sequence.

To recap: never change the in-point on a clip that has twixtor applied… wish we could avoid this problem, as I’m sure you do too. But nesting the sequence should solve the problem.
Pete
RE:Vision Effects

[Peter Litwinowicz]

I presume you are using the FxPlug version within FCP and not the AE-compatible version. Otherwise my directions would be different.

I presume that you might be hitting the problem described here: https://www.revisionfx.com/support/faqs/hostfaqs/fcp_fields/

Also, Not sure where you are getting Twixtor 4.5 as a first time user… if you are trying out a demo you should be using Twixtor 5.

Pete

[Peter Litwinowicz]

I presume you are using the FxPlug version within FCP and not the AE-compatible version. Otherwise my directions would be different.

I presume that you might be hitting the problem described here: https://www.revisionfx.com/support/faqs/hostfaqs/fcp_fields/

Also, Not sure where you are getting Twixtor 4.5 as a first time user… if you are trying out a demo you should be using Twixtor 5.

Pete

[Peter Litwinowicz]

The real question is this: what are you delivering to? I can’t imagine anyone actually playing back 60p at this point in time (not on the web via Vimeo or YouTube… and certinaly not for broadcast where you might see 60i). You certainly don’t want FCP to have to render 60p if your final delivery is 30p (that’s twice as many frames to render than you need at the end!).

So really it depends on what your final delivery is. Presumably this will be 30p or 24p, right? That said, if 60p is your delivery frame rate, the 60p it is.

pete Litwinowicz
RE:Vision Effects, Inc.

[Peter Litwinowicz]

The real question is this: what are you delivering to? I can’t imagine anyone actually playing back 60p at this point in time (not on the web via Vimeo or YouTube… and certinaly not for broadcast where you might see 60i). You certainly don’t want FCP to have to render 60p if your final delivery is 30p (that’s twice as many frames to render than you need at the end!).

So really it depends on what your final delivery is. Presumably this will be 30p or 24p, right? That said, if 60p is your delivery frame rate, the 60p it is.

pete Litwinowicz
RE:Vision Effects, Inc.