Re: [x265] [PATCH] fix non-determination output after apply new preset parameter sets

2016-01-03 Thread Deepthi Nandakumar
Min, can you elaborate? Where is bestME being used uninitialised? On Fri, Jan 1, 2016 at 2:48 AM, Min Chen wrote: > # HG changeset patch > # User Min Chen > # Date 1451594594 21600 > # Node ID e5abd9b22f52fb8800068a2c699aea1648b69f54 > # Parent

Re: [x265] [PATCH] fix non-determination output after apply new preset parameter sets

2016-01-03 Thread chen
End of function, below code made bug if (!m_param->limitModes) { splitCUData.mvCost[0] = 0; // L0 splitCUData.mvCost[1] = 0; // L1 splitCUData.rdCost= 0; } else { splitCUData.mvCost[0] = md.pred[PRED_2Nx2N].bestME[0][0].mvCost; // L0

[x265] [PATCH] fix non-determination output after apply new preset parameter sets

2015-12-31 Thread Min Chen
# HG changeset patch # User Min Chen # Date 1451594594 21600 # Node ID e5abd9b22f52fb8800068a2c699aea1648b69f54 # Parent fb58aa76a9ae1eb6b0bac37f34bc418ba2ce941c fix non-determination output after apply new preset parameter sets --- source/encoder/analysis.cpp | 16