This is challenging :/

Keeper of Hellfire · Post by **Keeper of Hellfire** » Mon Jan 29, 2007 2:30 pm

Do I understand it right? You try to deinterlace a finished AMV, which got resized while it was interlaced? And you decimate it too?

That sample that you did post is doomed. It makes AviSynth crash if I use TFM, which I wanted to suggest either. No matter if I convert it to Lagarith instead using the XviD.

Minion · Post by **Minion** » Mon Jan 29, 2007 3:54 pm

it made VDM crash, or it actually made avisynth crash?
the script ran for me, but it just made the footage choppy

Keeper of Hellfire · Post by **Keeper of Hellfire** » Mon Jan 29, 2007 3:58 pm

It made AviSynth crash.

If the footage becomes choppy, don't decimate and work with 29.97 fps

Minion · Post by **Minion** » Mon Jan 29, 2007 4:08 pm

exactly how this was setup:
any 720x480 source was cropped to 640x480
640x480 sources were left alone
widescreen stuff got boarders and lanczosresize to make them 640x480
all footage i edited with was interlaced. ya. not doing that again

DJ_Izumi · Post by **DJ_Izumi** » Mon Jan 29, 2007 4:13 pm

Minion wrote:any 720x480 source was cropped to 640x480

Aspect ratio fail. LOL

Minion · Post by **Minion** » Mon Jan 29, 2007 4:15 pm

it was actual 720x480. and the final export is 640x480. gtfo, kthnx

DJ_Izumi · Post by **DJ_Izumi** » Mon Jan 29, 2007 4:18 pm

You resize 720x480 to 640x480 to get a correct 1:1 PAR for PC viewing. If you just crop you're leaving it stretched out slightly (And foolishly)

Keeper of Hellfire · Post by **Keeper of Hellfire** » Mon Jan 29, 2007 4:25 pm

Kariudo's scripts works for me too. AviSynth crashes if I take out the PP=7 parameter or set it to 6 (which equals the default). With other PP it works too. Strange, if I work with DVD footage, it works with the default setting.

Minion · Post by **Minion** » Mon Jan 29, 2007 4:25 pm

Minion wrote:it was actual 720x480

square pixel.

post a script to help, or gtfo troll

DJ_Izumi · Post by **DJ_Izumi** » Mon Jan 29, 2007 4:47 pm

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.