18 fps --> 23.976 fps

[SiXXGuNNZ]

got some 18 fps material, need to convert it to 23.976 fps for dvd, google gave me a headache

[scharfis_brain]

avisource("bla.avi")
changefs(23.976)


this will give you heavy motion stutters.

better go to 29.97 fps interlaced:

avisource("bla.avi")
changefs(59.94)
assumetff()
separatefields().selectevery(4,0,3).weave()

[actionman133]

ChangeFPS will give crisp frames but may still appear stuttery. Consider using ConvertFPS (59.94). It blends frames together, resulting in smoother motion, but you will lose the integrity of your original frames. If this doesn't matter to you, then ConvertFPS will probably be your better option. If you want the more 'pure' output, then use ChangeFPS. It really depends on what you want.

[scharfis_brain]

@actionman133:
for such big framerate changes, blending is not useful.
look at the common 2:3 pattern.
are there any blendings?

blending only makes sense, if 59.94 <-> 50 of 29.97 <-> 50
framerate changes are wished.

but with 18 fps to 59.94 fps it will make the video less compressible witout inay visible improvement.

EDIT: and for 18fps -> 23.976 fps blending will help a little bit, but motion jerkyness will remain!
this means 23.976fps are not suitable for 18fps content.

[actionman133]

Well there you go... use ChangeFPS. Admittedly, I don't use either of them very much, and I guess it shows....

[SiXXGuNNZ]

thanks guys, good help :)

[Fizick]

You may try ChangeFps, and then DePanStabilize to prevent some global jerkiness.

[scharfis_brain]

@fizick: poor man's mvconvertfps(), eh? :D

but this will IHMO destroy the stuttery 18-fps look.

I think that going for 59.94i via telecine is the best solution - motion wise.

okay, all this depends on personal taste.

[Fizick]

No, it is a wise man's solution! :D

[scharfis_brain]

Yeah!
smooth panning background while the 'poor men' are moving hackly. like on drugs.