[Peter Litwinowicz]

Instead of doing it the way you are doing, on the first frame of the sequence set a Speed % keyframe of 100. Then on the frame before the section you want to slow down, set another keyframe of 100%. Then on the first frame of the section you want to slow down, set a speed % of what you want to slow down to.

(make sure your two 100% keyframes are set to have linear interpolation, so you don’t get anything but 100% speed in the area before you slowdown).

Then after you find the slowdown you like, say it’s 10%. Go to the last frame of the slowdown section that you want and set a keyframe of 10%. Then on the frame after that, set another keyframe for 100% to back to “regular” speed.
Pete

[Peter Litwinowicz]

Instead of doing it the way you are doing, on the first frame of the sequence set a Speed % keyframe of 100. Then on the frame before the section you want to slow down, set another keyframe of 100%. Then on the first frame of the section you want to slow down, set a speed % of what you want to slow down to.

(make sure your two 100% keyframes are set to have linear interpolation, so you don’t get anything but 100% speed in the area before you slowdown).

Then after you find the slowdown you like, say it’s 10%. Go to the last frame of the slowdown section that you want and set a keyframe of 10%. Then on the frame after that, set another keyframe for 100% to back to “regular” speed.
Pete

[Peter Litwinowicz]

Gosh, it’s a matter of taste, isn’t it? However if you want to simulate 180 degree shutter and you had shot with a shutter that captured no blur, I would use 0.5. Since you already have some blur, shooting at 30 (degrees I assume), which is 1/6 of what you want (30/180), I would try (5/6)*0.5, or .416. Your mileage may vary.

As to grain: adding motion blur after grain will smear the grain, as you have correctly anticipated. Again, that look may or may not be what you want

Pete LItwinowicz
RE:Vision Effects, In

[Peter Litwinowicz]

Gosh, it’s a matter of taste, isn’t it? However if you want to simulate 180 degree shutter and you had shot with a shutter that captured no blur, I would use 0.5. Since you already have some blur, shooting at 30 (degrees I assume), which is 1/6 of what you want (30/180), I would try (5/6)*0.5, or .416. Your mileage may vary.

As to grain: adding motion blur after grain will smear the grain, as you have correctly anticipated. Again, that look may or may not be what you want

Pete LItwinowicz
RE:Vision Effects, In

[Peter Litwinowicz]

New link: https://www.revisionfx.com/products/rsmb/features/#ae_compatible_5

Note that the Pro section is what’s added in the Pro version.
pete

[Peter Litwinowicz]

New link: https://www.revisionfx.com/products/rsmb/features/#ae_compatible_5

Note that the Pro section is what’s added in the Pro version.
pete

[Peter Litwinowicz]

[Joaquin Revel] “did the steps needed to do the slow motion with say 4% speed, but once it renders the video, just lags up it reaches the slow motion clip. “

Not sure what you mean? what does “just lags up it reaches the slow motion clip” mean?

If Twixtor works at 20%, it should work okay at 4%. Of course if there are any artifacts they will become more obvious at 4% than at 20%.

Basically Twixtor behavior is that it inbetweens frames with linear interpolation. ARe you seeing what seems like speed changes or shifts at each of the original frames when you slow mo to 4%? If so, then perhaps that’s too drastic for Twixtor. You might try slowing down by 20%, render out, read it, and slow down again. Although can introduce it’s own set of problem.

Twixtor Pro is not offered for Vegas Pro (because it doesn’t have the support we need). You can read more about Twixtor Pro features for After Effects here to understand the differences, but basically we supply more features so you can hand-tweak the results using mattes and splines. https://www.revisionfx.com/products/twixtor/features/#ae_compatible_4

Pete Litwinowicz

[Peter Litwinowicz]

[Joaquin Revel] “did the steps needed to do the slow motion with say 4% speed, but once it renders the video, just lags up it reaches the slow motion clip. “

Not sure what you mean? what does “just lags up it reaches the slow motion clip” mean?

If Twixtor works at 20%, it should work okay at 4%. Of course if there are any artifacts they will become more obvious at 4% than at 20%.

Basically Twixtor behavior is that it inbetweens frames with linear interpolation. ARe you seeing what seems like speed changes or shifts at each of the original frames when you slow mo to 4%? If so, then perhaps that’s too drastic for Twixtor. You might try slowing down by 20%, render out, read it, and slow down again. Although can introduce it’s own set of problem.

Twixtor Pro is not offered for Vegas Pro (because it doesn’t have the support we need). You can read more about Twixtor Pro features for After Effects here to understand the differences, but basically we supply more features so you can hand-tweak the results using mattes and splines. https://www.revisionfx.com/products/twixtor/features/#ae_compatible_4

Pete Litwinowicz

[Peter Litwinowicz]

To add to what Pierre said, from the manual:

Note on negative speed: A Speed% of -100.00 does not simply flip the original sequence so that it plays backwards starting at frame 0. Imagine the play head on your clip. If you are at the beginning of the clip and you tell the machine (Twixtor in this case) to start playing backward, then there’s nothing before the clip starting position to play. That’s why you will not see a result with a negative speed as the first keyframe. If you play the clip at 100% for a while, then put in a –30% keyframe (or other negative value) at the place where you want to start playing backward you will see proper results.

Pete Litwinowicz

[Peter Litwinowicz]

To add to what Pierre said, from the manual:

Note on negative speed: A Speed% of -100.00 does not simply flip the original sequence so that it plays backwards starting at frame 0. Imagine the play head on your clip. If you are at the beginning of the clip and you tell the machine (Twixtor in this case) to start playing backward, then there’s nothing before the clip starting position to play. That’s why you will not see a result with a negative speed as the first keyframe. If you play the clip at 100% for a while, then put in a –30% keyframe (or other negative value) at the place where you want to start playing backward you will see proper results.

Pete Litwinowicz