Function pvproxythreadmain_omx in opencore/codecs_v2/omx/omx_proxy/src/
pv_omx_interface_proxy.cpp.

On Mar 23, 7:03 am, Jia Meng <dspm...@gmail.com> wrote:
> Actually I have redirected PVAuthorEngine's log into a file using
> TextFileAppender for better reading. If I want to do the same thing
> for the OMX component thread, I guess a separate PV Logger should be
> created during OMX component thread initialization. Could you tell me
> where the OMX component thread is created by PV Author, e.g. H.264
> encoder?
>
> Thanks
>
> On Mar 23, 11:32 am, rktb <yend...@pv.com> wrote:
>
> > If I remember correctly, we have a bug open for this internally. We
> > are not able to log the components that are in a separate thread. And
> > hence the issue that you are seeing. I will check on the status and
> > let you know.
>
> > As a quick workaround, you can convert all the PVLOGGER statements in
> > the cpp file to a LOGE and then re-run to get the log statements.
>
> > -Ravi
>
> > On Mar 22, 9:24 pm, Jia Meng <dspm...@gmail.com> wrote:
>
> > > Hi,
>
> > > I have changed PVLOGGER_INST_LEVEL to 5, and created /sdcard/
> > > pvlogger.txt as below.
>
> > > 8,PVAuthorEngine
> > > 8,OmxComponentBase
>
> > > However, I can get output of "PVAuthorEngine", but not
> > > "OmxComponentBase". It's strange that "OmxComponentBase" is dumped
> > > with "PVLOGMSG_NOTICE", which should has enough priority. Please help
> > > me out.
>
> > > iLogger = PVLogger::GetLoggerObject("OmxComponentBase");
> > > PVLOGGER_LOGMSG(PVLOGMSG_INST_HLDBG, iLogger, PVLOGMSG_NOTICE, (0,
> > > "OmxComponentBase : constructed"));
>
> > > Thanks
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"android-framework" group.
To post to this group, send email to android-framework@googlegroups.com
To unsubscribe from this group, send email to 
android-framework+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/android-framework?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to