Glad to know. -Ravi
On Dec 10, 7:28 pm, guru <[email protected]> wrote: > Thanks Ravi... I am able to resolve that Issue. As you told the issue > was with my omx component initialization. > > On Dec 8, 2:34 pm, RaviY <[email protected]> wrote: > > > iThreadSafeHandlerEventHandler is initalized in the node Prepare(). > > > -Ravi > > > On Dec 8, 1:58 pm, guru <[email protected]> wrote: > > > > HI Ravi, > > > > I added log in the below function using LOGE to check problem with the > > > crash: > > > > OMX_ERRORTYPE CallbackEventHandler(OMX_OUT OMX_HANDLETYPE aComponent, > > > OMX_OUT OMX_PTR aAppData, > > > OMX_OUT OMX_EVENTTYPE aEvent, > > > OMX_OUT OMX_U32 aData1, > > > OMX_OUT OMX_U32 aData2, > > > OMX_OUT OMX_PTR aEventData) > > > { > > > ... > > > .. > > > if((EventHandlerSpecificData*) Node->iThreadSafeHandlerEventHandler > > > == NULL) > > > { > > > LOGE("iThreadSafeHandlerEventHandler is NULL\n"); > > > } > > > > } > > > > When i play aac audio file, then it is printing > > > "iThreadSafeHandlerEventHandler is NULL. > > > What I have to do in my component code, to make sure > > > iThreadSafeHandlerEventHandler is not NULL or PV core will take care > > > initializing this. > > > > Regards > > > Gururaja B O > > > > On Dec 8, 12:09 pm, RaviY <[email protected]> wrote: > > > > > If you don't support the index > > > > "PV_OMX_COMPONENT_CAPABILITY_TYPE_INDEX", then the default value for > > > > iIsOMXComponentMultiThreaded is true. > > > > > -Ravi > > > > > On Dec 7, 5:17 pm, guru <[email protected]> wrote: > > > > > > hi Ravi, > > > > > > Whether I have to set iIsOMXComponentMultiThreaded to TREU before > > > > > calling EventHandler? as below. > > > > > > pComponentPrivate->iPVCapabilityFlags.iIsOMXComponentMultiThreaded = > > > > > OMX_TRUE; > > > > > > I am not setting this flag in my component code, but calling > > > > > pthread_create to call ComponentThread. > > > > > > Regards > > > > > Gururaja B O > > > > > > RaviY wrote: > > > > > > You shouldn't be needing any changes in the callbacks. The callback > > > > > > functions are generic, and should work for all cases. Can you post > > > > > > the > > > > > > complete stacktrace? I would have expected the shared library names > > > > > > in > > > > > > the stack trace, and some address. > > > > > > > -Ravi > > > > > > > On Dec 4, 3:07 pm, guru <[email protected]> wrote: > > > > > > > HI All, > > > > > > > > I have integrated Audio decoder(OpenMAX) to OpenCORE. OpenCORE is > > > > > > > recognizing our component, but it is failing to play the audio > > > > > > > file. > > > > > > > > I added logs to identify the problem and found that getting > > > > > > > crashed at > > > > > > > event handler callback. > > > > > > > > Following is the log > > > > > > > > E/ ( 773): Calling core specific GetHandle > > > > > > > E/pvomxcore( 773): OMX_CORE.c OMX_GetHandle IN > > > > > > > E/pvomxcore( 773): ....Invoking ComponentInit > > > > > > > E/ ( 773): OMX_COMP.c MyComponentInit IN > > > > > > > E/ ( 773): .... Create the component thread > > > > > > > E/ ( 773): OMX_COMP.c ComponentThread IN > > > > > > > E/ ( 773): OMX_COMP.c MyComponentInit OUT > > > > > > > E/pvomxcore( 773): ....Exiting ComponentInit > > > > > > > E/pvomxcore( 773): Initializing CallBacks IN > > > > > > > E/pvomxcore( 773): Initializing CallBacks OUT > > > > > > > E/pvomxcore( 773): OMX_CORE.c OMX_GetHandle OUT > > > > > > > E/ ( 773): Exiting core specific GetHandle > > > > > > > E/ ( 773): .... case OMX_StateLoaded START > > > > > > > E/ ( 773): .... Calling Event Handler ( --> this is called > > > > > > > when STATE is Loaded) > > > > > > > I/DEBUG ( 770): *** *** *** *** *** *** *** *** *** *** *** > > > > > > > *** *** > > > > > > > *** *** * > > > > > > > ** > > > > > > > I/DEBUG ( 770): Build fingerprint: 'zoom/zoom2/zoom2/zoom2:1.5/ > > > > > > > CUPCAKE/eng.mi > > > > > > > ndtree.20091012.145505:eng/test-keys' > > > > > > > I/DEBUG ( 770): 405f5994 00000000 > > > > > > > I/DEBUG ( 770): 405f5998 00000000 > > > > > > > I/DEBUG ( 770): 405f599c 00000000 > > > > > > > I/DEBUG ( 770): 405f59a0 00000000 > > > > > > > I/DEBUG ( 770): 405f59a4 00000000 > > > > > > > I/DEBUG ( 770): 405f59a8 00000000 > > > > > > > I/DEBUG ( 770): 405f59ac 00000000 > > > > > > > I/DEBUG ( 770): 405f59b0 00000000 > > > > > > > I/DEBUG ( 770): 405f59b4 00000000 > > > > > > > I/DEBUG ( 770): 405f59b8 00000000 > > > > > > > I/DEBUG ( 770): 405f59bc 00000000 > > > > > > > I/DEBUG ( 770): 405f59c0 00000000 > > > > > > > I/DEBUG ( 770): 405f59c4 00000000 > > > > > > > I/DEBUG ( 770): 405f59c8 00000000 > > > > > > > I/DEBUG ( 770): 405f59cc 00000000 > > > > > > > I/DEBUG ( 770): 405f59d0 00000000 > > > > > > > I/DEBUG ( 770): 405f59d4 00000000 > > > > > > > > if i am integrating component, do i need to modify callbacks or > > > > > > > can we > > > > > > > directly call them by passing required parameters. > > > > > > > > please give me some direction regarding this. > > > > > > > > Thanks > > > > > > > Gururaja- Hide quoted text - > > > - Show quoted text - > > -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting
