[MPlayer-users] Re: [-] Crop before deinterlacing OK? NOSPAM

[Rich Felker]

On Mon, Jul 18, 2005 at 10:19:03AM -0700, RC wrote:
> On Mon, 18 Jul 2005 15:03:46 +0200
> Guillaume POIRIER <poirierg at gmail.com> wrote:
> 
> > Now, if you do not set the correct output framerate with "-ofps",
> > you'll either end-up with duplicate frames if you output with -ofps
> > 30000/1001 and your ivtc source is at 24000/1001 fps,
> 
> That's an acceptable situation, IMHO.  It would be far better if
> mplayer could output variable FPS files, or auto-detect content and
> change the filters/ofps appropriately.  Since it can't, there aren't
> many good alternatives.
> 
> How about using "-ofps 120000/1001"  :-)

Be aware this will use about 50 megs per hour in overhead because the
avi format sucks. Otherwise it will work. Just make sure you don't use
harddup, btw... :)

> > So please-please-please, identify your source before launching the
> > encoding process.
> 
> It would certainly be preferable if it was always possible.  With live
> TV capture, you really don't have any way to be sure what you are going
> to get.

Record (near-)lossless, keeping the original interlacing. Reencode
later to make a proper copy at reasonable size.

> You COULD capture interlaced (or with tfields) and convert the file
> later, but surely that's more hassle than most people would be willing
> to go through.

Hey, it's not easy to encode video.

Rich