From: James Almer <jamrial@gmail.com> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v1 03/13] lavc/hevc_ps: Add SPS/PPS parse support for HEVC extension syntax Date: Thu, 1 Dec 2022 22:22:36 -0300 Message-ID: <4f80073c-c925-a1d1-75d0-3f697982bc47@gmail.com> (raw) In-Reply-To: <20221201081408.2194579-3-fei.w.wang@intel.com> On 12/1/2022 5:13 AM, Fei Wang wrote: > +static void colour_mapping_octants(GetBitContext *gb, HEVCPPS *pps, int inp_depth, > + int idx_y, int idx_cb, int idx_cr, int inp_length) > +{ > + uint8_t split_octant_flag, coded_res_flag; > + uint16_t part_num_y, res_coeff_q, res_coeff_r; > + int bit_depth_cm_input_y, bit_depth_cm_output_y, cm_res_bits; > + int k, m, n, c, i, j; > + > + part_num_y = 1 << pps->cm_y_part_num_log2; > + > + if (inp_depth < pps->cm_octant_depth) > + split_octant_flag = get_bits1(gb); > + > + if (split_octant_flag) > + for (k = 0; k < 2; k++) > + for (m = 0; m < 2; m++) > + for (n = 0; n < 2; n++) > + colour_mapping_octants(gb, pps, inp_depth + 1, > + idx_y + part_num_y * k * inp_length / 2, > + idx_cb + m * inp_length / 2, > + idx_cr + n * inp_length / 2, > + inp_length / 2); > + else > + for (i = 0; i < part_num_y; i++) { > + for (j = 0; j < 4; j++) { > + coded_res_flag = get_bits1(gb); > + if (coded_res_flag) > + for (c = 0; c < 3; c++) { > + res_coeff_q = get_ue_golomb_long(gb); > + bit_depth_cm_input_y = 8 + pps->luma_bit_depth_cm_input_minus8; > + bit_depth_cm_output_y = 8 + pps->luma_bit_depth_cm_output_minus8; > + cm_res_bits = FFMAX(0, 10 + bit_depth_cm_input_y - bit_depth_cm_output_y - > + pps->cm_res_quant_bits - (pps->cm_delta_flc_bits_minus1 + 1)); > + res_coeff_r = get_bits(gb, cm_res_bits); cm_res_bits can be zero, and you can't call get_bits() to read zero bits. I can't say if that will fix the issue Michael mentioned, but it still needs to be fixed. > + if (res_coeff_q || res_coeff_r) > + skip_bits1(gb); > + } > + } > + } > +} _______________________________________________ ffmpeg-devel mailing list ffmpeg-devel@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-devel To unsubscribe, visit link above, or email ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2022-12-02 1:22 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-01 8:13 [FFmpeg-devel] [PATCH v1 01/13] lavc/hevc_ps: remove profile limitation of pps_range_extensions() Fei Wang 2022-12-01 8:13 ` [FFmpeg-devel] [PATCH v1 02/13] lavc/avcodec: Add HEVC Screen Content Coding Extensions profile Fei Wang 2022-12-01 8:13 ` [FFmpeg-devel] [PATCH v1 03/13] lavc/hevc_ps: Add SPS/PPS parse support for HEVC extension syntax Fei Wang 2022-12-02 0:21 ` Michael Niedermayer 2022-12-02 0:58 ` Wang, Fei W 2022-12-02 5:06 ` Michael Niedermayer 2022-12-02 1:22 ` James Almer [this message] 2022-12-02 1:52 ` James Almer 2022-12-05 6:11 ` Wang, Fei W 2022-12-01 8:13 ` [FFmpeg-devel] [PATCH v1 04/13] lavc/hevcdec: Add slice parse support for HEVC SCC extension Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 05/13] lavc/hevcdec: Fix the parsing for use_integer_mv_flag Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 06/13] lavc/hevcdec: Set max_num_merge_cand to uint8_t Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 07/13] lavc/hevc: Update reference list for SCC Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 08/13] lavc/vaapi_hevc: Pass SCC parameters Through VA-API Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 09/13] lavc/vaapi_hevc: Add vaapi profile parse support for SCC Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 10/13] lavc/vaapi_hevc: Set correct rps type for scc Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 11/13] lavc/vaapi_hevc: Loose the restricts for SCC decoding Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 12/13] avcodec/hevcdec: Replace number with enum Fei Wang 2022-12-01 8:14 ` [FFmpeg-devel] [PATCH v1 13/13] lavc/vaapi_hevc: Remove duplicate code Fei Wang
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=4f80073c-c925-a1d1-75d0-3f697982bc47@gmail.com \ --to=jamrial@gmail.com \ --cc=ffmpeg-devel@ffmpeg.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel This inbox may be cloned and mirrored by anyone: git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \ ffmpegdev@gitmailbox.com public-inbox-index ffmpegdev Example config snippet for mirrors. AGPL code for this site: git clone https://public-inbox.org/public-inbox.git