Opened 9 years ago

Closed 6 years ago

#1428 closed defect (fixed)

there seems to be a typo about anticlockwise_rotation

Reported by: jk73.kim Owned by:
Priority: minor Milestone: v5
Component: RExt text Version: v4 (12/2016)
Keywords: Cc: davidf, joel, teruhiko, jct-vc@…

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.

Change History (2)

comment:1 Changed 7 years ago by bbross

  • Milestone set to v5
  • Version changed from RExt D7 (Q1005) v8 to v4 (12/2016)

Agreed by the authors of the AHG2 report JCTVC-AD0002 (checked 2016/12 release of the HEVC specification).
Fix:
In D.3.17, the NOTE, change both instances of "0x8000000" to "0x8000".

comment:2 Changed 6 years ago by bbross

  • Resolution set to fixed
  • Status changed from new to closed

fixed in v5 (2018/02)

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

  • Benjamin Bross(Participant)
  • David Flynn(Subscriber)
  • jct-vc@…(Subscriber)
  • JK Kim(Reporter)
  • Joel(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Teruhiko Suzuki(Subscriber)