In a Bit of a Jam...

[Mister Hatt]

Mirko's suggestion is good, although decimating later on will mess up the smooth motion of your effects and anything else time based that you did in AE or whatever other effects engine.

[CodeZTM]

Well, I think you misunderstood my post Mirko in my pm. It wasn't 2 hours of processing, it was processing 2 hours of footage 4 times through ZarxGui. xD

But it's ok. Thank you all for y our help. I'll just have to start from square one it seems, but it could be far worse.

[Cannonaire]

I don't really see a need to use tdecimate at all, actually. If the AMV was made at 29.97, then it is probably synced exactly how he wants it and the motion smoothness shouldn't be an issue after taking into account timescaling and everything else that gets done in the editing process. Just TFM() should suffice without any decimation.

[mirkosp]

I don't really see a need to use tdecimate at all, actually. If the AMV was made at 29.97, then it is probably synced exactly how he wants it and the motion smoothness shouldn't be an issue after taking into account timescaling and everything else that gets done in the editing process. Just TFM() should suffice without any decimation.

The anime is still 23.976 tho... if there is any 23.976p pan in the source and he didn't stretch time, it'll be incredibly jerky.
Technically, the best solution would be manually going through the exported vid and decimating the dup frames and writing a proper timecodes file, but that's too much effort and totally not worth it, so yeah. It's his choice whether to do 23.976 or 29.97 based on what most of the video is and what would look less bad in motion in the end.