Minion wrote:Minion wrote:it was actual 720x480
square pixel.
post a script to help, or gtfo troll
If the footage came off a DVD or DV cam at 720x480 it didn't have square pixels. It had rectangular pixels at an aspect ratio of 10/11 (Roughly). This is because TV's don't have square pixels. PCs on the other hand, do. This is why 720x480 footage looks a bid 'wide' on the PC and why it should be resized to 640x480. (Well, that's the simple way. You could also do it entirely at 720x480 and make sure all your graphics are at a 10/11 ratio (Easily done by doing them at 720x540 and then scaling down to 720x480) and check marking the 4:3 tag as the aspect ratio for playback which is available in MKV, MP4 Mpeg and AVI... And probably a few others, I dunno.)
More importantly, why do you even think you can build a script to do an inverse telecine on this?
You can't. Raw anime footage is usually animated at 24fps (23.976) and was telecined (3:2 pulldown) to get it to 29.97fps for NTSC broadcast. You could have easily used an inverse telecine on the footage BEFORE you edited it and edited natively at 23.976fps.
However you
didn't and all you effects, pans, zooms and stuff are rendered at 29.97fps natively, (And I'm not sure if it's rendered at 29.97fps with both fields being a matched set or if it's 29.97fps with each field being independant and making it true 59.96 FIELDS per second. If so, that's even WORSE than just both fields being matched sets).
So no, you can't use a an inverse telecine script to return this footage to 23.967fps progressive because due to the way you edited this it's not possible. You can, at best, run a standard deinterlacing filter, leave it at 29.97fps and deal with the ghosting fromt he deinterlacing.
Unless you can go back and re-edit this the right way, no one's going to give you a script that'll take the native 29.97fps effects you did and make them 23.976fps without making decimating entire frames and making it jumpy.