Re: MP4 file open error
On Feb 13, 1:52 am, Andy Quan androidr...@gmail.com wrote:
Ravi,
Very clear explanation. Thanks. I guess ASP still will not be supported in
OpenCORE 2.0 release, right?
OpenCORE 2.0 has been released. And yes, ASP is still not supported.
In my understanding, those bytes handled by config parser are raw data from
the container. So are you expecting codec vendor to provide container
parsing capability as you want that function to be provided by vendor
themselves?
Exactly. However, to be sure, just in case the terminology is
different ... it is the bitstream header parsing capability that we
want the codec vendor to provide. I call mp4 fileformat as a
container :-)
On 2/13/09, rktb yend...@pv.com wrote:
Hi Andy,
Your expectation is correct. But, there is a small deviation. Once the
parser succeeds in parsing data, config data is passed to the OMX
decoder node to verify whether the decoder can support it. To validate
this, we have in place, something called the config parser which, in
brief, parses the bitstream to check whether our OMX component can
handle/support it. It is here that we see that the clip is advertising
ASP, and the track is rejected.
Ideally, this config parser should be provided by the decoder
supplier so that when validating a XYZ_component, the corresponding
XYZ_config_parser is used to verify whether a codec can support it or
not. We had internal discussions and were planning on providing this
API in the OpenCORE 2.0 time frame, but got delayed. If you have any
suggestions regarding the same, we would be glad to discuss it with
you.
Regarding the specific clip, you can modify the video config parser to
choose the tools that your codec supports and then use it to verify
the functionality of your codec.
-Ravi
On Feb 12, 9:54 pm, Andy Quan androidr...@gmail.com wrote:
Ravi,
Your information is very helpful. But I dont understand this: if the
parser
supports ASP then I expect to see at least some behaviors of OMX
pipeline.
So is it because the parser recognized ASP and refused to go
on? An equivalent question is if I replace OMX component with an ASP
capable
one, can I get that file played? My experiment showed that it still did
not
work.
On 2/13/09, rktb yend...@pv.com wrote:
Hi Andy,
On Feb 12, 7:32 pm, Andy Quan androidr...@gmail.com wrote:
Ravi,
Thank you! Let me make this clear: Is it the parser or OMX of
OpenCORE
that
can not handle MPEG4 ASP?
It is the codec that is not capable of handling the ASP.
1. And if OpenCORE has a limitation of media contents support, no
matter
it
is within parser or OMX, I'd like to know where I can get a
full feature
list information.
I don't have a ready list of supported feature set or tools that the
codecs can support. I shall try to collect it and post the details.
2. If there is no such kind of list, are there any known issues
regarding
to
media format/profile/contents support in the git code?
I did not get this question.
I think a big problem for many android developers here is that we get
video
cant be played information but never know why. This will help reduce
many
questions here.
Yes. We acknowledge this issue. We are trying to come up with more
meaningful errors in future versions.
Many thanks again for your help!
--
Thanks,
Andy
On 2/13/09, rktb yend...@pv.com wrote:
It looks like the clip is not simple profile and that's the reason
we
reject it.
-Ravi
On Feb 12, 9:41 am, Andy Quan androidr...@gmail.com wrote:
Test stream is attached as well. Thank you!
I/ActivityManager( 44): Starting activity: Intent {
action=android.intent.acti
on.VIEW data=content://media/external/video/media/18
type=video/mp4
comp={
com.an droid.music/com.android.music.MovieView} }
W/SensorService( 44): could not enable sensor 2
I/MediaPlayer-JNI( 171): prepareAsync: surface=0x1b0698 (id=1)
V/VideoMIO( 31): AndroidAudioSurfaceOutput surface=0x1c6a8
W/PlayerDriver( 31): PVMFInfoErrorHandlingComplete
I/ActivityManager( 44): Displayed activity
com.android.music/.MovieView:
236
ms
E/MediaPlayer( 171): Error (-1,0)
D/VideoView( 171): Error: -1,0
On 2/12/09, rktb yend...@pv.com wrote:
Can you provide us the actual content that you are using so it
is
easier to see what is going wrong instead of speculating?
What log did you trace? Can you share that log?
-Ravi
On Feb 12, 8:05 am, Andy Quan androidr...@gmail.com wrote:
Dave,
I have it tested both on real arm hardware and SDK r2
emulator.
They
are
opened with native Videoplayer as local file on sdcard. I
traced
the
log
information and
Re: MP4 file open error
Dave, I have it tested both on real arm hardware and SDK r2 emulator. They are opened with native Videoplayer as local file on sdcard. I traced the log information and found they failed faraway before running into OMX decoding. Some of them are of MPEG4 ASP but I dont think this matters as errors come up in an early stage. As for the size, is there any limitation? We used to have them as test streams for other MMF like GStreamer. As I remember there are some discussions here last year about limitations of MP4 container itself in PV framework, but I can not find them. Could you please help? Correct me if I misunderstand anything. -- Thanks, Andy On Thu, Feb 12, 2009 at 11:38 AM, Dave Sparks davidspa...@android.comwrote: There are limitations that may prevent a file from playing. What platform are you testing on? Is the streaming or local file playback? If streaming, HTTP or RTSP? What are the video and audio stream parameters (codec, frame size, bit rate, sample rate, etc)? On Feb 11, 7:24 pm, Andy Quan androidr...@gmail.com wrote: Hi, Is there any known issue on OpenCORE mp4 parser? I find that once a while some MP4 files fail before they are sent to decoding. However these files can be played in other MMF like GStreamer. Usually it fails in prepareAsync. -- Thanks, Andy --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: MP4 file open error
Can you provide us the actual content that you are using so it is easier to see what is going wrong instead of speculating? What log did you trace? Can you share that log? -Ravi On Feb 12, 8:05 am, Andy Quan androidr...@gmail.com wrote: Dave, I have it tested both on real arm hardware and SDK r2 emulator. They are opened with native Videoplayer as local file on sdcard. I traced the log information and found they failed faraway before running into OMX decoding. Some of them are of MPEG4 ASP but I dont think this matters as errors come up in an early stage. As for the size, is there any limitation? We used to have them as test streams for other MMF like GStreamer. As I remember there are some discussions here last year about limitations of MP4 container itself in PV framework, but I can not find them. Could you please help? Correct me if I misunderstand anything. -- Thanks, Andy On Thu, Feb 12, 2009 at 11:38 AM, Dave Sparks davidspa...@android.comwrote: There are limitations that may prevent a file from playing. What platform are you testing on? Is the streaming or local file playback? If streaming, HTTP or RTSP? What are the video and audio stream parameters (codec, frame size, bit rate, sample rate, etc)? On Feb 11, 7:24 pm, Andy Quan androidr...@gmail.com wrote: Hi, Is there any known issue on OpenCORE mp4 parser? I find that once a while some MP4 files fail before they are sent to decoding. However these files can be played in other MMF like GStreamer. Usually it fails in prepareAsync. -- Thanks, Andy --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: MP4 file open error
It looks like the clip is not simple profile and that's the reason we
reject it.
-Ravi
On Feb 12, 9:41 am, Andy Quan androidr...@gmail.com wrote:
Test stream is attached as well. Thank you!
I/ActivityManager( 44): Starting activity: Intent {
action=android.intent.acti
on.VIEW data=content://media/external/video/media/18 type=video/mp4 comp={
com.an droid.music/com.android.music.MovieView} }
W/SensorService( 44): could not enable sensor 2
I/MediaPlayer-JNI( 171): prepareAsync: surface=0x1b0698 (id=1)
V/VideoMIO( 31): AndroidAudioSurfaceOutput surface=0x1c6a8
W/PlayerDriver( 31): PVMFInfoErrorHandlingComplete
I/ActivityManager( 44): Displayed activity com.android.music/.MovieView: 236
ms
E/MediaPlayer( 171): Error (-1,0)
D/VideoView( 171): Error: -1,0
On 2/12/09, rktb yend...@pv.com wrote:
Can you provide us the actual content that you are using so it is
easier to see what is going wrong instead of speculating?
What log did you trace? Can you share that log?
-Ravi
On Feb 12, 8:05 am, Andy Quan androidr...@gmail.com wrote:
Dave,
I have it tested both on real arm hardware and SDK r2 emulator. They are
opened with native Videoplayer as local file on sdcard. I traced the log
information and found they failed faraway before running into OMX
decoding.
Some of them are of MPEG4 ASP but I dont think this matters as errors
come
up in an early stage. As for the size, is there any limitation? We used
to
have them as test streams for other MMF like GStreamer.
As I remember there are some discussions here last year about limitations
of
MP4 container itself in PV framework, but I can not find them. Could you
please help? Correct me if I misunderstand anything.
--
Thanks,
Andy
On Thu, Feb 12, 2009 at 11:38 AM, Dave Sparks davidspa...@android.com
wrote:
There are limitations that may prevent a file from playing.
What platform are you testing on?
Is the streaming or local file playback?
If streaming, HTTP or RTSP?
What are the video and audio stream parameters (codec, frame size, bit
rate, sample rate, etc)?
On Feb 11, 7:24 pm, Andy Quan androidr...@gmail.com wrote:
Hi,
Is there any known issue on OpenCORE mp4 parser? I find that once a
while
some MP4 files fail before they are sent to decoding. However these
files
can be played in other MMF like GStreamer. Usually it fails in
prepareAsync.
--
Thanks,
Andy
--
Thanks,
Andy
mpeg4_cif_noaudio.mp4
3490KViewDownload
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
Re: MP4 file open error
Hi Andy,
On Feb 12, 7:32 pm, Andy Quan androidr...@gmail.com wrote:
Ravi,
Thank you! Let me make this clear: Is it the parser or OMX of OpenCORE that
can not handle MPEG4 ASP?
It is the codec that is not capable of handling the ASP.
1. And if OpenCORE has a limitation of media contents support, no matter it
is within parser or OMX, I'd like to know where I can get a full feature
list information.
I don't have a ready list of supported feature set or tools that the
codecs can support. I shall try to collect it and post the details.
2. If there is no such kind of list, are there any known issues regarding to
media format/profile/contents support in the git code?
I did not get this question.
I think a big problem for many android developers here is that we get video
cant be played information but never know why. This will help reduce many
questions here.
Yes. We acknowledge this issue. We are trying to come up with more
meaningful errors in future versions.
Many thanks again for your help!
--
Thanks,
Andy
On 2/13/09, rktb yend...@pv.com wrote:
It looks like the clip is not simple profile and that's the reason we
reject it.
-Ravi
On Feb 12, 9:41 am, Andy Quan androidr...@gmail.com wrote:
Test stream is attached as well. Thank you!
I/ActivityManager( 44): Starting activity: Intent {
action=android.intent.acti
on.VIEW data=content://media/external/video/media/18 type=video/mp4
comp={
com.an droid.music/com.android.music.MovieView} }
W/SensorService( 44): could not enable sensor 2
I/MediaPlayer-JNI( 171): prepareAsync: surface=0x1b0698 (id=1)
V/VideoMIO( 31): AndroidAudioSurfaceOutput surface=0x1c6a8
W/PlayerDriver( 31): PVMFInfoErrorHandlingComplete
I/ActivityManager( 44): Displayed activity com.android.music/.MovieView:
236
ms
E/MediaPlayer( 171): Error (-1,0)
D/VideoView( 171): Error: -1,0
On 2/12/09, rktb yend...@pv.com wrote:
Can you provide us the actual content that you are using so it is
easier to see what is going wrong instead of speculating?
What log did you trace? Can you share that log?
-Ravi
On Feb 12, 8:05 am, Andy Quan androidr...@gmail.com wrote:
Dave,
I have it tested both on real arm hardware and SDK r2 emulator. They
are
opened with native Videoplayer as local file on sdcard. I traced the
log
information and found they failed faraway before running into OMX
decoding.
Some of them are of MPEG4 ASP but I dont think this matters as errors
come
up in an early stage. As for the size, is there any limitation? We
used
to
have them as test streams for other MMF like GStreamer.
As I remember there are some discussions here last year about
limitations
of
MP4 container itself in PV framework, but I can not find them. Could
you
please help? Correct me if I misunderstand anything.
--
Thanks,
Andy
On Thu, Feb 12, 2009 at 11:38 AM, Dave Sparks
davidspa...@android.com
wrote:
There are limitations that may prevent a file from playing.
What platform are you testing on?
Is the streaming or local file playback?
If streaming, HTTP or RTSP?
What are the video and audio stream parameters (codec, frame size,
bit
rate, sample rate, etc)?
On Feb 11, 7:24 pm, Andy Quan androidr...@gmail.com wrote:
Hi,
Is there any known issue on OpenCORE mp4 parser? I find that once
a
while
some MP4 files fail before they are sent to decoding. However
these
files
can be played in other MMF like GStreamer. Usually it fails in
prepareAsync.
--
Thanks,
Andy
--
Thanks,
Andy
mpeg4_cif_noaudio.mp4
3490KViewDownload
--~--~-~--~~~---~--~~
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
-~--~~~~--~~--~--~---
Re: MP4 file open error
Ravi,
Very clear explanation. Thanks. I guess ASP still will not be supported in
OpenCORE 2.0 release, right?
In my understanding, those bytes handled by config parser are raw data from
the container. So are you expecting codec vendor to provide container
parsing capability as you want that function to be provided by vendor
themselves?
On 2/13/09, rktb yend...@pv.com wrote:
Hi Andy,
Your expectation is correct. But, there is a small deviation. Once the
parser succeeds in parsing data, config data is passed to the OMX
decoder node to verify whether the decoder can support it. To validate
this, we have in place, something called the config parser which, in
brief, parses the bitstream to check whether our OMX component can
handle/support it. It is here that we see that the clip is advertising
ASP, and the track is rejected.
Ideally, this config parser should be provided by the decoder
supplier so that when validating a XYZ_component, the corresponding
XYZ_config_parser is used to verify whether a codec can support it or
not. We had internal discussions and were planning on providing this
API in the OpenCORE 2.0 time frame, but got delayed. If you have any
suggestions regarding the same, we would be glad to discuss it with
you.
Regarding the specific clip, you can modify the video config parser to
choose the tools that your codec supports and then use it to verify
the functionality of your codec.
-Ravi
On Feb 12, 9:54 pm, Andy Quan androidr...@gmail.com wrote:
Ravi,
Your information is very helpful. But I dont understand this: if the
parser
supports ASP then I expect to see at least some behaviors of OMX
pipeline.
So is it because the parser recognized ASP and refused to go
on? An equivalent question is if I replace OMX component with an ASP
capable
one, can I get that file played? My experiment showed that it still did
not
work.
On 2/13/09, rktb yend...@pv.com wrote:
Hi Andy,
On Feb 12, 7:32 pm, Andy Quan androidr...@gmail.com wrote:
Ravi,
Thank you! Let me make this clear: Is it the parser or OMX of
OpenCORE
that
can not handle MPEG4 ASP?
It is the codec that is not capable of handling the ASP.
1. And if OpenCORE has a limitation of media contents support, no
matter
it
is within parser or OMX, I'd like to know where I can get a
full feature
list information.
I don't have a ready list of supported feature set or tools that the
codecs can support. I shall try to collect it and post the details.
2. If there is no such kind of list, are there any known issues
regarding
to
media format/profile/contents support in the git code?
I did not get this question.
I think a big problem for many android developers here is that we get
video
cant be played information but never know why. This will help reduce
many
questions here.
Yes. We acknowledge this issue. We are trying to come up with more
meaningful errors in future versions.
Many thanks again for your help!
--
Thanks,
Andy
On 2/13/09, rktb yend...@pv.com wrote:
It looks like the clip is not simple profile and that's the reason
we
reject it.
-Ravi
On Feb 12, 9:41 am, Andy Quan androidr...@gmail.com wrote:
Test stream is attached as well. Thank you!
I/ActivityManager( 44): Starting activity: Intent {
action=android.intent.acti
on.VIEW data=content://media/external/video/media/18
type=video/mp4
comp={
com.an droid.music/com.android.music.MovieView} }
W/SensorService( 44): could not enable sensor 2
I/MediaPlayer-JNI( 171): prepareAsync: surface=0x1b0698 (id=1)
V/VideoMIO( 31): AndroidAudioSurfaceOutput surface=0x1c6a8
W/PlayerDriver( 31): PVMFInfoErrorHandlingComplete
I/ActivityManager( 44): Displayed activity
com.android.music/.MovieView:
236
ms
E/MediaPlayer( 171): Error (-1,0)
D/VideoView( 171): Error: -1,0
On 2/12/09, rktb yend...@pv.com wrote:
Can you provide us the actual content that you are using so it
is
easier to see what is going wrong instead of speculating?
What log did you trace? Can you share that log?
-Ravi
On Feb 12, 8:05 am, Andy Quan androidr...@gmail.com wrote:
Dave,
I have it tested both on real arm hardware and SDK r2
emulator.
They
are
opened with native Videoplayer as local file on sdcard. I
traced
the
log
information and found they failed faraway before running into
OMX
decoding.
Some of them are of MPEG4 ASP but I dont think this matters
as
errors
come
up in an early stage. As for the size, is there any
limitation?
We
used
to
have them as test streams for other MMF like GStreamer.
As I remember there are some discussions here last year about
limitations
MP4 file open error
Hi, Is there any known issue on OpenCORE mp4 parser? I find that once a while some MP4 files fail before they are sent to decoding. However these files can be played in other MMF like GStreamer. Usually it fails in prepareAsync. -- Thanks, Andy --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
Re: MP4 file open error
There are limitations that may prevent a file from playing. What platform are you testing on? Is the streaming or local file playback? If streaming, HTTP or RTSP? What are the video and audio stream parameters (codec, frame size, bit rate, sample rate, etc)? On Feb 11, 7:24 pm, Andy Quan androidr...@gmail.com wrote: Hi, Is there any known issue on OpenCORE mp4 parser? I find that once a while some MP4 files fail before they are sent to decoding. However these files can be played in other MMF like GStreamer. Usually it fails in prepareAsync. -- Thanks, Andy --~--~-~--~~~---~--~~ 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 -~--~~~~--~~--~--~---
