Equivalent of "Pixel Motion" in AE

[audiohominis]

Back for help again, guys. I'm looking to convert 30fps footage to 24fps footage PROPERLY, i.e. without that periodic jerky effect. I believe the formal term is "temporal scaling". Will "DePan" give me what I want? Is there something better? How does it work?
Thanks.

[Dark Shikari]

The formal term is "motion-compensated framerate changing", and it's slow and still not very good. There is no "right" way to convert 30fps to 24fps.

[audiohominis]

I'm aware of the extreme computational cost of this approach but it provides excellent results for reducing the fps and occasionally even acceptable results for extending the footage.
If there's an AVISynth plugin that can perform as good as AE's Pixel Motion, I'll be happy ...and not very surprised, BTW, since it wouldn't be the first time freeware matching/outperforming its commercial counterparts. It does happen.
Thank you again.

[Dark Shikari]

MVFlowFPS

[wonkey_monkey]

MVFlowFPS is the function in MVTools version 1, while MFlowFPS (without the V) is the function in MVTools version 2.

Depan could also work in some cases, but both will fall down if there is too much motion within the clip. I've had great success with MVTools, for example, travelogue footage which tends not to be too actiony but may things like crowd scenes or city scapes. On those scenes where it fails, I just splice in footage that has been done with convertfps or changefps (i.e., jerky, as you said).

David

[Alex_ander]

In very many cases it works well throughout, much depends on the relationship between source framerate, type/ammount of motion and shape of moving objects (drumsticks and fiddlesticks are usually problematic). This defines ammount of correlation between object positions in different frames and therefore, the possibility to extract proper motion information. Generally, interlaced NTSC is the best source (needs bobbing before MFlowFPS), progressive 30fps is not as good and wants testing with particular material (target framerate doesn't matter as much as source). Low framerates from still cameras make problems with most types of footage.

[7ekno]

MCTempGause to 60fps, MFlowFPS to 24fps ..

7

[shoopdabloop]

MFlowFPS might give PixelMotion-quality results, but I am unsure of the differences.

[Blue_MiSfit]

If your content is actually 30fps pure interlaced, then you can bob to 60p and then use MFlowFPS to bring it down to 24fps.

If your content is 30fps interlaced, but hard telecined, then you should use an inverse telecine filter.

If you content is 30fps progressive, then you can use MFlowFPS to 24fps.

~MiSfit

[audiohominis]

It's footage from the Mark II, so MFlowFPS to 24fps it is then.:thanks:

[scharfis_brain]

why do you want to make it 24p?
going from 30 to 24 always is very bad.

[audiohominis]

After reading the official manual, I'm still a bit unclear on the usage. Is it a one-step process, or a two-step process where you acquire motion vector analysis data first? I'm also slightly confused about the denomination part.:confused:
My epic gratitude would go out to whoever provides me with a little code snippet for converting a 30fps png sequence to a 30pfs one.
:thanks: in advance
why do you want to make it 24p?
going from 30 to 24 always is very bad.
Exactly, how do you mean, always?

[wonkey_monkey]

It's footage from the Mark II, so MFlowFPS to 24fps it is then.:thanks:

Isn't there a firmware update to enable 24fps now?

David

[audiohominis]

Isn't there a firmware update to enable 24fps now?David
We are editing footage that was shot a while ago.
I still await your kind help on MVFlowFPS

[Blue_MiSfit]

Straight from the MVTools2 Documentation:


AVISource("c:\test.avi") # or MPEG2Source, DirectShowSource, some previous filter, etc
super = MSuper(pel=2)
backward_vec = MAnalyse(super, overlap=4, isb = true, search=3)
# Use block overlap, halfpixel accuracy and Exhaustive search
forward_vec = MAnalyse(super, overlap=4, isb = false, search=3)
MFlowFps(super, backward_vec, forward_vec, num=24000, den=1001)


There are faster options in the documentation as well.

~MiSfit

[audiohominis]

Thanks, Blue_MiSfit
I'm gona test to see if this would also work with ImageSource(...) ConvertToYV12()
:thanks:

[SubOne]

MFlowFPS has its limitations - especially if there is a lot of motion, AE's Pixel Motion Timewarp performs considerably better. Then again, it costs infinite times as much. MFlowFPS is pretty fantastic for less complex video though.