changefps vs pulldown

45tripp · Dolphin Blue Joined: 21 Dec 2004 Location: Triptonia

hi,

I have an avi with 23.976 progressive xvid content.
I've been converting samples to mpeg2.
When converting with CCE i get the following:

45tripp · Dolphin Blue Joined: 21 Dec 2004 Location: Triptonia

the 4 frame sequence I guess goes aa, ab, bc, cc.

Whereas if I feed it with avisynth using changefps()
One gets the below which I suppose is a, b, b, c.

Obviously when freezing frames and looking at them on a pc it's better looking at the below but what's better for encoding, using pulldown or changefps?
for viewing as final product on DVD?

guns1inger · Member Joined: 01 Apr 2004 Location: Miskatonic U

Pulldown. Encode as 23.976, then apply pulldown (or let CCE do it while encoding), then author. Your playback hardware will do a much better job at creating the missing frames than you will do in software.
_________________
The views expressed in this post are mine alone, unless plagiarised from others
Read my new blog here

45tripp · Dolphin Blue Joined: 21 Dec 2004 Location: Triptonia

I suspected as much.

Some encoders produce results like changefps(). (mainconcept)
Drawback?
Should each encoder be able to produce both results? (settings)
Or are you to encode to 23.976 and use external pulldown software for such encoders?

How do you pulldown in avisynth?

ty

jagabo · Member Joined: 09 Dec 2005 Location: none

45tripp · Dolphin Blue Joined: 21 Dec 2004 Location: Triptonia

manono · Member Joined: 28 Aug 2003

Hi-

Are all pulldown options equal?

I've never used MainConcept, but if you're asking if 2:3 pulldown is about the same as 3:2 pulldown, then for all intents and purposes, yes. 2:3 pulldown is far and away the most commonly used, though.

It seems simple enough but would you prefer to have your authoring program flag the
pulldown rather than the encoder?

Either do it during the encoding phase, or apply pulldown afterwards using DGPulldown or Pulldown.exe. I do it afterwards. Personally, I'd be hesitant about letting any authoring program do it for me. It's liable to want to reencode the entire thing, since you're feeding it a non-compliant video.

All you can do in avisynth is change framerate and convert 23.976 to 29.97 interlaced?
What is assumefps?

You can do a lot in AviSynth. ChangeFPS, ConvertFPS, or even hard telecine a perfectly good progressive video. AssumeFPS changes the length of the video (and creates out-of-synch audio unless you stretch it) by adjusting the framerate, at the same time keeping the number of frames constant. You know, you could read up on these things yourself, and get the answers more quickly:

http://avisynth.org/index.php?page=FPS

guns1inger · Member Joined: 01 Apr 2004 Location: Miskatonic U

I haven't used an authoring tool that applies pulldown. Most I have used refuse to load 23.976 fps source if it doesn't have the pulldown already applied, as it isn't compliant without it. CCE's pulldown seems to be very good, and so far I have had no problems with it. Ditto for ProCoder. But there is always DGPulldown to fall back on if you have doubts or a healthy level of paranoia.
_________________
The views expressed in this post are mine alone, unless plagiarised from others
Read my new blog here

manono · Member Joined: 28 Aug 2003

I was wondering about that. The authoring programs I use won't take a progressive 23.976fps video either, but I haven't used all that many different ones, so I wasn't sure about some of the others. Thanks.

guns1inger · Member Joined: 01 Apr 2004 Location: Miskatonic U

NTSC for DVD is 29.970 fps. That can be either 29.970 actual frames per second - as in NTSC video - or come from pulldown. So you source can be 23.976 with 2:3 or 3:2 pulldown, or it could even be 720 x 480 @ 25 fps, with pulldown applied to reach 29.970. This last option is often used when doing PAL to NTSC conversion. The hardware then takes care of how it should be displayed.
_________________
The views expressed in this post are mine alone, unless plagiarised from others
Read my new blog here

Pinstripes23 · Member Joined: 25 Aug 2004 Location: United States

DVDLab Pro will warn you then do pulldown for you if you import a 23.976fps mpv file into the assets section. I accidentially discovered this when I forgot to run dgpulldown on the file after encoding. I just let dvdlab do it this one time on this file and had no problems with playback. But for the most part I use dgpulldown.

guns1inger · Member Joined: 01 Apr 2004 Location: Miskatonic U

That's right - it does. I had forgotten because I just do it as a matter of course long before I get to authoring.
_________________
The views expressed in this post are mine alone, unless plagiarised from others
Read my new blog here

AlanHK · Member Joined: 25 Apr 2006 Location: Hong Kong

guns1inger · Member Joined: 01 Apr 2004 Location: Miskatonic U

Even What is DVD, our first point of reference, doesn't mention VCD @ 23.976 being compliant.

As I can't actually stand VCD resolution, I don't encode or author with it, so it's never been an issue.
_________________
The views expressed in this post are mine alone, unless plagiarised from others
Read my new blog here

AlanHK · Member Joined: 25 Apr 2006 Location: Hong Kong

45tripp · Dolphin Blue Joined: 21 Dec 2004 Location: Triptonia

guns1inger · Member Joined: 01 Apr 2004 Location: Miskatonic U

There should be no difference. I remember using the DLP pulldown function beck when I started encoding NTSC material. I had no idea what it was for back then. Then along cam DGPulldown, which allowed me add pulldown outside any particular authoring tool, which made the it easier to produce universally acceptable video.

Now I just let ProCoder/CCE do it, and have no problems. I haven't tested the latest HCEnc fully yet, so I don't know if the bugs have been ironed out there. If not, DGPulldown is the perfect solution.

I believe the pulldown done by DLP is sound, so don't be put off.
_________________
The views expressed in this post are mine alone, unless plagiarised from others
Read my new blog here