Open QSXW opened 1 month ago
linux is not build able. 16 files in conformance/failed/v1/PAL/ will fail. Could you help make it all passed? thank you
+++++++++ report +++++++++ passed files: PALETTE_A_Alibaba_2.bit PALETTE_B_Alibaba_2.bit PALETTE_C_Alibaba_2.bit PALETTE_D_Alibaba_2.bit PALETTE_E_Alibaba_2.bit mismatch files: 8b444_A_Kwai_2.bit 10b422_J_Sony_5.bit 8b422_J_Sony_5.bit 10b422_L_Sony_5.bit 8b422_L_Sony_5.bit ACT_A_Kwai_3.bit 10b422_H_Sony_5.bit 8b422_H_Sony_5.bit 8b422_I_Sony_5.bit 10b422_I_Sony_5.bit 10b422_K_Sony_5.bit 8b422_K_Sony_5.bit 10b422_G_Sony_5.bit 8b422_G_Sony_5.bit 8b444_B_Kwai_2.bit decode_err files: ACT_B_Kwai_3.bit
total = 21, passed = 5, skipped = 0, failed = 16
Sure. It's funny that I didn't test Alibaba_2.bit samples but they passed and other failed.
I've checked all the pixels decoded by palette prediction are the same. The yellow rect on the right is the only difference that our first frame will decode twice and other pixels are identical.
The difference may occur in the stage of intra-prediction or IBC prediction. Can you help verify that?
I compare the whole frame by YUVViewer and found that the Y is almost the same, but there are some differences between the u and v components.
sure, I will check it
@QSXW , I know why other clips are failed. the Deblock, SAO, and ALF codes need to be added.
@QSXW , I know why other clips are failed. the Deblock, SAO, and ALF codes need to be added.
Yes, it is. Do we have an interface to get the cu by x0,y0? We need to get cu_q and cu_p for getting the pred_mode?
you can use fc->tab.cpm
I think I've filtered out all the flaky fuzz failures now so these appear to be legitimate.
thank you @QSXW , will check it this week end.