mplayer-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Original]

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


To: ivop@xxxxxxxxxx,"MPlayer usage questions, feature requests, bug reports" <mplayer-users@xxxxxxxxxxxx>
Subject: Re: [MPlayer-users] Re: Crop before deinterlacing OK?
From: Rich Felker <dalias@xxxxxxxxxx>
Date: Tue, 26 Jul 2005 00:50:44 -0400
Cc:
Delivered-to: itdp@localhost
Delivered-to: mplayer-users@mplayerhq.hu
In-reply-to: <200507260600.45675.ivop@euronet.nl>
References: <200507061108.18714.mwieser@gmx.de><20050725231952.GB319@brightrain.aerifal.cx><1122333643.17675.153.camel@draco.sault.org><200507260600.45675.ivop@euronet.nl>
User-agent: Mutt/1.3.25i

On Tue, Jul 26, 2005 at 06:00:45AM +0200, Ivo wrote:
> On Tuesday 26 July 2005 01:20, Jason Tackaberry wrote:
> > I'd be ecstatic to see MPlayer have something like this, but I have a
> > hunch there might be some architectural issues. :)
> 
> Yes, I think so. I have looked into it a few months ago (the DScaler code, 
> not what's in xinelib) and it wasn't trivial. I mean, one could convert it 
> to C and all, but IMHO it would be better to write an avisynth and/or 
> virualdub videofilter wrapper, so you get a whole bunch of filters all at 
> once (like I did for ladspa, instead of porting an audio limiter filter).
> 
> Btw why isn't there something like ladspa for video? Lots of people are 
> (re)creating and/or porting the same filters over and over again for 
> numerous applications. IMHO there should be one API for the whole lot, from 
> Adobe Premiere to Cinelerra to Kino to MPlayer.

Because all the existing APIs completely SUCK. They're full of
slowness and limitations; many use idiotic colorspaces, etc.

Rich

_______________________________________________
MPlayer-users mailing list
MPlayer-users@xxxxxxxxxxxx
http://mplayerhq.hu/mailman/listinfo/mplayer-users


[Prev in Thread] Current Thread [Next in Thread]