• Locked Locked
  • Replies 1 reply
  • Subscribers 100 subscribers
  • Views 485 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

VFPC component holding input buffers during state transition

Shrikara B
Prodigy 10 points

Hi,

We are using a DM8168 processor with TI EZSDK-5-03-01-15 for an AV encoder system.

We are observing an issue with VFPC component when de-interlacing is enabled - 

- One of our requirements is connecting and disconnecting the video source. During disconnect state, our application inserts colored frames with text overlay. So we move both capture and scaler components to idle state.    

- Moving the capture (VFCC) component from executing state to idle state works without any issues.  But, moving the scaler (VFPC) component from executing state to idle state causes 1 or 2 input buffers to be held by the VFPC component :- EmptyBufferDone()  call back is not received by the application. The latest 1 or 2 buffers given in EmptyThisBuffer call is/are held by the component.

- These 1 or 2 buffers are never released by the component and hence cannot be used by the application.

- This issue is not seen every time we disconnect the source.  Around 5-6 times for 10 disconnect/connect iterations. 

- We have allocated 7 buffers for capture output which will be used by the scaler input. So after around 10 disconnect/connect, all the buffers will be held back by the VFPC component.

- While there is no issue seen with scalar output buffers.

- We tried to perform OMX_CommandFlush for all the ports, but, the issues still exists.

Please advise us on this issue.

Thanks and Regards,

Shrikara.

We couldn't send this message because Anita Choudhary is unavailable or offline.
[11/30/2016 6:26 PM] Shrikara B:
y not?
[11/30/2016 6:26 PM] Shrikara B:
*Mujhepatanahi
This message may not have been sent to Anita Choudhary because there was no response from the server.
y not?
When contacting your support team, reference error ID 1 (source ID 0).
 
 
 
Troubleshooting information is available online, including best practices for using Lync.
y not?
When contacting your support team, reference error ID 1 (source ID 0).
 
 
 
Troubleshooting information is available online, including best practices for using Lync.
*Mujhepatanahi
 
  • TI__Guru* 80190 points

    Hello,

    Shrikara B said:
    TI EZSDK-5-03-01-15

    This is very old version of EZSDK. The latest version is 5.05.02. Do you observe this problem with the latest EZSDK?

    Shrikara B said:
    - We tried to perform OMX_CommandFlush for all the ports, but, the issues still exists.

    Here is example of flush command for decoder element:

        
            printf("Sending FlushCommand...\n");
            eError =    OMX_SendCommand (decILComp->handle, OMX_CommandFlush,  0 , NULL);
            eError =    OMX_SendCommand (decILComp->handle, OMX_CommandFlush,  1 , NULL);
     

    BR
    Margarita