On Tue, 2006-10-10 at 18:55 +0200, Dirk Meyer wrote:
> kaa.beacon has some idea if the content is interlaced or not. This
> could be wrong, but it is still an idea. It works for avi and it can
> read the progressive flag. If freevo thinks the content is interlaced,
> it can tell popcorn to deinterlace. But the user always has a way to
> set deinterlace=False on ui level.
Sounds good. And agreed, the user should have a UI-accessible method to
set deinterlacing for a file.
> So you insert the FOO_FILTER only mplayer has to the generic filter
> chain. Xine will ignore it, but we should still support to add stuff
> to the generic chain.
Right, and 'stuff' should be abstracted to work across all backends when
possible, such as with the generic 'deinterlace' filter.
> OK, so it could be append_filter and stream_append_filter. But what
> happens at the next file? Same filter? No filter?
Well, if we have two separate methods like that, then the behavior is
apparent. Maybe we could model it after Signal, so like append_filter
and append_filter_once. Alternatively we could have a persist kwarg,
and any filter added with persist=True is applied to all streams played
by that player instance until it is explicitly removed. I might prefer
to have separate methods.
> OK. The question is how to configure a driver. Maybe
>
> | set_video_device('mga,vidix')
> | configure_video_device('mga', options='xy', filter='blurr')
Looks ok. What's filter='blurr' though?
Jason.
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Freevo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/freevo-devel
