Hi Rukhsana, On Sat, Apr 23, 2011 at 2:59 PM, rukhsana afroz <[email protected]> wrote: > Here, I have attached a patch, code block style of which I have tested. Page > number in the spec is 115 (D.5) for this code block style. This codeblock > style checks whether the bitplane is decoded correctly in every cleanup > pass. I have found a file which has this code block style. In fact, some bit > plane is correctly decoded and some bit plane is not correctly decoded and > my code correctly checks this.
Which bit planes are decoded correctly? And especially, how many out of how many? Are 99 out of 100 decoded correctly? Or 1 out of 10? Don't forget, the end-of-plane marker is 4 bits set to 1. For every 4 bits, the chance is pow(0.5, 4) that each bit is set, from a random perspective. Therefore, if 1 out of 10 is decoded correctly, your code is likely incorrect. However, if 99 out of 100 are correct, your code may well be correct but you're hitting some corner case that doesn't make it work. either way, you need to compare further to make sure that we're on the right track. > Also, I have checked the register values with > the reference codec jasper. I found in the middle somewhere, bit plane is > not decoded correctly. I am checking this too. However, as for my > qualification task, is it enough? Or do you want me to do something more? How does it compare to the reference decoder? Are there blocks that are being decoded correctly now for files that previously decoded incorrectly? I've told you before, I need to see some data where you're attempting to decode an actual jpeg2k file using your decoder versus the reference decoder, then show me what values are being read in your decoder versus the reference decoder, so we can assess whether your decoder is doing the right thing. Ronald _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
