[MPlayer-dev-eng] [PATCH] ffw-av - interactive fastforward/slow with audio speed adjust (1st draft)

[Jan Knutar]

On Wednesday 13 October 2004 23:56, Alexander Strasser wrote:
> A good
> portion of features were fighting against each other in the past and I'm
> not in mplayer development such a long time. So I vote for not applying
> patches because they sound fancy without some1 having really checked them.
> And until that will happen it is best for the users that want to have
> that feature to get the patch and test for themselves.

Inspired by someone's suggestion of WOLK equivalent for MPlayer (applying as many
patches as possible while still maintaining functionality), I tried that for awhile, keeping my
own tree. However, as free time decreased, and the number of patches making it into CVS
increased, my own tree now only differs by 41K. During the course, I've discovered a few
patches which introduced bad behaviour, and posted that to mailing list. In the end, I discovered
that mplayer CVS tree is pretty well managed after all, and that my own rapid applying of patches
tree doesn't really provide much benefit.

My current tree, merged with CVS, holds the following patches:

20.exit.patch (Probably in CVS now)
aspect_for_vf_expand-B1-mplayer-1.0pre5.diff
*lavc_dummy_frames_2.patch (not in CVS afaik)
MPlayer-1.0pre5-iterative_seek. patch
'MPlayer-1.0pre5-no_zero_length_ keyframes.patch
MPLAYER-AUDIO-DISPLAY-PATCH
'MPLAYER-END-OF-SOUND-PATCH
MPLAYER-INPUT-PATCH
MPLAYER-SEEK-PATCH
ofmpeg_configurable_blocksize3.patch (to be replaced by Nico Sabbi's (sp?) patch)
patch-MPlayer-alsa-chunk-size
*and polarworlf's mga_vid patches

Some of those might be in CVS already.

Those marked with * are ones I personally think should be applied to CVS immediately.

The major work is testing, testing, testing. (I wish Ballmer made a performance with that!). :P