Hi,
Its a newbie question. I have looked through various posts in Android-
porting and Android-platform.
I have also gone through the opencore documents in the doc folder.
I have the following requirement:
Access the H.264 decoder either directly or via OpenCore from my
application. I am not looking to playback via pvplayer.
Decode the H.264 frames (NAL) and pass the decoded frame back to my
application.
The file parsing, etc happens within my application. The decoder will
have to decode the input frame that the application provides.
Can you guide me on this?
I am unable to understand the starting point (class instance) for
accessing the H.264 codec.
Are there any documents for explaining how the Opencore components can
be used? Specifically for the use case described above. I guess, it
would be the usage of the H.264 decoder component.
Is it a VTC application?? curious to know the usecase..
Eclair 2.1 has minimal stagefright library, and it does 'almost'
exactly what you described below..
It reads, parses media files, sends buffer to PV OMX components (h264
inclusive), gets output buffers and frees it (does nothing in
eclair)..
To run stagefright: build stagefright (add BUILD_WITH_FULL_STAGEFRIGHT
:= true in ./buildspec.mk file and build while FS), run 'stagefright
<video-file>' to see the behavior..
Also refer the source
./frameworks/base/cmds/stagefright/stagefright.cpp
./frameworks/base/media/libstagefright/OMXCodec.cpp
On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
> Hi,
> Its a newbie question. I have looked through various posts in Android-
> porting and Android-platform.
> I have also gone through the opencore documents in the doc folder.
> I have the following requirement:
> Access the H.264 decoder either directly or via OpenCore from my
> application. I am not looking to playback via pvplayer.
> Decode the H.264 frames (NAL) and pass the decoded frame back to my
> application.
> The file parsing, etc happens within my application. The decoder will
> have to decode the input frame that the application provides.
> Can you guide me on this?
> I am unable to understand the starting point (class instance) for
> accessing the H.264 codec.
> Are there any documents for explaining how the Opencore components can
> be used? Specifically for the use case described above. I guess, it
> would be the usage of the H.264 decoder component.
> Is it a VTC application?? curious to know the usecase..
> Eclair 2.1 has minimal stagefright library, and it does 'almost'
> exactly what you described below..
> It reads, parses media files, sends buffer to PV OMX components (h264
> inclusive), gets output buffers and frees it (does nothing in
> eclair)..
> To run stagefright: build stagefright (add BUILD_WITH_FULL_STAGEFRIGHT
> := true in ./buildspec.mk file and build while FS), run 'stagefright
> <video-file>' to see the behavior..
> Also refer the source
> ./frameworks/base/cmds/stagefright/stagefright.cpp
> ./frameworks/base/media/libstagefright/OMXCodec.cpp
> No docs i've seen except source today..
> -Deva
> On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
> > Hi,
> > Its a newbie question. I have looked through various posts in Android-
> > porting and Android-platform.
> > I have also gone through the opencore documents in the doc folder.
> > I have the following requirement:
> > Access the H.264 decoder either directly or via OpenCore from my
> > application. I am not looking to playback via pvplayer.
> > Decode the H.264 frames (NAL) and pass the decoded frame back to my
> > application.
> > The file parsing, etc happens within my application. The decoder will
> > have to decode the input frame that the application provides.
> > Can you guide me on this?
> > I am unable to understand the starting point (class instance) for
> > accessing the H.264 codec.
> > Are there any documents for explaining how the Opencore components can
> > be used? Specifically for the use case described above. I guess, it
> > would be the usage of the H.264 decoder component.
On Fri, Apr 30, 2010 at 1:19 PM, shri <shrira...@gmail.com> wrote:
> Hi Deva,
> Thanks for the reply.
> Its not a VTC usecase. Just that, my application has its own engine
> and needs just the decoding part to happen outside.
> I was not able to find buildspec.mk.
> I saw usages of BUILD_WITH_FULL_STAGEFRIGHT - ( ifeq ($
> (BUILD_WITH_FULL_STAGEFRIGHT),true) )
> Am i missing anything?
> - shriram
> On Apr 29, 10:33 pm, Deva R <r.deva...@gmail.com> wrote:
>> Is it a VTC application?? curious to know the usecase..
>> Eclair 2.1 has minimal stagefright library, and it does 'almost'
>> exactly what you described below..
>> It reads, parses media files, sends buffer to PV OMX components (h264
>> inclusive), gets output buffers and frees it (does nothing in
>> eclair)..
>> To run stagefright: build stagefright (add BUILD_WITH_FULL_STAGEFRIGHT
>> := true in ./buildspec.mk file and build while FS), run 'stagefright
>> <video-file>' to see the behavior..
>> Also refer the source
>> ./frameworks/base/cmds/stagefright/stagefright.cpp
>> ./frameworks/base/media/libstagefright/OMXCodec.cpp
>> No docs i've seen except source today..
>> -Deva
>> On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
>> > Hi,
>> > Its a newbie question. I have looked through various posts in Android-
>> > porting and Android-platform.
>> > I have also gone through the opencore documents in the doc folder.
>> > I have the following requirement:
>> > Access the H.264 decoder either directly or via OpenCore from my
>> > application. I am not looking to playback via pvplayer.
>> > Decode the H.264 frames (NAL) and pass the decoded frame back to my
>> > application.
>> > The file parsing, etc happens within my application. The decoder will
>> > have to decode the input frame that the application provides.
>> > Can you guide me on this?
>> > I am unable to understand the starting point (class instance) for
>> > accessing the H.264 codec.
>> > Are there any documents for explaining how the Opencore components can
>> > be used? Specifically for the use case described above. I guess, it
>> > would be the usage of the H.264 decoder component.
Irrespective of whether using StageFright or OpenCORE, the method of
application providing demuxed input that can be passed directly to
decoders is not available via the MediaPlayer, yet.
-Ravi
On Apr 30, 5:12 am, Deva R <r.deva...@gmail.com> wrote:
> you can modify Android.mk so as to include libstagefright always..
> i guess if you dont have a ./buildspec.mk for you platform, i guess
> below generic file will come into picture..
> ./build/buildspec.mk.default
> can you playaroud and check w that?
> On Fri, Apr 30, 2010 at 1:19 PM, shri <shrira...@gmail.com> wrote:
> > Hi Deva,
> > Thanks for the reply.
> > Its not a VTC usecase. Just that, my application has its own engine
> > and needs just the decoding part to happen outside.
> > I was not able to find buildspec.mk.
> > I saw usages of BUILD_WITH_FULL_STAGEFRIGHT - ( ifeq ($
> > (BUILD_WITH_FULL_STAGEFRIGHT),true) )
> > Am i missing anything?
> > - shriram
> > On Apr 29, 10:33 pm, Deva R <r.deva...@gmail.com> wrote:
> >> Is it a VTC application?? curious to know the usecase..
> >> Eclair 2.1 has minimal stagefright library, and it does 'almost'
> >> exactly what you described below..
> >> It reads, parses media files, sends buffer to PV OMX components (h264
> >> inclusive), gets output buffers and frees it (does nothing in
> >> eclair)..
> >> To run stagefright: build stagefright (add BUILD_WITH_FULL_STAGEFRIGHT
> >> := true in ./buildspec.mk file and build while FS), run 'stagefright
> >> <video-file>' to see the behavior..
> >> Also refer the source
> >> ./frameworks/base/cmds/stagefright/stagefright.cpp
> >> ./frameworks/base/media/libstagefright/OMXCodec.cpp
> >> No docs i've seen except source today..
> >> -Deva
> >> On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
> >> > Hi,
> >> > Its a newbie question. I have looked through various posts in Android-
> >> > porting and Android-platform.
> >> > I have also gone through the opencore documents in the doc folder.
> >> > I have the following requirement:
> >> > Access the H.264 decoder either directly or via OpenCore from my
> >> > application. I am not looking to playback via pvplayer.
> >> > Decode the H.264 frames (NAL) and pass the decoded frame back to my
> >> > application.
> >> > The file parsing, etc happens within my application. The decoder will
> >> > have to decode the input frame that the application provides.
> >> > Can you guide me on this?
> >> > I am unable to understand the starting point (class instance) for
> >> > accessing the H.264 codec.
> >> > Are there any documents for explaining how the Opencore components can
> >> > be used? Specifically for the use case described above. I guess, it
> >> > would be the usage of the H.264 decoder component.
Has anyone tested stagefright with a video file? does it work?
once i enable all the macros how do I test stagefright player?
also what did you mean by
"
run 'stagefright
<video-file>' to see the behavior.
"
Also I saw one test app "/home/nimesh/android/frameworks/base/media/
tests/MediaFrameworkTest"
Does anyone know how to enable this test app and test the media player
using this?
On Apr 29, 10:33 pm, Deva R <r.deva...@gmail.com> wrote:
> Is it a VTC application?? curious to know the usecase..
> Eclair 2.1 has minimal stagefright library, and it does 'almost'
> exactly what you described below..
> It reads, parses media files, sends buffer to PV OMX components (h264
> inclusive), gets output buffers and frees it (does nothing in
> eclair)..
> To run stagefright: build stagefright (addBUILD_WITH_FULL_STAGEFRIGHT
> := true in ./buildspec.mk file and build while FS), run 'stagefright
> <video-file>' to see the behavior..
> Also refer the source
> ./frameworks/base/cmds/stagefright/stagefright.cpp
> ./frameworks/base/media/libstagefright/OMXCodec.cpp
> No docs i've seen except source today..
> -Deva
> On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
> > Hi,
> > Its a newbie question. I have looked through various posts in Android-
> > porting and Android-platform.
> > I have also gone through the opencore documents in the doc folder.
> > I have the following requirement:
> > Access the H.264 decoder either directly or via OpenCore from my
> > application. I am not looking to playback via pvplayer.
> > Decode the H.264 frames (NAL) and pass the decoded frame back to my
> > application.
> > The file parsing, etc happens within my application. The decoder will
> > have to decode the input frame that the application provides.
> > Can you guide me on this?
> > I am unable to understand the starting point (class instance) for
> > accessing the H.264 codec.
> > Are there any documents for explaining how the Opencore components can
> > be used? Specifically for the use case described above. I guess, it
> > would be the usage of the H.264 decoder component.
>Has anyone tested stagefright with a video file? does it work?
i've tested video/audio decoding using stagefright.. it works straight away
for PV OMX components, but required few fixes for our new hw codecs.
>once i enable all the macros how do I test stagefright player?
u can run below commands in android shell
'stagefright -h' will give all options.
'stagefirght <video-file>' will decode the file (no posting to overlay.,
decoded buffers are just free'd)
'stagefright -a <audio-file>' will decode audio file.,
>Does anyone know how to enable this test app and test the media player
using this?
just build by running 'make mediaframeworktest' in your android setup.
it will generate new 'mediaframeworktest.apk' in your <out>/.../data folder.
keep it in file system., you can test various media player api calls, and
video usecases by below command..,
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#<test-command>
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner
Just sure you have required file names, as specified in
.\frameworks\base\media\tests\MediaFrameworkTest\src\com\android\mediaframe worktest\MediaNames.java
PS.
few of video decoding tests i ran.
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testLargeVideo Heigth
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testLargeVideo Width
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoMP4Se ekTo
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoLong3 gpSeekTo
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH263A ACSeekTo
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH263A MRSeekTo
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH264A ACSeekTo
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH264A MRSeekTo
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoWMVSe ekTo
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testGetThumbna il
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testLocalH263A MRPrepareAsyncCallback
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testStreamPrep areAsyncCallback
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.functional.MediaPlayerApiTest#testStreamPrep areAsyncCallbackReset
-w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
am instrument -e class
com.android.mediaframeworktest.performance.MediaPlayerPerformance#testH263V ideoPlaybackMemoryUsage
-w com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner &
am instrument -e class
com.android.mediaframeworktest.performance.MediaPlayerPerformance#testH264V ideoPlaybackMemoryUsage
-w com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner &
am instrument -e class
com.android.mediaframeworktest.performance.MediaPlayerPerformance#testWMVVi deoPlaybackMemoryUsage
-w com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner &
am instrument -e class
com.android.mediaframeworktest.stress.MediaPlayerStressTest#testStressHWDec oderRelease
-w com.android.mediaframeworktest/.MediaRecorderStressTestRunner &
am instrument -e class
com.android.mediaframeworktest.stress.MediaPlayerStressTest#testStressGetCu rrentPosition
-w com.android.mediaframeworktest/.MediaRecorderStressTestRunner &
On Wed, May 19, 2010 at 8:48 PM, NimeshChanchani
<nimeshchanch...@gmail.com>wrote:
> Has anyone tested stagefright with a video file? does it work?
> once i enable all the macros how do I test stagefright player?
> also what did you mean by
> "
> run 'stagefright
> <video-file>' to see the behavior.
> "
> Also I saw one test app "/home/nimesh/android/frameworks/base/media/
> tests/MediaFrameworkTest"
> Does anyone know how to enable this test app and test the media player
> using this?
> On Apr 29, 10:33 pm, Deva R <r.deva...@gmail.com> wrote:
> > Is it a VTC application?? curious to know the usecase..
> > Eclair 2.1 has minimal stagefright library, and it does 'almost'
> > exactly what you described below..
> > It reads, parses media files, sends buffer to PV OMX components (h264
> > inclusive), gets output buffers and frees it (does nothing in
> > eclair)..
> > To run stagefright: build stagefright (addBUILD_WITH_FULL_STAGEFRIGHT
> > := true in ./buildspec.mk file and build while FS), run 'stagefright
> > <video-file>' to see the behavior..
> > Also refer the source
> > ./frameworks/base/cmds/stagefright/stagefright.cpp
> > ./frameworks/base/media/libstagefright/OMXCodec.cpp
> > No docs i've seen except source today..
> > -Deva
> > On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
> > > Hi,
> > > Its a newbie question. I have looked through various posts in Android-
> > > porting and Android-platform.
> > > I have also gone through the opencore documents in the doc folder.
> > > I have the following requirement:
> > > Access the H.264 decoder either directly or via OpenCore from my
> > > application. I am not looking to playback via pvplayer.
> > > Decode the H.264 frames (NAL) and pass the decoded frame back to my
> > > application.
> > > The file parsing, etc happens within my application. The decoder will
> > > have to decode the input frame that the application provides.
> > > Can you guide me on this?
> > > I am unable to understand the starting point (class instance) for
> > > accessing the H.264 codec.
> > > Are there any documents for explaining how the Opencore components can
> > > be used? Specifically for the use case described above. I guess, it
> > > would be the usage of the H.264 decoder component.
but I guess i'm having trouble with buildspec.mk .
i copied buildspec.mk.default to buildspec.mk . added
BUILD_WITH_FULL_STAGEFRIGHT. And I also changed TARGET_BUILD_TYPE to
debug.
but when i "make cleaned" and then gave
make , I got the following : .It has got TARGET_BUILD_TYPE=release
instead of debug. This makes me wonder if the changes that i did in
buildspec.mk are being effected?
> >Has anyone tested stagefright with a video file? does it work?
> i've tested video/audio decoding using stagefright.. it works straight away
> for PV OMX components, but required few fixes for our new hw codecs.
> >once i enable all the macros how do I test stagefright player?
> u can run below commands in android shell
> 'stagefright -h' will give all options.
> 'stagefirght <video-file>' will decode the file (no posting to overlay.,
> decoded buffers are just free'd)
> 'stagefright -a <audio-file>' will decode audio file.,
> >Also I saw one test app
> "/home/nimesh/android/frameworks/base/media/tests/MediaFrameworkTest">Does anyone know how to enable this test app and test the media player
> using this?
> just build by running 'make mediaframeworktest' in your android setup.
> it will generate new 'mediaframeworktest.apk' in your <out>/.../data folder.
> keep it in file system., you can test various media player api calls, and
> video usecases by below command..,
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#<test-command>
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner
> Just sure you have required file names, as specified in
> .\frameworks\base\media\tests\MediaFrameworkTest\src\com\android\mediaframe worktest\MediaNames.java
> PS.
> few of video decoding tests i ran.
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testLargeVideo Heigth
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testLargeVideo Width
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoMP4Se ekTo
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoLong3 gpSeekTo
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH263A ACSeekTo
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH263A MRSeekTo
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH264A ACSeekTo
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoH264A MRSeekTo
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testVideoWMVSe ekTo
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testGetThumbna il
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testLocalH263A MRPrepareAsyncCallback
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testStreamPrep areAsyncCallback
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.functional.MediaPlayerApiTest#testStreamPrep areAsyncCallbackReset
> -w com.android.mediaframeworktest/.MediaFrameworkTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.performance.MediaPlayerPerformance#testH263V ideoPlaybackMemoryUsage
> -w com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.performance.MediaPlayerPerformance#testH264V ideoPlaybackMemoryUsage
> -w com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.performance.MediaPlayerPerformance#testWMVVi deoPlaybackMemoryUsage
> -w com.android.mediaframeworktest/.MediaFrameworkPerfTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.stress.MediaPlayerStressTest#testStressHWDec oderRelease
> -w com.android.mediaframeworktest/.MediaRecorderStressTestRunner &
> am instrument -e class
> com.android.mediaframeworktest.stress.MediaPlayerStressTest#testStressGetCu rrentPosition
> -w com.android.mediaframeworktest/.MediaRecorderStressTestRunner &
> On Wed, May 19, 2010 at 8:48 PM, NimeshChanchani
> <nimeshchanch...@gmail.com>wrote:
> > Has anyone tested stagefright with a video file? does it work?
> > once i enable all the macros how do I test stagefright player?
> > also what did you mean by
> > "
> > run 'stagefright
> > <video-file>' to see the behavior.
> > "
> > Also I saw one test app "/home/nimesh/android/frameworks/base/media/
> > tests/MediaFrameworkTest"
> > Does anyone know how to enable this test app and test the media player
> > using this?
> > On Apr 29, 10:33 pm, Deva R <r.deva...@gmail.com> wrote:
> > > Is it a VTC application?? curious to know the usecase..
> > > Eclair 2.1 has minimal stagefright library, and it does 'almost'
> > > exactly what you described below..
> > > It reads, parses media files, sends buffer to PV OMX components (h264
> > > inclusive), gets output buffers and frees it (does nothing in
> > > eclair)..
> > > To run stagefright: build stagefright (addBUILD_WITH_FULL_STAGEFRIGHT
> > > := true in ./buildspec.mk file and build while FS), run 'stagefright
> > > <video-file>' to see the behavior..
> > > Also refer the source
> > > ./frameworks/base/cmds/stagefright/stagefright.cpp
> > > ./frameworks/base/media/libstagefright/OMXCodec.cpp
> > > No docs i've seen except source today..
> > > -Deva
> > > On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
> > > > Hi,
> > > > Its a newbie question. I have looked through various posts in Android-
> > > > porting and Android-platform.
> > > > I have also gone through the opencore documents in the doc folder.
> > > > I have the following requirement:
> > > > Access the H.264 decoder either directly or via OpenCore from my
> > > > application. I am not looking to playback via pvplayer.
> > > > Decode the H.264 frames (NAL) and pass the decoded frame back to my
> > > > application.
> > > > The file parsing, etc happens within my application. The decoder will
> > > > have to decode the input frame that the application provides.
> > > > Can you guide me on this?
> > > > I am unable to understand the starting point (class instance) for
> > > > accessing the H.264 codec.
> > > > Are there any documents for explaining how the Opencore components can
> > > > be used? Specifically for the use case described above. I guess, it
> > > > would be the usage of the H.264 decoder component.
> but I guess i'm having trouble with buildspec.mk .
> i copied buildspec.mk.default to buildspec.mk . added
> BUILD_WITH_FULL_STAGEFRIGHT. And I also changed TARGET_BUILD_TYPE to
> debug.
> but when i "make cleaned" and then gave
> make , I got the following : .It has got TARGET_BUILD_TYPE=release
> instead of debug. This makes me wonder if the changes that i did in
> buildspec.mk are being effected?
> On May 19, 8:34 pm, Deva R <r.deva...@gmail.com> wrote:
>> >Has anyone tested stagefright with a video file? does it work?
>> i've tested video/audio decoding using stagefright.. it works straight
away
>> for PV OMX components, but required few fixes for our new hw codecs.
>> >once i enable all the macros how do I test stagefright player?
>> u can run below commands in android shell
>> 'stagefright -h' will give all options.
>> 'stagefirght <video-file>' will decode the file (no posting to overlay.,
>> decoded buffers are just free'd)
>> 'stagefright -a <audio-file>' will decode audio file.,
>> >Also I saw one test app
"/home/nimesh/android/frameworks/base/media/tests/MediaFrameworkTest">Does
anyone know how to enable this test app and test the media player
>> using this?
>> just build by running 'make mediaframeworktest' in your android setup.
>> it will generate new 'mediaframeworktest.apk' in your <out>/.../data
folder.
>> keep it in file system., you can test various media player api calls, and
>> video usecases by below command..,
>> On Wed, May 19, 2010 at 8:48 PM, NimeshChanchani
>> <nimeshchanch...@gmail.com>wrote:
>> > Has anyone tested stagefright with a video file? does it work?
>> > once i enable all the macros how do I test stagefright player?
>> > also what did you mean by
>> > "
>> > run 'stagefright
>> > <video-file>' to see the behavior.
>> > "
>> > Also I saw one test app "/home/nimesh/android/frameworks/base/media/
>> > tests/MediaFrameworkTest"
>> > Does anyone know how to enable this test app and test the media player
>> > using this?
>> > On Apr 29, 10:33 pm, Deva R <r.deva...@gmail.com> wrote:
>> > > Is it a VTC application?? curious to know the usecase..
>> > > Eclair 2.1 has minimal stagefright library, and it does 'almost'
>> > > exactly what you described below..
>> > > It reads, parses media files, sends buffer to PV OMX components (h264
>> > > inclusive), gets output buffers and frees it (does nothing in
>> > > eclair)..
>> > > To run stagefright: build stagefright (addBUILD_WITH_FULL_STAGEFRIGHT
>> > > := true in ./buildspec.mk file and build while FS), run 'stagefright
>> > > <video-file>' to see the behavior..
>> > > Also refer the source
>> > > ./frameworks/base/cmds/stagefright/stagefright.cpp
>> > > ./frameworks/base/media/libstagefright/OMXCodec.cpp
>> > > No docs i've seen except source today..
>> > > -Deva
>> > > On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
>> > > > Hi,
>> > > > Its a newbie question. I have looked through various posts in
Android-
>> > > > porting and Android-platform.
>> > > > I have also gone through the opencore documents in the doc folder.
>> > > > I have the following requirement:
>> > > > Access the H.264 decoder either directly or via OpenCore from my
>> > > > application. I am not looking to playback via pvplayer.
>> > > > Decode the H.264 frames (NAL) and pass the decoded frame back to my
>> > > > application.
>> > > > The file parsing, etc happens within my application. The decoder
will
>> > > > have to decode the input frame that the application provides.
>> > > > Can you guide me on this?
>> > > > I am unable to understand the starting point (class instance) for
>> > > > accessing the H.264 codec.
>> > > > Are there any documents for explaining how the Opencore components
can
>> > > > be used? Specifically for the use case described above. I guess, it
>> > > > would be the usage of the H.264 decoder component.
> but I guess i'm having trouble with buildspec.mk .
> i copied buildspec.mk.default to buildspec.mk . added
> BUILD_WITH_FULL_STAGEFRIGHT. And I also changed TARGET_BUILD_TYPE to
> debug.
> but when i "make cleaned" and then gave
> make , I got the following : .It has got TARGET_BUILD_TYPE=release
> instead of debug. This makes me wonder if the changes that i did in
> buildspec.mk are being effected?
> On May 19, 8:34 pm, Deva R <r.deva...@gmail.com> wrote:
> > >Has anyone tested stagefright with a video file? does it work?
> > i've tested video/audio decoding using stagefright.. it works straight
> away
> > for PV OMX components, but required few fixes for our new hw codecs.
> > >once i enable all the macros how do I test stagefright player?
> > u can run below commands in android shell
> > 'stagefright -h' will give all options.
> > 'stagefirght <video-file>' will decode the file (no posting to overlay.,
> > decoded buffers are just free'd)
> > 'stagefright -a <audio-file>' will decode audio file.,
> > >Also I saw one test app
> "/home/nimesh/android/frameworks/base/media/tests/MediaFrameworkTest">Does
> anyone know how to enable this test app and test the media player
> > using this?
> > just build by running 'make mediaframeworktest' in your android setup.
> > it will generate new 'mediaframeworktest.apk' in your <out>/.../data
> folder.
> > keep it in file system., you can test various media player api calls, and
> > video usecases by below command..,
> > On Wed, May 19, 2010 at 8:48 PM, NimeshChanchani
> > <nimeshchanch...@gmail.com>wrote:
> > > Has anyone tested stagefright with a video file? does it work?
> > > once i enable all the macros how do I test stagefright player?
> > > also what did you mean by
> > > "
> > > run 'stagefright
> > > <video-file>' to see the behavior.
> > > "
> > > Also I saw one test app "/home/nimesh/android/frameworks/base/media/
> > > tests/MediaFrameworkTest"
> > > Does anyone know how to enable this test app and test the media player
> > > using this?
> > > On Apr 29, 10:33 pm, Deva R <r.deva...@gmail.com> wrote:
> > > > Is it a VTC application?? curious to know the usecase..
> > > > Eclair 2.1 has minimal stagefright library, and it does 'almost'
> > > > exactly what you described below..
> > > > It reads, parses media files, sends buffer to PV OMX components (h264
> > > > inclusive), gets output buffers and frees it (does nothing in
> > > > eclair)..
> > > > To run stagefright: build stagefright (addBUILD_WITH_FULL_STAGEFRIGHT
> > > > := true in ./buildspec.mk file and build while FS), run 'stagefright
> > > > <video-file>' to see the behavior..
> > > > Also refer the source
> > > > ./frameworks/base/cmds/stagefright/stagefright.cpp
> > > > ./frameworks/base/media/libstagefright/OMXCodec.cpp
> > > > No docs i've seen except source today..
> > > > -Deva
> > > > On Thu, Apr 29, 2010 at 3:17 PM, shri <shrira...@gmail.com> wrote:
> > > > > Hi,
> > > > > Its a newbie question. I have looked through various posts in
> Android-
> > > > > porting and Android-platform.
> > > > > I have also gone through the opencore documents in the doc folder.
> > > > > I have the following requirement:
> > > > > Access the H.264 decoder either directly or via OpenCore from my
> > > > > application. I am not looking to playback via pvplayer.
> > > > > Decode the H.264 frames (NAL) and pass the decoded frame back to my
> > > > > application.
> > > > > The file parsing, etc happens within my application. The decoder
> will
> > > > > have to decode the input frame that the application provides.
> > > > > Can you guide me on this?
> > > > > I am unable to understand the starting point (class instance) for
> > > > > accessing the H.264 codec.
> > > > > Are there any documents for explaining how the Opencore components
> can
> > > > > be used? Specifically for the use case described above. I guess, it
> > > > > would be the usage of the H.264 decoder component.
