I think I might have found the problem.
The mjpeg source I edited with is 29 FPS, but the deinterlaced Huffy is 23 FPS.
I have a feeling adding AssumeFPS(29.97) after the deinterlacing commands might bring it back to where it should be.

Cycle - The number tells decimate how regularly to remove a frame. For NTSC IVTC it is 1 in every 5 frames. Later you will see some examples where decimation is used differently or not at all..Mode - The mode will govern what frame in a sequence gets deleted. This decision will affect how smooth the output will be. For a simple NTSC Telecine of anime, mode of 2 is best - you can read the decomb manual for info on the other modes.

OK, you said your using an avi file... what codec is your avi? does it play right outside of premiere? Like in Virtual Dub? it may be a bad codec or bad encode of a video... re-encoding the video might be a solution.... if the avs scripting dosnt work..

When I started work on this video a year ago (and then forgot about it for 8 months) I didn't know about all of this stuff, so my timeline is all in 29.97fps.

Most deinterlacing filters won't change your FPS. EADFAG goes over a bunch of possibilities <a href="http://www.animemusicvideos.org/guides/avtech/interlaceremoval.html">here</a>; I've never used any of them myself.

Decimate is not, and never has been, a deinterlacing filter; all it does is get rid of extra frames.
(In fact, its partner function Telecide isn't really a deinterlacer either; it's a field matcher that uses a deinterlacer if it can't find a non-combed match and postprocessing is turned on.)

he was using telecide with decimate as his deinterlacer but the settings on decimate were probably incorrect giving him a different frame rate. I took the Decimate(cycle=5) from the EADFAG because it suggested that with telecide and NTSC (29.97) footage in.

Personally I use
TomsMoComp(1,5,1)
which I believe doesn't alter fps (it's in the amvapp)

but then I'm a PAL user so this stuff is a bit different and more difficult *cough* blending *cough* for me.

If it's like most AVI files for computer playback (downloaded video), it's most likely already de-interlaced so doing it again is unnecessary. Most DV-AVI files (from camcorders or output from Windows Movie Maker, etc.), though, do need de-interlacing if there is to be any editing beyond just basic scene rearranging, especially if the final output is for computer playback.

For de-interlacing (keeping 29.97 fps) I use either TDeint() or TomsMoComp(). Sometimes one does a bit better with certain anime than the other.

Warpwind wrote:he was using telecide with decimate as his deinterlacer...

Technical note: Telecide plus Decimate does not deinterlace; it performs an inverse telecine. In other words, Telecide plus Decimate restores the original progressive frames and gets rid of the duplicates created by the telecine process, which usually gives you a frame rate of 23.976 when you're done. More on this in EADFAG; I don't wish to repeat.

You can use a deinterlacer as part of an IVTC process (and most IVTC plugins do), but you should not use an IVTC solution if all you need is deinterlacing (without reducing the frame rate).

Warpwind wrote:he was using telecide with decimate as his deinterlacer...

Technical note: Telecide plus Decimate does not deinterlace; it performs an inverse telecine. In other words, Telecide plus Decimate restores the original progressive frames and gets rid of the duplicates created by the telecine process, which usually gives you a frame rate of 23.976 when you're done. More on this in EADFAG; I don't wish to repeat.

You can use a deinterlacer as part of an IVTC process (and most IVTC plugins do), but you should not use an IVTC solution if all you need is deinterlacing (without reducing the frame rate).

Ah thanks for that. I think I get it now. I had always thought that telecide by deinterlacing created duplicate frames and thus increased the fps. Which is why I thought decimate was necessary.

But if telecide keeps the same framerate why is decimate even mentioned in the guide? Is it just for completeness sake?