[x265] Poor Development Practices
Derek Buitenhuis
derek.buitenhuis at gmail.com
Tue Feb 18 19:09:01 CET 2014
On 2/18/2014 6:00 PM, Steve Borho wrote:
> I disagree; any program that used the old API can use the new one without any change because before that commit internal and input bit depth were always the same. Both before and after that commit that particular field has only served to validate that the user was aware of whether the library was compiled for 16bpp or not.
If it really is this, then the API was documented wrong, and it does
some weird things.
e.g. x265_picture_init() copies it over into the x265_picture.bitDepth field,
which sure does look like *input* depth...
> Let's keep this polite. I'll err on the side of bumping the build number in the future.
I may be somewhat grumpy due to coming back with my inbox full of people
blaming me.
- Derek
More information about the x265-devel
mailing list