Returned size value sometimes incorrect with i.MX53 VPU API decoding

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Returned size value sometimes incorrect with i.MX53 VPU API decoding

486 Views
torus1000
Contributor V


Hi,

When I call vpu_DecGetBitstreamBuffer() after one frame decoded,
returned size value was sometimes less than actual decoded data size.
This issue continuously observed in several frames.

In such case I confirmed BitstreamBuffer always included whole frame data.

(Q1) How to decide the size of vpu_DecGetBitstreamBuffer()?

(Q2) Which kind of miscalculation cases assumed for above size unmatch(shortage)?

Can anyone help me?

Thanks.

Labels (1)
Tags (2)
0 Kudos
2 Replies

350 Views
b36401
NXP Employee
NXP Employee

Please try to always fill bitstream from beginning of buffer for each picture.
This way you don't need to call vpu_DecGetBitstreamBuffer.

Have a great day,
Victor

-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------

350 Views
torus1000
Contributor V

Dear Victor

Thank you for your advice. It was helpful.

I'm still wondering why vpu_DecGetBitstreamBuffer() didn't return correct size.

Could you let me know the possibility to miscalculate the size?

(e.g. If it was a ring buffer it may have chance to unmatch the size, I'm not sure.)

BR

0 Kudos