android player, how to call hardware solution

            


I would like to call the player in direct decoding hardware solution, the underlying is not very familiar with, probably know something next OMX and the like, but still do not know how to call direct hardware decoding, do not know whether directly through java layer calls , but also look great God urged January
Reply:
Not like it, the .java layer determined by the underlying estimation can not decide
Reply:

quote landlord lucherr reply:

I think the player in decoding hardware solution called directly on the bottom is not very familiar with, probably know the next OMX like stuff, but still do not know how to call direct hardware decoding, do not know whether to call directly through java layer, but also look great God urged January

Thank you for your reply, that if I want to set the way for decoding hardware solution, then call the underlying modify decoded directly by jni hard solution feasible?
Like mxplayer did not know where to start
Reply:
I think the so-called third-party player to call hardware solution is to call the system mediaplayer, while soft solution is to call your own realization player, based on the ffmpeg. native has called prefer, is to have the time and the presence of soft solutions hardware solutions, priority call perfer
Reply:
Thank you for your reply, I would like to ask to call the system call awesomeplayer mediaplayer refers like it? You need directly through jni call? ffmpeg software solution it belongs to? For I want to achieve this function, do not know that you have no plan, I saw mx player and rock plyer which has switching hardware solutions and software solutions, do not know specifically how to achieve, I saw rock player Useful to ffmpeg, but do not know the specific principles, under the guidance of hope
Reply:

quote 3rd floor shcalm reply:

I think the so-called third-party player to call hardware solution is to call the system mediaplayer, while soft solution is to call your own implementation player, based on the ffmpeg. native has called prefer, it is to have the time and the presence of soft solutions hardware solutions, priority call perfer

Thank you for your reply, I would like to ask to call the system call awesomeplayer mediaplayer refers like it? You need directly through jni call? ffmpeg software solution it belongs to? For I want to achieve this function, do not know that you have no plan, I saw mx player and rock plyer which has switching hardware solutions and software solutions, do not know specifically how to achieve, I saw rock player Useful to ffmpeg, but do not know the specific principles, under the guidance of hope
Reply:
I think you call mediaplayer hardware solution on the line, because the solution can only be so hard to do, then soft solution if you need to add formats supported, you need a transplant ffmpeg
Reply:

quote, 6th Floor shcalm reply:

I think hardware solutions you can call mediaplayer on the line, because the hardware solution can only be so to do, the soft solution, then if you need increased format support, we need a transplant ffmpeg

Oh, you mean direct calls mediaplayer java layer? It defaults to first find it hard solution? Format hard solution is not too libstagefrighthw.so support provided by the manufacturers to decide?
Reply:
Format just container, look hard to see the solution or software solution is an encoding format H263, H264 like nothing relationship with container. Platform-specific framework written inside dead
Reply:

quote 8th floor shcalm reply:

format only container, look hard to see the solution or software solution is an encoding format H263, H264 like nothing with container relationship. Platform-specific framework written inside dead

Oh, a lot clearer! You look at me right now an understanding: calling java layer mediaplayer to play when the hardware solution will be called by default, if the device does not support the system will call the soft solution, if you want to customize the decoder can write their own respective decoder, or the introduction of such ffmpeg codec library implementation, hope pointing
Reply:
Learning the
Reply:

quote 9th floor lucherr reply:

Quote: quote, 8th Floor shcalm reply:

Format just container, look hard to see the solution or software solution is an encoding format H263, H264 like nothing relationship with container. Platform-specific framework written inside dead

Oh, a lot clearer! You look at me right now an understanding: calling java layer mediaplayer to play when the hardware solution will be called by default, if the device does not support the system will call the soft solution, if you want to customize the decoder can write their own respective decoder, or the introduction of such ffmpeg codec library implementation, hope pointing

System for certain decoding format corresponding hardware solution or software solution implementation, will be found in the registration map inside. If not want to expand the decoder manufacturers, are generally introduced ffmpeg. Currently available in the market are basically
Reply:

quote the 11th floor shcalm reply:

System decoding formats for some hardware solution or software solution corresponding implementation, will be found in the registration map inside. If not want to expand the decoder manufacturers, are generally introduced ffmpeg. The current market basically

Oh, thank you for your guidance, I have a lot clearer now, thanks again
Reply:
I also clearly a lot
Reply:
A slight gain, thanks
Reply:
If you now want to write a own player, hard solutions in native c layer no api? For example, you know what format the hard solution api support?
On the third floor said mediaplayer refers stagefright / awesomeplayer or java layer open mediaplayer? Hardware solution with respect to the advantages of software solutions that can reduce cpu utilization, and efficiency of the hardware layer code is definitely better than the story.
If referring to the java layer open mediaPlayer, that player development, then if you want to use hardware solution, in accordance with the third floor of a friend's statement is totally directly mediaPlayer to play? But Android's mediaplayer actually very poor HLS support, the ability to substantially zero fault tolerance (one of the reasons to write your own player).