Hi all ,
Why H264 codec decode one frame data to next frame data in memory buffer must be continuous.
If this is CODEC restriction , have the opportunity to update by TI ?
Thanks !!
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Hi all ,
Why H264 codec decode one frame data to next frame data in memory buffer must be continuous.
If this is CODEC restriction , have the opportunity to update by TI ?
Thanks !!
Hi,
There is no such restriction from the H.264 decoder perspective. The encoded farme data need not be continuous in memory. If you pass the correct pointer at start of every frame with appropritae validBytes, the decoder will work fine.
regards
Yashwant
Hi ,
sorry I use DM365 and H264 CODEC use H264DEC.version.01.00.00.08
I set correct pointer at start of every frame with appropriate validBytes , the decoder will work slow and return error decoder use size.
thanks ~
I suspect the pointer is not correct. Hence decoder considers it error frame and takes some time in doing concealment.
Please check if the frame data contains start code prefix and the other stream part correctly. The version 1.0 codec only supports byte stream format, so start code should be part frame data provided to the the decoder.
regards
Yashwant
Hi
I have already check the frame start pointer and every frame is all correctly. but it also work error .
May I ask what version of DM365 H264 codec are you use.
And if not the version 1.0 why can I get the version you use.
thanks
You can try the latest version of decoder http://software-dl.ti.com/dsps/dsps_public_sw/codecs/DM365/index_FDS.html
But all the version of the decoder should work fine. Nevertheless, please try the new version and let us know.
regards
Yashwant
Please let me know which is the complete setup.
Which kernel version and dvsdk is suggested.
I'm using arago kernel r36 and I'm waiting for dvsdk to be released.
Thx