View Single Post
Old 5th November 2016, 02:42   #2  |  Link
FancyMouse
Registered User
 
Join Date: Sep 2014
Posts: 12
Definitely not fault of h265 - it has various ways to get to a precise resolution. MinCbSize controls the minimum granularity of decoded picture (could be smaller than Ctb size, and last row/column of Ctb can span across boundary of picture). conformance window data in SPS can further restrict decoded picture to some output picture size (could be any size as long as chroma subsampling can still be well defined).

Seeing that 2176 is the smallest multiple of 32 to fit 2160, probably the encoder you're using is simply not supporting Ctbs crossing the boundary of decoded picture. If you can specify ctb size and if you specify it to be 16, then my guess is it may be able to produce 2160.
FancyMouse is offline   Reply With Quote