FrameEncoder and compressFrame needs to be refactored for mallocs and
failures to be handled correctly.
On Thu, Sep 19, 2013 at 1:31 PM, Gopu Govindaswamy
g...@multicorewareinc.com wrote:
# HG changeset patch
# User Gopu Govindaswamy g...@multicorewareinc.com
# Date 1379577682 -19800
#
+cliopt.log(X265_LOG_ERROR, Unable to register CTRL+C handler, error
%d\n, errno);
How do you think about to retrieve a message text for the passed error code?
Would you like to call the function strerror there (and similar source
code places)?
Can you try sending this as a fresh patch to the mailing list? Does not
apply cleanly to the parent node.
On Thu, Sep 19, 2013 at 2:46 PM, Deepthi Devaki Akkoorath
deepthidev...@multicorewareinc.com wrote:
# HG changeset patch
# User Deepthi Devaki deepthidev...@multicorewareinc.com
# Date
On 9/19/2013 5:18 AM, Steve Borho wrote:
+typedef uint8_t UChar;
+typedef uint16_t UShort;
+typedef unsigned int UInt;
+typedef int64_t Int64;
+typedef uint64_t UInt64;
This seems quite wrong, since they're not necessarily analogous on
all platforms... like short.
Why not
On 9/19/2013 10:16 AM, Min Chen wrote:
+// Disabled because Frame Parallelism call processRowPost early, it is
broken data.
+// OPT(sao-lcu-opt, param-saoLcuBasedOptimization,required_argument,
0, 0: SAO picture-based optimization, 1: SAO LCU-based optimization )
... Why not fix it
I check code again, no more reduce checks
the SAO split into three parts, one run before deblock and another after, if we
disable ao-lcu-opt, we have to bypass all of SAO operators on row level, we
process sao after frame finished.
At 2013-09-19 20:05:11,Derek Buitenhuis
my 2 reasons:
1. turn it on may not get improvement quality or bitrate, but we need disable
other acceleration feature
2. Maintain a rarely used features to be increase the workload
At 2013-09-19 20:02:07,Derek Buitenhuis derek.buitenh...@gmail.com wrote:
On 9/19/2013 10:16 AM, Min Chen wrote:
