Custom Query (1442 matches)
Results (52 - 54 of 1442)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #1430 | fixed | TComPicYuv.cpp possible memory leak | kolya | |
| Description |
It is possible to set to NULL valid pointer in HM-16.7. It seems it is better to check if they points to allocated memory. See the patch attached. |
|||
| #1429 | fixed | cfg_DisplayPrimariesCode fix | lenchik | |
| Description |
Issue reported in JCTVC-V0063 and m37008 is fixed but attached patch. An example of cfg file suitable for proper encoding MPEG's HDR&WCG CfE materials is attached. |
|||
| #1428 | fixed | there seems to be a typo about anticlockwise_rotation | jk73.kim | |
| Description |
In "D.3.17 Display orientation SEI message semantics" (pp.311 in H.265-201504), there is an example in NOTE. Because anticlockwise_rotation is u(16), 0x8000000 should be chaged to "0x8000". The example, "the combination of having both hor_flip and ver_flip equal to 1 with anticlockwise_rotation equal to 0 can alternatively be expressed by having both hor_flip and ver_flip equal to 1 with anticlockwise_rotation equal to 0x8000000" seems to be changed to "the combination of having both hor_flip and ver_flip equal to 1 with anticlockwise_rotation equal to 0 can alternatively be expressed by having both hor_flip and ver_flip equal to 0 with anticlockwise_rotation equal to 0x8000". Thanks. |
|||
