[Pierre Jasmin]

You need to make sure there is a 100% speed keyframe at the frame before where you want to start the slowmo (or work in frame mode)

Scoll down https://library.creativecow.net/tutorials/revisionfx
there is a set of for FCP tutorials (in backward order, starts on second page)

Alternatively on our website: https://help.revisionfx.com/album/19/

Pierre
RE:Vision Effects

[Pierre Jasmin]

You need to make sure there is a 100% speed keyframe at the frame before where you want to start the slowmo (or work in frame mode)

Scoll down https://library.creativecow.net/tutorials/revisionfx
there is a set of for FCP tutorials (in backward order, starts on second page)

Alternatively on our website: https://help.revisionfx.com/album/19/

Pierre
RE:Vision Effects

[Pierre Jasmin]

Often it does not matter. However if the color correction is “too creative”, somehow clamps the data or leaves some areas flat, is animated, etc… it’s better to color correct after. Also depending in what application you run twixtor, you can choose the original media for the ALT Track Sequence and apply Twixtor on the Colored Source, then it will use the original to track but will timewarp the colored source.

Pierre

[Pierre Jasmin]

Often it does not matter. However if the color correction is “too creative”, somehow clamps the data or leaves some areas flat, is animated, etc… it’s better to color correct after. Also depending in what application you run twixtor, you can choose the original media for the ALT Track Sequence and apply Twixtor on the Colored Source, then it will use the original to track but will timewarp the colored source.

Pierre

[Pierre Jasmin]

It’s one way in the end to make the layer duration longer.

Another one would be to set a solid layer of the right spatial dimension and apply twixtor there and set the color and track source to be the proper layer (and turn that layer visibility off).

[Pierre Jasmin]

It’s one way in the end to make the layer duration longer.

Another one would be to set a solid layer of the right spatial dimension and apply twixtor there and set the color and track source to be the proper layer (and turn that layer visibility off).

[Pierre Jasmin]

You can do that – interpret footage to 25 FPS, drop that into a 25 FPS comp… And in Twixtor you then put 25 FPS for input frame rate.

However you don’t need to do that in AE, you can also Make New Comp from that footage (then 50 FPS, and at same time make that comp as long in Comp Duration as will be needed), then drop that comp in a 25 FPS comp, and in Twixtor set input fps to 50.

Also check this:
https://library.creativecow.net/freitag_lori/twixtor-frame-rate-conversion/1
or
https://help.revisionfx.com/album/18/#/tutorial-36

[Pierre Jasmin]

You can do that – interpret footage to 25 FPS, drop that into a 25 FPS comp… And in Twixtor you then put 25 FPS for input frame rate.

However you don’t need to do that in AE, you can also Make New Comp from that footage (then 50 FPS, and at same time make that comp as long in Comp Duration as will be needed), then drop that comp in a 25 FPS comp, and in Twixtor set input fps to 50.

Also check this:
https://library.creativecow.net/freitag_lori/twixtor-frame-rate-conversion/1
or
https://help.revisionfx.com/album/18/#/tutorial-36

[Pierre Jasmin]

Twixtor will work but it won’t be in real-time for HD size frames. It involves render of that section. The more CPU you have the faster. Aside CPU, disk IO bandwidth and the nature of the media affects the render time. For example although so-called camera native formats can be played in a streaming manner fast, they achieve size compression by using what is called long-GOP encoding (e.g. a group of 15 frames is encoded together). So since Twixtor collects two frames on the timeline to make one it ends up some apps (twixtor is a plugin) ends up having to retrieve 15 frames at once to read a frame… so why for example it’s much faster from ProRes for example, or in Avid the equivalent intermediate codec they ingest the media to. I think for example that’s why FCP marketing demo at NAB put so much emphasis on editing native media as they are one of the apps that could be better in that area.

Pierre
RE:Vision Effects

[Pierre Jasmin]

Twixtor will work but it won’t be in real-time for HD size frames. It involves render of that section. The more CPU you have the faster. Aside CPU, disk IO bandwidth and the nature of the media affects the render time. For example although so-called camera native formats can be played in a streaming manner fast, they achieve size compression by using what is called long-GOP encoding (e.g. a group of 15 frames is encoded together). So since Twixtor collects two frames on the timeline to make one it ends up some apps (twixtor is a plugin) ends up having to retrieve 15 frames at once to read a frame… so why for example it’s much faster from ProRes for example, or in Avid the equivalent intermediate codec they ingest the media to. I think for example that’s why FCP marketing demo at NAB put so much emphasis on editing native media as they are one of the apps that could be better in that area.

Pierre
RE:Vision Effects