A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://ffmpeg.org/pipermail/ffmpeg-devel/2007-January/026965.html below:

[Ffmpeg-devel] [PATCH] x264 interface: bidirectional motion estimation parameter

[Ffmpeg-devel] [PATCH] x264 interface: bidirectional motion estimation parameter [Ffmpeg-devel] [PATCH] x264 interface: bidirectional motion estimation parameterRobert Swain robert.swain
Tue Jan 2 23:55:40 CET 2007
Loren Merritt wrote:
> On Tue, 2 Jan 2007, Robert Swain wrote:
> 
>> I noticed that the bidirectional motion estimation parameter was never 
>> added the the x264 interface in FFmpeg so here is a small patch to add 
>> it.
>>
>> Usage: -flags2 +bime
> 
> There already is an equivalent lavc variable: bidir_refine
> x264's is a boolean and not an int because I tried all 4 values of 
> lavc's version and found bidir_refine=2 to be by far the best on a 
> speed-quality curve, so I didn't implement the other values.

Right you are. That parameter slipped under my nose. The attached patch uses 
bidir_refine >0 to mean bime enabled, else disabled.

Rob
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: ffmpeg_x264_bime.1.diff
URL: <http://lists.mplayerhq.hu/pipermail/ffmpeg-devel/attachments/20070102/845b5c5a/attachment.txt>

More information about the ffmpeg-devel mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4