![]() In fact, MediaCodec is more like an intermediate layer. Then,Why? Brief analysis of codemedic architectureīecause Android is a platform with a variety of hardware manufacturers, and MediaCodec is not a hardware manufacturer, it does not provide hardware encoding and decoding solutions. Therefore, we still refer to demuxing_decoding.c to realize MediaCodec hard decoding on Android platform. Trying to reference hw_decode.c in the process of realizing MediaCodec hard decoding, avcodec in 195 lines_ get_ hw_ Config failed. ![]() However, the decoding of MediaCodec on Android platform has not been realized. Referring to this file, we can implement hardware decoding on Linux or Windows platforms by using the hard decoding function implemented by cuvid, NVIDIA, Intel and other hardware manufacturers. It looks like a demo of hardware decoding. It is suggested that novices can refer to the second scheme.Īs for the third document, hw_decode.c. In fact, the schemes of the first two files are similar, except that the first one is for bare h264 streams and the second one is for encapsulated video files. ![]() However, about video decoding, there is decode in the official source code of FFmpeg_ video. It should be the fastest idea to refer to the relevant function implementation of examples in the official source code of FFmpeg to realize your own program design. Therefore, it is necessary to engage in hardware decoding at the mobile terminal to accelerate the decoding speed and release some CPU resources at the same time. The 1080p video is OK, but up to 2k and 4k, the decoding speed (decoding a frame at the speed visible to the naked eye) can't stand it. The pure FFmpeg method can also be implemented on the mobile terminal, but the efficiency is indeed slower. Recently, when doing mobile audio and video coding and decoding, the first thing to realize is the decoding function of mobile video.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |