Hi Michael, On Wed, Jun 1, 2011 at 3:42 AM, rukhsana afroz <[email protected]>wrote:
> Hi Michael, > >> maybe jaspers and ours advance the pointer at a slightly different >> spot in the implementation >> >> > As per the discussion on IRC chat, I checked where s->bit_index gets > modified. I see, in our decoder that s->bit_index has been manually set to 8 > at the beginning of decoding packet. whereas, in jasper, I did not see this. > Also, jasper always reads the entire byte to check present bit even for > other files, like file1.jp2 etc. Whereas, our decoder does not do so. I need > your suggestion on this as i do not find any clue in the doc for this. I am > waiting for you on the IRC chat. > > > > > I have rebased the codebase against ffmpeg and also decode_packet function works properly comparing with jasper. However, it gets segmentation fault somewhere in decode_cblk function for adding new code. Tomorrow I will be in chat to discuss this code. My new code rebased with ffmpeg is in: https://github.com/rukhsana/ffmpeg_j2k Thanks > -- > Rukhsana Ruby Phd Student Department of Electrical & Computer Engineering The University of British Columbia ============================
_______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
