The OMX IL 1.1.2 spec does not specify explicitly who is responsible for setting the value of nOffset parameter in each buffer. (whether it is the OMX IL client or OMX component). Since there is no clear obligation on either client or component to set this value (and OMX components have been found that do not initialize this value) - to ensure the proper operation over a range of possible OMX components the OMX client sets the value of nOffset to 0. THis is not in collision with the omx spec in any way. The valid data in input the buffer starts where indicated.
Depending on your use-case - the component On Feb 25, 8:43 pm, hdandroid <[email protected]> wrote: > Looks like OpenCore does not understand the usage of nOffset field on > input port. There is no effect when component sets nOffset to a non- > zero value. OpenCore ignores nOffset and copies data into reserved > region (same behavior as when nOffset is set to Zero) > > >>>Sec 2.1.12 of OMX IL 1.1.2 > > The nOffset parameter indicates the number of bytes between the start > of the buffer and the start of valid data. The nFilledLen parameter > specifies the number of contiguous bytes of valid data in the buffer. > The valid data in the buffer is therefore located in the range pBuffer > + nOffset to pBuffer + nOffset + nFilledLen. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "android-framework" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-framework?hl=en -~----------~----~----~----~------~----~------~--~---
