Hi , We are trying to make the simpler H.264 application on DM6467 which takes input from file and dumps the output in file.
App Flow:- h.264 720P 420P encoded file ------------->Decode---------------->File Dump 420P YUV The problem we are facing is that we see the some portions of image as corrupted were there is movement in motion. But that corruption goes when there is change of scene. See the attached corrupted.jpeg snapshot image. It again reoccurs after when there is motion. We don't see this problem in standard TI decode demo application provided with DVSDK package. Decoder parameters are same as of standard TI decode demo application. We don't understand what could be the problem. Another thing we noticed that the image pitch returned from decode processing API call is some what more that image width. (ex For 720P "1280*720" image pitch returned in 1368) .Can any one explain why this is done? We would also like to know the exact start of image from which we can take dump also what pointer should go as input and output. In H.264 user guide the buffer format is explained . Can any one explain tht image in detail? I have following questions regarding it. * Which element of displayBufs contains the pointer returned by codec? * On what basis this extra pitch is computed? Hoping for some help as I am really struck in my schedule . Regards, Siddhish Siddhish Sutaria "victory always"
_______________________________________________ Davinci-linux-open-source mailing list [email protected] http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
