[MPlayer-dev-eng] filter policy clarification / suggestion

[Andrew Mahone]

On 10/27/06, Michael Niedermayer <michaelni at gmx.at> wrote:
> i see no reason or sense in completely forbidding external file usage
> in filters,
> storing and loading specific frames from a rawfile or pipe could be
> used for building non linear filter chains with the current filter
> system, combined with vf_geq this would allow pretty interresting stuff
>
> for dumping timestamps, crop coordinates and such though i am against
> using fopen() fwrite() in a filter
> there also is no issue with multiple instances, just prefix the messages
> by the filter context pointer [0xDEADBEEF] style its guranteed to be unique
>
> [...]

I think this seems generally reasonable. When I can get together in my
head how to go about it, I'll start on the two-pass filmdint, using a
log file. If the consensus goes against that, once more developers
have spoken up, it shouldn't be hard to change it to dump to stdout or
stderr on pass 1 and read from stdin on pass 2.

The tcdump filter could still be useful with console output, so I'll
rework it along those lines once filmdint is working to my
satisfaction.

-- 
Andrew Mahone
andrew DOT mahone AT gmail DOT com