[x265] [PATCH RFC] api: add support for float or rational FPS [API CHANGE]

[Steve Borho]

On Tue, Feb 18, 2014 at 9:53 AM, Tim Walker <tdskywalker at gmail.com> wrote:

> On 18 Feb 2014, at 08:44, Steve Borho <steve at borho.org> wrote:
>
> > # HG changeset patch
> > # User Steve Borho <steve at borho.org>
> > # Date 1392704518 21600
> > #      Tue Feb 18 00:21:58 2014 -0600
> > # Node ID 3512dec4936ea2d6346587ede59b61e3c5c1b3c9
> > # Parent  8571d160aedb00e07a3f47016f04d8d9aeaa5856
> > api: add support for float or rational FPS [API CHANGE]
>
> No idea on the implementation, but please do switch to rational FPS. I've
> never seen anything use an integer for that, even the "worse" APIs have a
> floating-point field for that.
>

Yeah, this is one of those HMisms that probably should have been fixed a
long time ago.

As to the implementation, I'm pretty sure the cuTree timebase calculation
is still wrong, I need to dig through that today.

-- 
Steve Borho
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/x265-devel/attachments/20140218/bb644af4/attachment.html>