Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Alexei_I_
Beginner
45 Views

Video Pro Analyzer: a bug (analysis of H.264 stream)

It seems that indexing of the non-zero coefficients and sign flags is not right when a block is analyzed (H.264): in all cases the last non-zero coefficient is skipped in the analysis pane, and the other non-zero coefficients are counted in a straight forward way without skipping the non-zero coefficients as it should be according to section  7.3.5.3.3 Residual block CABAC syntax.

Here is an excerpt:

373        145        coded_block_flag             1

257        145        significant_coeff_flag[0]               1

304        291        last_significant_coeff_flag[0]      0

292        242        significant_coeff_flag[1]               1

380        181        last_significant_coeff_flag[1]      0

476        362        significant_coeff_flag[2]               0

284        56           significant_coeff_flag[3]               0

368        112        significant_coeff_flag[4]               0

402        224        significant_coeff_flag[5]               0

466        448        significant_coeff_flag[6]               1

376        305        last_significant_coeff_flag[6]      1

270        128        coeff_abs_level_minus1[2]           0  (indices below should be 6, 1, 0, but not 2,1,0)

257        128        coeff_sign_flag[2]           0

257        256        coeff_abs_level_minus1[1]           4

374        225        coeff_sign_flag[1]           1

374        76           coeff_abs_level_minus1[0]           0

504        152        coeff_sign_flag[0]           0

0 Kudos
5 Replies
Alexey_F_Intel
Employee
45 Views

Appreciate your report!

Alexei_I_
Beginner
45 Views

I do not see any updates since November 3, 2015 (!), i.e. ~4 months.

I wonder if this bug was ever considered? It seems that even product pre-sales support people did not elevate the issue although I notified them about it.

 

 

Jeffrey_M_Intel1
Employee
45 Views

I'll sync with the developer team and update you soon.

Regards, Jeff

Jeffrey_M_Intel1
Employee
45 Views

According to our records, this issue was fixed in the 2.1.0 release of VPA, which is the most recent release.  Please let us know if you're still seeing the issue with this version.

Alexei_I_
Beginner
45 Views

Jeffrey, thank you for the heads up. I hope the new release is available for download as a trial version.