Opened 12 years ago

Closed 12 years ago

#470 closed technical change (fixed)

Shortcoming of lossless functionality

Reported by: felix.henry Owned by: bbross
Priority: minor Milestone:
Component: Text Version: D6 (H1003) dI/dJ/dK
Keywords: Cc: bbross, wjhan, jct-vc@…


This is not really a bug but it is rather a possible shortcoming of lossless coding at CU level.

If a CU needs to be encoded losslessly, but the residue is zero, cu_qp_delta cannot be transmitted. One may force the encoder to use another prediction mode in order to get a non-zero residue (just for the sake of transmitting cu_qp_delta) but there may be no prediction mode with any residue. In that case the block cannot be treated as lossless (for instance because DBF will be active).

Conversely, if a block needs to be encoded in a lossy way, but the predicted QP is zero and there is no residue, it is not possible to indicate that lossy coding is active and that we want the block to be filtered.

One solution can be to enforce lossless coding at slice level only, or, if one wants CU lossless granularity, to have a slice level flag that allows lossless coding in the current slice, and then, if this flag is active, an extra CU level flag for lossless coding.

Change History (3)

comment:1 Changed 12 years ago by DefaultCC Plugin

  • Cc bbross wjhan jct-vc@… added

comment:2 Changed 12 years ago by ksuehring

  • Type changed from defect to technical change

comment:3 Changed 12 years ago by bbross

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

Fixed by integration of JCTVC-I0529 in JCTVC-I1003 d2

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(Owner, Subscriber, Participant)
  • Felix Henry(Reporter)
  • jct-vc@…(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Participant, Always)
  • Woo-Jin Han(Subscriber)