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.

DM355 MPEG Decoder flushing issues

Hello,

I am running into some issues trying to flush the video decoder so that I can start a new video up without having frames from the previous video stuck in the pipe.  

According to documentation for the Vdec2_flush() method:

1. Call Vdec2_flush.

2. Call Vdec2_process and hInBuf will be ignored.

3. Loop on Vdec2_getDisplayBuf() and Vdec2_getFreeBuf() until all buffers are cleared out.

I have a note in my decode demo relating to EOF and decoder flushing that there is a DM355 codec issue with flushing and the section includes a workaround which essentially skips flushing.  

If I try something similar to this disabled section (implementing steps 1, 2, and 3) in my own code, then I receive a "Bit error on stream" error from Vdec2_process().  

Are there any working flushing examples or a workaround to accomplish flushing on DM355?  I considered shutting down the decoder and creating a new handle, but would that safely release buffers that it presently has in-use?  Will upgrading to DVSDK 3.10 be of any use?

Thank you,

Wiley

  • I suggest you migrate to DVSDK 3.1 which has new set of DM355 codecs(similar to Dm365 ones). We are no longer supporting DM355 codec from DVSDK 1.x and 2.x.

    Bty, why do you need flush in DM355 Mpeg4 decoder? This codec should be releasing buffer with every process call as it is Mpeg4 SP and there are no buffers held by the codec.

    regards

    Yashwant