- Timestamp:
-
Jan 6, 2015, 7:07:50 PM (10 years ago)
- Author:
-
ksuehring
- Comment:
-
Legend:
- Unmodified
- Added
- Removed
- Modified
-
initial
|
v1
|
|
1 | 1 | Which version of the standard document are you looking at. I think, this has been addressed in the defect report (JCTVC-Q1001), which is also included in the second edition. The modified text defines (semantics of au_cpb_removal_delay_minus1): |
2 | 2 | |
3 | | The variables AuCpbRemovalDelayMsb and AuCpbRemovalDelayVal of the current picture are derived as follows: |
4 | | – If the current access unit is the access unit that initializes the HRD, AuCpbRemovalDelayMsb and AuCpbRemovalDelayVal are both set equal to 0. |
| 3 | > The variables AuCpbRemovalDelayMsb and AuCpbRemovalDelayVal of the current picture are derived as follows: |
| 4 | > – If the current access unit is the access unit that initializes the HRD, AuCpbRemovalDelayMsb and AuCpbRemovalDelayVal are both set equal to 0. |
5 | 5 | |
6 | 6 | I think that solves the problem that you are seeing. |
| This list contains all users that will be notified about changes made to this ticket. These roles will be notified: Reporter, Owner, Subscriber, Participant - Alex Bishop(Reporter, Participant)
- Benjamin Bross(Subscriber)
- jct-vc@…(Subscriber)
- karl.sharman@…(Always)
- Karsten Suehring(Participant, Always)
- Woo-Jin Han(Subscriber)
|