As you can see, no responded. So I had no choice but to reverse engineer the PV code. About all you can do is observe how they enabled the MP4 parser and recognizer to be dynamically registered. Now I am stuck trying to understand their build system and how it automatically recognizes the insertion of new nodes and creates make files to build the new nodes into the system.
On Dec 1, 12:44 am, Nilly <ni...@oriolesoftware.com> wrote: > jeffb, > > You able to do any progress?I am working on same line but do know how > to go ahead.If you have any idea kindly share with me. > > Regards, > Nilly > > On Oct 30, 5:53 am, jeffb <jeffbo...@gmail.com> wrote: > > > > > Sorry, I meant to say parsernode, not decodernode. > > > On Oct 28, 1:54 pm, jeffb <jeffbo...@gmail.com> wrote: > > > > I have a need tocreatea decodernodewhose output will require > > > processing by anothernode. I have read the PVPlayer SDK Developer's > > > Guide and believe that one way to do this is the creation of a new > > >PVMFnode. Not seeing any additional documentation on the creation of > > >PVMFnodes, I have been spending a lot of time looking at the > > > PVPlayerEngine and the advancement of the engine state machine. > > > > I was wondering if there is documentation to make this process easier > > > (i.e. something that describes what interfaces must be created, how a > > > newPVMFnodeis added to the registry, how aPVMFnodeplug-in is > > > sequenced in thenodegraph/pipeline, etc). > > > > I did notice the OMX Core Integration Guide, but at first glance, I > > > was not sure if this is complimentary toPVMFnodes in thenodegraph. > > > > Any guidance would be appreciated.- Hide quoted text - > > - Show quoted text - -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
