[Pierre Jasmin]

I would shoot 60P the material that will be slow-mo if it’s an option. To match the 24P and 60P look, the slider “Motion Blur Compensation” at the bottom of Twixtor controls is a good option.

Pierre

[Pierre Jasmin]

I would shoot 60P the material that will be slow-mo if it’s an option. To match the 24P and 60P look, the slider “Motion Blur Compensation” at the bottom of Twixtor controls is a good option.

Pierre

[Pierre Jasmin]

That indicates a frame rate issue somehow

Normally this happens when the source FPS (nested comp or media) is not the same as the Input FPS slider in Twixtor. For example someone types 24 or 23.96 instead of 23.976…

Are you sure that’s not it?

Pierre

[Pierre Jasmin]

That indicates a frame rate issue somehow

Normally this happens when the source FPS (nested comp or media) is not the same as the Input FPS slider in Twixtor. For example someone types 24 or 23.96 instead of 23.976…

Are you sure that’s not it?

Pierre

[Pierre Jasmin]

I only see the output movie
not MVI_2807.mov which is what I would need to look at yout project

Pierre
RE:Vision Effects

[Pierre Jasmin]

I only see the output movie
not MVI_2807.mov which is what I would need to look at yout project

Pierre
RE:Vision Effects

[Pierre Jasmin]

Not directly possible in RSMB.
And it’s on our feature request list.

Ideas of some imperfect workarounds.

If you use Maya or Softimage and Mental Ray + AE there is a different option which is in SmoothKit (SmoothKit Directional that is part of the SmoothKit plugin set) that allows blur one way only. Probably still works better to do a bit of RSMB first if you do SmoothKit Directional One Way. If you already have the MV, and also have our RE:Map plugins, there is a way to convert the Motion Vectors to a form SmoothKit understands with RE:map Displace. I can go over with you at techsupport if you want as it’s a bit convoluted. The only two shaders I know are LaMaison Mental Shader that has this as a target option and Mental Images mip motion vector shader where for that you have to set boolean “blue_is_magnitude”… (read the doc).

Another way is to apply SmoothKit Frame Accumulate after RSMB with 1 for Previous frames and make the Blur Amount 1.0 in RSMB. This will give you a long follow trail. This only works if the RSMB blur amount is over 1.0 (so the motion blur trail connect to the previous frame)

I tried before playing in Maya with Shutter Open to render the Motion Vectors time offset from beauty pass but the result is not always glorious.

Pierre
RE:Vision Effects

[Pierre Jasmin]

Not directly possible in RSMB.
And it’s on our feature request list.

Ideas of some imperfect workarounds.

If you use Maya or Softimage and Mental Ray + AE there is a different option which is in SmoothKit (SmoothKit Directional that is part of the SmoothKit plugin set) that allows blur one way only. Probably still works better to do a bit of RSMB first if you do SmoothKit Directional One Way. If you already have the MV, and also have our RE:Map plugins, there is a way to convert the Motion Vectors to a form SmoothKit understands with RE:map Displace. I can go over with you at techsupport if you want as it’s a bit convoluted. The only two shaders I know are LaMaison Mental Shader that has this as a target option and Mental Images mip motion vector shader where for that you have to set boolean “blue_is_magnitude”… (read the doc).

Another way is to apply SmoothKit Frame Accumulate after RSMB with 1 for Previous frames and make the Blur Amount 1.0 in RSMB. This will give you a long follow trail. This only works if the RSMB blur amount is over 1.0 (so the motion blur trail connect to the previous frame)

I tried before playing in Maya with Shutter Open to render the Motion Vectors time offset from beauty pass but the result is not always glorious.

Pierre
RE:Vision Effects

[Pierre Jasmin]

Yes, there is an issue with CS5.5 (OK in CS5.0)
And I did file a bug at Adobe for it.

Essentially what I noticed is if I make a keyframe at frame 0, Premiere does not remember it, looks like this:

* type 100 at frame 0 for Speed param in Twixtor
* go to frame 60, type 60
* come back to first keyframe pressing < (previous KF) and value at frame 0 is now 60…

workaround: seems to work if I set KF at frame 1 instead, seems to be an issue with frame 0

Pierre

[Pierre Jasmin]

Yes, there is an issue with CS5.5 (OK in CS5.0)
And I did file a bug at Adobe for it.

Essentially what I noticed is if I make a keyframe at frame 0, Premiere does not remember it, looks like this:

* type 100 at frame 0 for Speed param in Twixtor
* go to frame 60, type 60
* come back to first keyframe pressing < (previous KF) and value at frame 0 is now 60…

workaround: seems to work if I set KF at frame 1 instead, seems to be an issue with frame 0

Pierre