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/027134.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 parameterMåns Rullgård mru
Sun Jan 7 19:04:36 CET 2007
Robert Swain <robert.swain at gmail.com> writes:

> 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.

Applied.

-- 
M?ns Rullg?rd
mru at inprovide.com


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