below is the Recognize function, when pvfile.Open() is called,
error happened.
PVMFStatus PVMYFFRecognizerPlugin::Recognize(PVMFDataStreamFactory&
aSourceDataStreamFactory, PVMFRecognizerMIMEStringList* aFormatHint,
Oscl_Vector<PVMFRecognizerResult, OsclMemAllocator>&
aRecognizerResult)
{
OSCL_UNUSED_ARG(aFormatHint);
OSCL_wHeapString<OsclMemAllocator> tmpfilename;
Oscl_FileServer fileServ;
PVFile pvfile;
pvfile.SetCPM(&aSourceDataStreamFactory);
if (!(pvfile.Open(tmpfilename.get_cstr(), Oscl_File::MODE_READ |
Oscl_File::MODE_BINARY, fileServ)))
On Apr 22, 9:49 am, chuan <terr...@gmail.com> wrote:
> Hi Ravi,
> Now I scan out a new format in a time this morning, but only for
> one time even I just rename the same file and push it into.
> So I have the chance to test the recognizer, but when I open the
> file using pvfile, the thread died, below debug info is log out, but i
> compare my code to other recognizer , there is nothing different, how
> is that?
>
> E/PV ( 25): PVLOG:TID
> (0xe5408):Time=352:PVMYFFRecognizerPlugin::Recognize Called in
>
> E/PV ( 25): PVLOG:TID
> (0xe5408):Time=352:PVMIDataStreamSyncInterfaceRefImpl::PVMIDataStreamSyncInterfaceRefImpl
>
> E/PV ( 25): PVLOG:TID
> (0xe5408):Time=352:PVMIDataStreamSyncInterfaceRefImpl::OpenSession
>
> E/PV ( 25): PVLOG:TID
> (0xe5408):Time=352:PVMIDataStreamSyncInterfaceRefImpl::OpenSession -
> File Open returning 0
>
> I/DEBUG ( 21): *** *** *** *** *** *** *** *** *** *** *** *** ***
> *** *** ***
>
> I/DEBUG ( 21): Build fingerprint: 'generic/generic/generic/:1.5/
> MAIN/eng.chuanhe.20090415.204213:eng/test-keys'
>
> I/DEBUG ( 21): pid: 25, tid: 198 >>> /system/bin/mediaserver <<<
>
> I/DEBUG ( 21): signal 11 (SIGSEGV), fault addr 00000037
>
> I/DEBUG ( 21): r0 00000037 r1 00000043 r2 00000037 r3 00000003
>
> I/DEBUG ( 21): r4 43000000 r5 00000037 r6 a791e5a0 r7 0000002b
>
> I/DEBUG ( 21): r8 40407b1c r9 afe37dd0 10 a9d28795 fp 00000001
>
> I/DEBUG ( 21): ip a7421958 sp 40608bc0 lr a734ea85 pc
> afe0e258 cpsr 00000010
>
> I/DEBUG ( 21): #00 pc 0000e258 /system/lib/libc.so
>
> I/DEBUG ( 21): #01 pc 0004ea80 /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #02 pc 00055736 /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #03 pc 00055b68 /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #04 pc 00106592 /system/lib/
> libopencore_player.so
>
> I/DEBUG ( 21): #05 pc 001066ca /system/lib/
> libopencore_player.so
>
> I/DEBUG ( 21): #06 pc 000505ce /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #07 pc 000505fc /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #08 pc 0005064a /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #09 pc 000c916e /system/lib/
> libopencore_player.so
>
> I/DEBUG ( 21): #10 pc 000cb09c /system/lib/
> libopencore_player.so
>
> I/DEBUG ( 21): #11 pc 000cb218 /system/lib/
> libopencore_player.so
>
> I/DEBUG ( 21): #12 pc 00056c1e /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #13 pc 00056cd4 /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #14 pc 00056d8a /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): #15 pc 00103358 /system/lib/
> libopencore_player.so
>
> I/DEBUG ( 21): #16 pc 0010340c /system/lib/
> libopencore_player.so
>
> I/DEBUG ( 21): #17 pc 000287fc /system/lib/libutils.so
>
> I/DEBUG ( 21): #18 pc 0000f96c /system/lib/libc.so
>
> I/DEBUG ( 21): #19 pc 0000f4e0 /system/lib/libc.so
>
> I/DEBUG ( 21): stack:
>
> I/DEBUG ( 21): 40608b80 00000000
>
> I/DEBUG ( 21): 40608b84 00000001
>
> I/DEBUG ( 21): 40608b88 00000000
>
> I/DEBUG ( 21): 40608b8c 00000000
>
> I/DEBUG ( 21): 40608b90 00000000
>
> I/DEBUG ( 21): 40608b94 00000000
>
> I/DEBUG ( 21): 40608b98 00000000
>
> I/DEBUG ( 21): 40608b9c 40608bb0
>
> I/DEBUG ( 21): 40608ba0 00000000
>
> I/DEBUG ( 21): 40608ba4 00000000
>
> I/DEBUG ( 21): 40608ba8 00000001
>
> I/DEBUG ( 21): 40608bac a734ea79 /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): 40608bb0 00000160
>
> I/DEBUG ( 21): 40608bb4 a7355555 /system/lib/
> libopencore_common.so
>
> I/DEBUG ( 21): 40608bb8 df002777
>
> I/DEBUG ( 21): 40608bbc e3a070ad
>
> I/DEBUG ( 21): #01 40608bc0 00000400
>
> I/DEBUG ( 21): 40608bc4 a735573b /system/lib/
> libopencore_common.so
>
> W/MediaPlayer( 184): MediaPlayer server died!
>
> E/MediaPlayer( 184): error (100, 0)
>
> I/ServiceManager( 19): service 'media.audio_flinger' died
>
> I/ServiceManager( 19): service 'media.player' died
>
> I/ServiceManager( 19): service 'media.camera' died
>
> W/AudioSystem( 50): AudioFlinger server died!
>
> I/ServiceManager( 184): Waiting for sevice media.player...
>
> I/ ( 199): ServiceManager: 0xabe0
>
> I/AudioFlinger( 199): AudioFlinger's main thread ready to run.
>
> On Apr 21, 8:57 pm, Ravi <yend...@pv.com> wrote:
>
>
>
> > What happens if you push a new mp4 file? Can you see the file doing
> > "adb shell ls -l /sdcard" ?
>
> > For the file to be detected, did you try restarting the emulator?
>
> > For new formats to be detected by the mediascanner, you need to start
> > from frameworks/base/media/java/android/media/MediaFile.java.
>
> > On Apr 21, 7:47 am, chuan <terr...@gmail.com> wrote:
>
> > > When push file below is showed:
> > > adb push vec.qcp sdcard/
> > > 1585 KB/s (0 bytes in 126827.000s)
>
> > > On Apr 21, 8:28 pm, Ravi <yend...@pv.com> wrote:
>
> > > > When was the last time you did your "repo sync"?
>
> > > > When you "push" the content, do you see any error? Are you sure the
> > > > sdcard is working for any other application?
>
> > > > Note that on master, the sdcard functionality is
> > > > broken.http://code.google.com/p/android/issues/detail?id=2335
>
> > > > On Apr 21, 6:30 am, chuan <terr...@gmail.com> wrote:
>
> > > > > I modify MediaScanner.java MediaFile.java too, but no file can be
> > > > > scanned out successfully as well as .mp4/3gp/3g2
>
> > > > > On Apr 21, 6:23 pm, chuan <terr...@gmail.com> wrote:
>
> > > > > > Dear Ravi,
> > > > > > I met a problem when testing video/audio playbak on opencore
> > > > > > 2.0, I
> > > > > > can't scan out media files that I push into the sdcard, my step as
> > > > > > below:
> > > > > > 1. adb push test.mp4 sdcard/ (or other audio/video files)
> > > > > > 2. reset emulator and run it using "emulator -sdcard sdcard.img"
> > > > > > This happen when I change opencore from 1.x to 2.0. In opencore
> > > > > > 1.x
> > > > > > it can always work and i can find media file in Music or VideoPlayer
> > > > > > app, but now i cannot get them.
> > > > > > The difference is In opencore 1.x I useScannerin Dev Tool to scan
> > > > > > files,while in 2.0 I have to reset emulator( it seems scan work is
> > > > > > done when emulator is set up). I only get a file occasionally.
> > > > > > AND, if I want to scan out a new file format(such as .awb or
> > > > > > .qcp),
> > > > > > what need to be done except modify mediascanner.cpp ? ( only scan
> > > > > > out,
> > > > > > other work is beyond consideration)
> > > > > > Many thanks!
>
> > > > > > On Apr 15, 10:40 pm, Ravi <yend...@pv.com> wrote:
>
> > > > > > > On Apr 15, 7:11 am, chuan <terr...@gmail.com> wrote:> Dear Ravi:
> > > > > > > > Thank so much for your quickly reply, as i am try hard to
> > > > > > > > figure it
> > > > > > > > out .
> > > > > > > > Now i wish to share my plan and wish get help from you.
> > > > > > > > 1. modify mp4 parer src code to support the audio
> > > > > > > > codec(modify
> > > > > > > > atomdefs.h sampledescriptionatom.h and some other .cpp).
> > > > > > > > 2. modify mp4parser node code ,add audio codec type
> > > > > > > > support.
> > > > > > > > 3. use OpenCORE OMX-core to register my new omx component,
> > > > > > > > add
> > > > > > > > codec type or registration to omx related file.
> > > > > > > > from above steps, i have some question:
> > > > > > > > (1) as you know opencore version 1.x has a simpler omx
> > > > > > > > component
> > > > > > > > interface, but in 2.0 the interface is more complex, why? it
> > > > > > > > make me
> > > > > > > > to wrap the interface
> > > > > > > > in cpp file.
>
> > > > > > > Actually, I don't know this. I am not aware of any change of OMX
> > > > > > > component interface. Can you please point me to an example?>
> > > > > > > (2) and if i want use my own OMX-core (i'm going to do so), how
> > > > > > > > can i do the job as you say? i read the omx intergrate doc, but
> > > > > > > > i
> > > > > > > > could not understand it fully.
>
> > > > > > > Here is a thread where someone was able to do
> > > > > > > so.http://groups.google.com/group/android-framework/browse_thread/thread....
> > > > > > > Let us know if you still have questions.> (3) today i try to
> > > > > > > get the pv log out to debug ,but failed to do
> > > > > > > > so, as you know in version 1.x i can modify two head files and
> > > > > > > > one cpp
> > > > > > > > to get the log out, i have try to make with
> > > > > > > > ENABLE_PV_LOGGING=1 and even try to modify some log
> > > > > > > > related
> > > > > > > > head files, but i got nothing. you know it cost a lot of time,
> > > > > > > > and
> > > > > > > > can't use log message to debug make me upset.
>
> > > > > > > This should still work. Folks here have also been able to get logs
> > > > > > > through this method. Let me see if I can patch up something to
> > > > > > > get the
> > > > > > > logs more easily.
>
> > > > > > > > looking forward for your reply expecial question(3) , thx!
>
> > > > > > > > On Apr 15, 4:10 pm, Ravi <yend...@pv.com> wrote:
>
> > > > > > > > > I don't know enough about QCELP to comment on how and if to
> > > > > > > > > modify the
> > > > > > > > > mp4 parser. I can try to find out.
>
> > > > > > > > > In general, the steps to add a new OMX codec would be:
> > > > > > > > > (i) Add the required format, if not present, in
> > > > > > > > > pvmi/pvmf/include/
> > > > > > > > > pvmf_format_type.h.
> > > > > > > > > (ii) Add the mime type in the capability of
> > > > > > > > > PVMFOMXAudioDecNode()
> > > > > > > > > or PVMFOMXVideoDecNode() [see the constructor].
> > > > > > > > > if you are going to use the OpenCORE OMX-core ...
> > > > > > > > > (iii) Register the component in the omx registry -
> > > > > > > > > codecs_v2/omx/
> > > > > > > > > omx_common/src/pv_omxregistry.cpp.
> > > > > > > > > or
> > > > > > > > > if you are going to provide your own OMX-core ...
> > > > > > > > > (iii) Have your OMX-core register this new component.
> > > > > > > > > (iv) Have your
>
> ...
>
> read more »- Hide quoted text -
>
> - Show quoted text -
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
