- Video applications must use video hardware codecs.
- In video scenarios, the dedicated video decoder (VDEC) should be used, which has a significantly better power consumption efficiency than the CPU software decoding. Therefore, you are advised to use the VDEC of the platform for video playback.
Call the OH_AVCodec APIs to use the video hardware codec for video processing.
// To create a decoder using a codec name, if the application has special requirements, such as selecting a decoder that supports a certain resolution specification, // the capability can be queried first, and then the decoder can be created based on the codec name. OH_AVCapability *capability = OH_AVCodec_GetCapability(OH_AVCODEC_MIMETYPE_VIDEO_AVC, false); const char *name = OH_AVCapability_GetName(capability); // Create a decoder through mimetype // Hard solution: Create H264 decoder. When there are multiple optional decoders, the system will create the most suitable decoder OH_AVCodec *videoDec = OH_VideoDecoder_CreateByMime(OH_AVCODEC_MIMETYPE_VIDEO_AVC); // Hard solution: Create H265 decoder OH_AVCodec *videoDecH = OH_VideoDecoder_CreateByMime(OH_AVCODEC_MIMETYPE_VIDEO_HEVC);
Debugging and Verification
- Method 1: In the Command Prompt window, execute the hdc shell top command to check the CPU usage of top-running processes. If the CPU load of the av_codec_service process exceeds 5%, video hardware decoding has been enabled.
- Method 2: Use the Profiler in DevEco Studio to capture systrace.
Verify the load of the av_codec_service process via Systrace, as shown below. Frequent process wakeups with actual function executions indicate that hardware video decoding is active.
