[MPlayer-dev-eng] Re: Moving the audio plugins to libmpcodecs - design of plugin management

[Alban Bedel]

Hi Anders Johansson,

on Wed, 19 Jun 2002 13:15:46 +0800 you wrote:

> > > > Bleh, I hope they're also nice and functional without gui...
> > >
> > > I should have said OSD or GUI. Some plugins becomes a bit hard to use
> > > without visual feedback like for example EQ and multi channel volume.
> > 
> > What I would like is the possibility for a standalone program to
> > connect to mplayer and change settings like volume, EQ, do seeks, get
> > status info etc., so you can control mplayer from a different display
> > or computer.
Easy if you don't need any kind of feedback. Just write a driver for the input layer.
See the slave mode one. It's in my TODO to add feedback in the input layer to
allow full remote control.

> > Plugins should not have GUI of OSD support hardcoded in them, but
> > instead export a list of parameters with name, type, range info, and
> > an interface to change them on-the-fly.
I agree, a common one for all libmpcodec stuff (vd/ad/vf/af/ve/ae) would be even
better.
	Albeu