Opened 14 years ago Closed 14 years ago #35 closed enhancement (fixed)Improved configurability of residual quadtree
Description
According to the residual quadtree concept, for the given CU, various TU size is evaluated in the quadtree style. In the configuration file, two parameters are given:
QuadtreeTULog2MaxSize
where they specify the maximum and minimum possible transform sizes, respectively. It is a good feature, however, it can be improved further. For example, for 64x64 PU, all transform sizes of 4x4, 8x8, 16x16, 32x32 and 64x64 are evaluated when RQT=1. It slows encoder a lot.
We suggest to add one another way to configure residual quadtree: maximum allowed depth of residual quadtree such as:
QuadtreeTUMaxDepth
If we set QuadtreeTUMaxDepth=3, 64x64, 32x32 and 16x16 are used for 64x64 CU while 16x16, 8x8 and 4x4 are used for 16x16 CU. It is helpful to reduce the encoder complexity.
It should be noted that it does not change RQT itself, but just encoder behaviour. And if we set QuadtreeTUMaxDepth sufficiently large value, it should have the same results in the previous version.
This feature is also useful in TE9 to check variable aspects of the TU structure. Change History (6)comment:1 Changed 14 years ago by fbossen
comment:2 Changed 14 years ago by wjhancomment:3 Changed 14 years ago by fbossen
Fixed in r247 comment:4 Changed 13 years ago by davidf
Updating component after adding WD (Text) tickets comment:5 Changed 13 years ago by davidf
comment:6 Changed 13 years ago by davidf
Note: See
TracTickets for help on using
tickets. | This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber, Participant
|
It was suggested to test the case disabling use of sub-tranform unit splits. This ticket should include that modification to test it.