[Pierre Jasmin]

Mark,

In AE, did you set the field menu in Twixtor to Upper Field (probably what it is if 1080)?
Otherwise you are only using half the video fields as source so it will make a big difference.

Did you look at tutorials at help dot revisionfx dot com (some also here at the cow)?

Pierre

[Pierre Jasmin]

Something wrong
Can you send a project of the app (e.g. AE CS5) with a frame of color/beauty pass and one frame of the MV
(to techsupport at revisionfx dot com)
Also when you do tell us what version of C3D etc

Pierre

[Pierre Jasmin]

Something wrong
Can you send a project of the app (e.g. AE CS5) with a frame of color/beauty pass and one frame of the MV
(to techsupport at revisionfx dot com)
Also when you do tell us what version of C3D etc

Pierre

[Pierre Jasmin]

Adam,

Sorry for delay I was at NAB

What is the output FPS you want to render at? I read you say 59.94 FPS (well you said 60)
What is the input FPS your project is set to if you look at Project Properties Frame Rate? 59.94?
What is the clip you imported property frame rate? I read you say 29.97 FPS (well you said 30)
Do you have fields in source media or are you trying to export with fields? (I assume no)

Additional Note: Twixtor speed is not the same thing as FPS

Here’s what tutorials say:

So if you have 90 frames at 30P (3 seconds) and the project property (what you want to render at) is 60P and no fields, so you want 180 frames so the effective duration remains the same. Now once you drop the clip on the timeline you first see each frame repeated twice. You select clip in timeline and right click select property and type for Playback Rate (2.0 because it’s what is 59.94/29.97). Now you see all the frames except you still only have 90 frames and you need 180. So you apply Twixtor, and you set speed to 50% and you grab the clip end-point handle at the end to make the duration twice as long so the clip is still 3 seconds.

Pierre

[Pierre Jasmin]

Adam,

Sorry for delay I was at NAB

What is the output FPS you want to render at? I read you say 59.94 FPS (well you said 60)
What is the input FPS your project is set to if you look at Project Properties Frame Rate? 59.94?
What is the clip you imported property frame rate? I read you say 29.97 FPS (well you said 30)
Do you have fields in source media or are you trying to export with fields? (I assume no)

Additional Note: Twixtor speed is not the same thing as FPS

Here’s what tutorials say:

So if you have 90 frames at 30P (3 seconds) and the project property (what you want to render at) is 60P and no fields, so you want 180 frames so the effective duration remains the same. Now once you drop the clip on the timeline you first see each frame repeated twice. You select clip in timeline and right click select property and type for Playback Rate (2.0 because it’s what is 59.94/29.97). Now you see all the frames except you still only have 90 frames and you need 180. So you apply Twixtor, and you set speed to 50% and you grab the clip end-point handle at the end to make the duration twice as long so the clip is still 3 seconds.

Pierre

[Pierre Jasmin]

Perhaps this tutorial will shed some light
Basically you have to combine Vegas Rate and Twixtor Speed

https://library.creativecow.net/freitag_lori/Twixtor-in-Vegas-Frame-Rates/1

Pierre

[Pierre Jasmin]

Perhaps this tutorial will shed some light
Basically you have to combine Vegas Rate and Twixtor Speed

https://library.creativecow.net/freitag_lori/Twixtor-in-Vegas-Frame-Rates/1

Pierre

[Pierre Jasmin]

I did not close this thread based on off-line discussion so here:

You have to split the morph in two
Take the “warp to” spline of that surrounds an area you don’t want moving in second morph, and paste it two times in second warp (typically in a second comp). Two times so from and to are at that same location, this will lock these pixels.

Pierre

[Pierre Jasmin]

I did not close this thread based on off-line discussion so here:

You have to split the morph in two
Take the “warp to” spline of that surrounds an area you don’t want moving in second morph, and paste it two times in second warp (typically in a second comp). Two times so from and to are at that same location, this will lock these pixels.

Pierre

[Pierre Jasmin]

To add to this, the latest 7970 is a beast in that price point but in practice (fine print) it requires something like 450W of power by itself. It does not help at all someone using Premiere but it would help a lot an openCL app like FCP X for example. Just so it’s clear to run a new dual Sandy Bridge dual Extreme and two 7970 cards and add other peripherals, would bring the power requirement to something like a 1400W power supply for a system (before anyone tries overclocking, what is that? $100 a month in electricity for 12 hours a day???). And not something that could be retrofitted on say an iMac (iMac Pro X would need to be bigger)… If FCP was still considered an horse in terms of driving hardware sales, they would probably have made sure to go with cards that can’t run CUDA just to annoy Adobe… At this point it does not look like it’s going to happen on Apple front and maybe Smoke on the Mac (to give a different clear example of a system where such config would be legit) should also become Smoke on Windows… 🙂