IVTC PATTERN (it just make me NUTS)

[dionisos]

Somebody?
hehehe
well, lets get to the point:

2 progressives+ 1 interlaced: Thats the way it goes.

can anybody drop some lightfull words about it?

what can i do to proper decimate it?

[trbarry]

What is the frame rate?

I think I've seen this pattern only in 480p & 720p 59.94 HDTV material made from progressive 24 fps film material.

But if so then the pairs of progressive frames would be duplicates and something like SelecEvery(5,0,3) or so would give you back the film.

- Tom

[dionisos]

tanx for dropping words
The source its an NTSC (29,blabla) fps.
its an old movie (Berlim : Simphony of a City)

i guess it should be something around 20fps or so
but i cant figure out how to decimate.
i've thougt to do "changefps(30)"
them decimate @3
but it seems a little weird to set up on this fps

[manono]

Hi-

According to IMDB (http://us.imdb.com/Title?0017668), it's a silent film from 1927. Therefore the original frame rate was almost certainly less than 24fps. I think your first instinct is the best-decimate it by 3. Then look carefully through parts of it for any more duplicate frames. Silent films were made with many different frame rates, 18fps being perhaps the most common. It wasn't until sound came in that 24fps became the standard. However, if you use the AssumeFPS(30) to begin with, the audio will become slightly asynch, so you'll have to resynch it with a WAV editor.

Sounds like an interesting movie.

[dionisos]

thanx a lot
gonna try soon and post some words about it
cheers

[WarpEnterprises]

@manono: Why should the audio get out of sync by using AssumeFPS ?
This function can take more precise (float) arguments as well.
Or did you mean something else?

[ErMaC]

From what I understand AssumeFPS() is just like hexediting an AVI source and changing the framerate. It doesn't decimate or duplicate frames to maintain sync. If I AssumeFPS(48) a 24fps stream the audio will be only half done when the video finishes.

ChangeFPS() will decimate or duplicate frames to maintain sync. ConvertFPS() will blend frames to create inbetweens and will also maintain sync. AssumeFPS() doesn't.

[manono]

Hi Warp-

I have a feeling you already know the things ErMaC posted (which doesn't make them any less valuable), as I've noticed you've posted to many threads on similar subjects. I was speaking of correcting the Audio outside of AviSynth and then muxing it back to the finished .avi afterwards. But it not only needs the speed corrected, but the pitch as well, (although the difference between a speed and pitch corrected 19.980fps->20fps MP3 and just a speed corrected one probably isn't noticeable). So yes, I'd say we're probably talking about 2 slightly different things.