Help Center/
Atlas 300 Application (Model 3000)/
DVPP API Reference/
Appendix/
Sample Usage of the DVPP Executor/
VDEC Usage
Updated on 2022-03-13 GMT+08:00
VDEC Usage
./sample_dvpp_hlt_ddk --in_image_file dvpp_vdec_h264_1frame_bp_51_1920x1080.h264 --out_image_file h264_image --in_format 0 --test_type 3 ./sample_dvpp_hlt_ddk --in_image_file dvpp_vdec_h265_1frame_mp_51_1920x1080.h265 --out_image_file h265_image --in_format 1 --test_type 3
Sample description: The preceding commands call the VDEC to decode H.264 and H.265 streams and call the VPC to generate YUV images.
- Input video:
- The stream has the width of 1920 pixels, height of 1080 pixels, and file name of dvpp_vdec_h264_1frame_bp_51_1920x1080.h264.
- The stream has the width of 1920 pixels, height of 1080 pixels, and file name of dvpp_vdec_h265_1frame_mp_51_1920x1080.h265.
- The video files are in the same directory as the executable file.
- Output image:
- The output image is in YUV420SP format and has the width of 1920 pixels and height of 1080 pixels.
- For the decoding of H.264 streams, an image named h264_image* is generated in the output_dir directory. Only one image is output because the current video contains only one frame. If the video contains multiple frames, multiple images will be output.
- For the decoding of H.265 streams, an image named h265_image* is generated in the output_dir directory. Only one image is output because the current video contains only one frame. If the video contains multiple frames, multiple images will be output.
- You can open the h264_image* and h265_image* files by using image display software to verify the correctness.
Parent topic: Sample Usage of the DVPP Executor
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
The system is busy. Please try again later.
For any further questions, feel free to contact us through the chatbot.
Chatbot