Hi all,
The following code is in Encoder::configure():
//======== set pad size if width is not multiple of the minimum CU size
uint32_t maxCUDepth = (uint32_t)g_convertToBit[_param->maxCUSize];
uint32_t minCUDepth = (_param->maxCUSize >> (maxCUDepth - 1));
if ((_param->sourceWidth % minCUDepth) != 0)
{
//pad width to multiple of minCUDepth
}
...
if ((_param->sourceHeight % minCUDepth) != 0)
{
//pad height to multiple of minCUDepth
}
I had a couple of questions:
* Should minCUDepth be renamed minCUSize?
* Aren't the first two lines a convoluted way of always computing "8"?
x >> ((log2(x) - 2) - 1) = x / 2^(log2(x) - 3) = 8
* Is there any reason for maxCUDepth or minCUSize to be set via command
line or some other way instead of being implicitly computed here?
Thanks,
Matt
_______________________________________________
x265-devel mailing list
[email protected]
https://mailman.videolan.org/listinfo/x265-devel
