![]() ![]() For the transcode and sv04 CCS projects, since there are at most two channels, we are directly using .c. cmd files can be generated for multi-core and multi-channel use case. ![]() *.beh, *.bec, *.becmd files are parsed by Active Perl during the making process so that. Sv01 is a multi-core and multi-channel application. Meanwhile, please remove siuVigdkCodecMgr.c from your project. Those functions are used only by VPPU-Rx. Since you are using only VPPU-Tx, you can replace gmpAllocGmc, gmpFreeGmc, and siuRxVideoPost with NULL in vppuContext after adding it in dsp\gg\ggCodecTestCfg.c. For sv04 debugging, as sv04.out is loaded through CCS, it can be debugged in the same way as a. sv04 make instructions can be found from. ![]() If a source file of sv04 is modified, you can just rerun the make command to rebuild sv04.out. After the compilation is completed, you can get the list of files from what are included in dsp\mkrel\sv04\flat directory. One way to identify the source files is making sv04 with "FLAT=YES". In MCSDK Video 2.0, H264BP encoder and H264HP decoder have been integrated in sv04, and can be used as is.įor your use case of 1-channel 1080p H264 encoding, we would like to recommend starting with sv04. Adding a codec to sv04 is straightforward as described in. It is single video channel, and each testing is for a single codec as configured in. Sv04 is developed for integrating and testing individual codecs with data IO via TFTP. Sv01 is a full-fledged video demo which has such features as: 1) multiple C6678 video codecs (as seen are integrated, 2) supports multiple transcoding channels 3) supports multiple resolutions from QCIF to 1080p 4) supports three channel models: encode only, decode only, and transcode 5) supports core-core transcoding and multi-core encoding/decoding 6) demo runs in real-time. Sample code of VPPU and RCU can be found from sv01. 2) NEU module has been integrated an used in both the transcode example and sv04. Then, the TFTP-GET can be replaced with a faster data input method.įor your earlier questions: 1) RTP output can be played out via MPlayer on a PC, as demonstrated in MCSDK Video real-time demo ( ). out file from a CCS project.įrom sv04, the first step can be focusing on adding RTP for the encoded output while still using TFTP to get the YUV input. After getting the sv04.out, it can be loaded in CCS and then debugged in the same way as a. Therefore, the steps 2)-4) for adding RTP support in our earlier reply are still applicable to sv04. Similar to the transcode example, it also uses TFTP for data I/O. sv04 supports mullti-core H.264BP encoding and also the mode of encoding only. Instead, a better starting point would be sv04: codec integration and test application ( ). Since the transcode example in CCS is a single-core demonstration, it may not be suitable for further developing your demo. 1080p H264 needs 2-3 cores for the encoding itself. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |