[Media Decode] dont reduce the slice number when app layer destroy SliceDataBuffer
sometimes, app call vaDestoryBuffer for VASliceDataBufferType in middle of one frame execution.
for example: there are two VASliceDataBufferType for one frame. after first VASliceDataBufferType
was created. then destroy one VASliceDataBufferType of last frame , then create second slice for
current frame, it will cause problem.
the rootcause is :media driver try to optimize the bistream combination, so it allocate one buffer
for mulitple slice data. then these slice data just get the offset and were filled into one bistream
buffer. this method reduce one combination copy.
Signed-off-by: Carl Zhang <carl.zhang@intel.com>
2 files changed
