Comparison of the effects of using GDI, direct, and DirectDraw in tcpmp

I discussed with ZL earlier about using tcpmp to play videos in wince6.0. He believes that direct video writing should make video playing smoother. Today, I tested it on our platform and made benchmark using the following methods: GDI, direct, and DirectDraw. Direct is what he calls Direct Writing and video storage.

To enable tcpmp to support direct mode, you need to modify the relatedCodeTo directly access the video memory of the CE device. The specific method will not be described here. Please refer to the previous article. As mentioned in the previous article, the methods provided here can only be used for special purposes, and some optimizations are made for their own platforms. After implementing the direct method, you can see several methods supported by the system in Options> video settings, as shown in.

 

The video file used for testing is miniplayer.mp4, an advertisement in M8. The comparison of the test reports in three modes is as follows.

The above is a comparison between direct and GDI. We can see that direct is faster than GDI, and the average speed of the former is 10% higher than that of the latter.

The comparison between direct and DirectDraw is shown below. We can see that the two of them are basically equal to each other.

In addition, when tcpmp is started in wince6.0, some abnormal printing information is displayed. If it looks uncomfortable, you can modify the 78th line code of CPU. C and change it to "# If! Defined (target_palmos )&&! Defined (target_symbian )&&! Defined (target_wince) ", that is, do not call functions such as checkarm5e.