Thanks for replying.
I've seen what you provided and I understand how a MIME format should be added
in that header. However, I think it's not just a problem of adding MIME format.
If I want to support motion jpeg, is that means I should revise the parser node
to recognize MJPEG video format?
In other words, assuming I want to support AVI+MJPEG (Assuming a parser node
exists) and MP4+MJPEG, I should manually check if the MJPEG have been
recognized. Is that true?
In my understanding, what I should do are as following, take Mp4+MJPEG for
instance.
1. add Mime type for motion jpeg (video/x-motion-jpeg) in pvmf_format_type.h
(Here just some small problem, where can I find MIME registration list?
I just googled and find this but it's not an offical site.)
2. Revise the Mp4 parser provided by Opencore
in the "external/opencore/fileformats/mp4/parser"
2.1 Revise the parsing process
http://android.git.kernel.org/?
p=platform/external/opencore.git;a=blob;f=fileformats/mp4/parser/src/sampledescr
iptionatom.cpp
on the context of line 300.
--Is this entry the official fourcc? (take AVC for example)
--const uint32 AVC_SAMPLE_ENTRY = FourCharConstToUint32('a', 'v', 'c',
'1');
2.2 Revise "void SampleDescriptionAtom::getMIMEType(OSCL_String& aMimeType)" on
the Line 891 of the same file to return the Mime string, which we add in the
first step.
3. then we have the OMX core to recognize this string, so as to pass to the
right decoder
Is that right? In short, if we want to decode mjpg for some kind of container
(e.g. MP4), we must have the control the container parsers. Is that true?
Thanks,
Alonso
--
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
