CIF to HD

Hi Tushar,

Can you please provide more details on the requirement? For example, two scenarios I can think of are as follows:

1) Input of H.264 CIF via TFTP get --> Decoding to CIF YUV --> Upscaling to 720p YUV --> 720p YUV output via TFTP put

2) Input of H.264 CIF via TFTP get --> Decoding to CIF YUV --> Upscaling to 720p YUV --> encoding to 720p H.264 --> 720p H.264 output via TFTP put

Is it required to be real-time? If so, what is the FPS?

There are three builds in MCSDK Video 2.0:

1) sv01: full-fledged real-time video demos with multiple codecs integrated, supporting transcoding, scaling, overlay, and etc.

2) sv04: allow integration and testing of individual codecs with data IO via TFTP, encode only or decode only. 

3) transcode example: simple example of H264-->H264 transcoding on single core, data IO via TFTP.

Upon details of your requirement, we can select an appropriate build to start. In MCSDK Video 2.0, scaling is done with YUV data. It is integrated in sv01, but not part of sv04 or transcode example.

Thanks,

Hongmei

Hi Hongmei,

I Want to work with Input of H.264 CIF via TFTP get --> Decoding to CIF YUV --> Upscaling to 720p YUV --> encoding to 720p H.264 --> 720p H.264 output via TFTP put

and fps should be 60 and can i get sv01 in ccs project format.

Hi Tushar,

Using TFTP, we cannot do real-time video data IO (e.g., 60fps as you specified). Is 60fps or real-time a must-have for your use case? If not, we can start with the simple transcode example and then add in scaling.

Thanks,

Hongmei

Tushar,

At 720p, each YUV 420 frame is 1382400 bytes. For 720p60 the data rate is 82,944,000 bytes/sec.  Assuming an MTU size of 1460 bytes per packet, it results to 56,810 packets per second. TFTP requires an ACK to be sent for every packet. TFTP is manageable for datarates of 1-2000 packets per sec (primarily for compressed bitstreams, not raw YUV data).

For realtime 720p60 data you need faster peripheral (PCIe, SRIO etc) to get the raw YUV data. 

Regards,

Vivek