Opened 12 years ago

Closed 12 years ago

#758 closed defect (fixed)

cu_transquent_bypass_flag for subsequent IPCM blocks

Reported by: sunnykr Owned by: bbross
Priority: minor Milestone: D8
Component: Text Version: D8 (J1003) d7
Keywords: Cc: bbross, wjhan, jct-vc@…


cu_transquent_bypass_flag syntax is for lossless coding, indicating whether transform, quantization, and filtering are bypassed for each CU. Although cu_transquent_bypass_flag should be set for each CU, we don't have any mechanism to set cu_transquent_bypass_flag of the subsequent IPCM blocks. I was wondering how that was possible in the current syntax structure.

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 kchono

If your intention is to disable in-loop filtering on IPCM blocks, you can set pcm_loop_filter_disable_flag in SPS to 1. Then in-loop filtering is disabled for IPCM blocks regardless of their associated cu_transquent_bypass_flag values.

Otherwise, if your encoder needs to send cu_transquant_bypass_flags in order to indicate the associated blocks are lossless for some purpose, your encoder can set num_subsequent_pcm to 0 even if the subsequent block is IPCM. Then you can send cu_transquent_bypass_flag in the subsequent IPCM block.

comment:3 Changed 12 years ago by bbross

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

This is fixed in JCTVC-K1003_v2 with removal of num_subsequent_pcm

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)
  • jct-vc@…(Subscriber)
  • karl.sharman@…(Always)
  • Karsten Suehring(Always)
  • Keiichi Chono(Participant)
  • Woo-Jin Han(Subscriber)