Jason Tackaberry wrote: > On Sun, 2008-04-06 at 10:52 +0200, Duncan Webb wrote: >> | <file id="file1">Batman_Dead_End.mpg >> | <mplayer> >> | <option name="vf" value="crop=704:272:8:102"/> >> | <option name="vf" value="scale=720:576"/> >> | </mplayer> >> | </file> > > For common options (crop, scale, deinterlace, gamma correction), it'd be > better if these things where generic options that had specific > implementations in the backend, as opposed to tying options to a > specific player. > > I'm thinking more about freevo 2 compatibility here.
I thought about this, but it does have one big problem, when mplayer, xine or vlc changes options then the code need changing and then it become dependent on the version of the player used. An advantage is it move the responsibility of correct options from the developers to the users :-) I was only an example, as crop detection is already built into "freevo cache" but nothing happens with the results and it is turned off by default. As you say common options it should be quite practical to have stuff like: | <file id="file1">Batman_Dead_End.mpg | <deinterlace value="on"/> | <mplayer> Gamma correction needs to be an event driven setting while the player is running so that the changes can be seen and it possible needs doing for a directory tree, most TV recordings will need the same gamma corrections. Duncan ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Register now and save $200. Hurry, offer ends at 11:59 p.m., Monday, April 7! Use priority code J8TLD2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ Freevo-devel mailing list Freevo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-devel
