Opened 4 years ago
Closed 4 years ago
#1210 closed defect (fixed)
Editorial issue in 8.5.2.9
Reported by: | chhuanb | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | spec | Version: | |
Keywords: | Cc: | ksuehring, bbross, XiangLi, fbossen, jvet@… |
Description
It looks that in subclause 8.5.2.9, step 3 and step 4 should be merged into one bullet.
Current spec:
- If both availableFlagLXA and availableFlagLXB are equal to 1 and mvLXA is not equal to mvLXB, availableFlagLXCol is set equal to 0.
- Otherwise, the following applies:
Suggest:
- If both availableFlagLXA and availableFlagLXB are equal to 1 and mvLXA is not equal to mvLXB, availableFlagLXCol is set equal to 0. Otherwise, the following applies:
Change history (3)
comment:1 follow-up: ↓ 2 Changed 4 years ago by jlchen
comment:2 in reply to: ↑ 1 Changed 4 years ago by chhuanb
Replying to jlchen:
Thanks for the suggestion. How do you think merging them as follows:
- The availability flag availableFlagLXCol and the temporal motion vector predictor mvLXCol are derived as follows:
– If both availableFlagLXA and availableFlagLXB are equal to 1 and mvLXA is not equal to mvLXB, availableFlagLXCol is set equal to 0.
– Otherwise, the following applies:
......
The changes look ok to me.
comment:3 Changed 4 years ago by jlchen
- Resolution set to fixed
- Status changed from new to closed
The changes will be included in JVET-S2001-vE release.
Note: See TracTickets for help on using tickets.
Thanks for the suggestion. How do you think merging them as follows:
– If both availableFlagLXA and availableFlagLXB are equal to 1 and mvLXA is not equal to mvLXB, availableFlagLXCol is set equal to 0.
– Otherwise, the following applies: