equal
deleted
inserted
replaced
34 Surfaces</xref> </p> </li> |
34 Surfaces</xref> </p> </li> |
35 </ul> </section> |
35 </ul> </section> |
36 <section><title>Architecture</title> <p>The Video Renderer can be implemented |
36 <section><title>Architecture</title> <p>The Video Renderer can be implemented |
37 in two different ways, as shown in the following diagram: </p> <fig id="GUID-33691E6E-8B90-579B-876B-6F14E953BB7C"> |
37 in two different ways, as shown in the following diagram: </p> <fig id="GUID-33691E6E-8B90-579B-876B-6F14E953BB7C"> |
38 <title> The two Video Renderer architectures </title> |
38 <title> The two Video Renderer architectures </title> |
39 <image href="GUID-BE11D652-3B39-51D2-ACE9-571E8EB71E94_d0e534503_href.png" placement="inline"/> |
39 <image href="GUID-BE11D652-3B39-51D2-ACE9-571E8EB71E94_d0e541963_href.png" placement="inline"/> |
40 </fig> <p> <b>Note</b>: For simplicity, only the Multimedia Framework client/controller |
40 </fig> <p> <b>Note</b>: For simplicity, only the Multimedia Framework client/controller |
41 thread boundary has been shown; other thread boundaries may exist. </p> <p>In |
41 thread boundary has been shown; other thread boundaries may exist. </p> <p>In |
42 both architectures, the <xref href="GUID-0EE3180B-4814-517E-A6DD-748136C17D55.dita">Video |
42 both architectures, the <xref href="GUID-0EE3180B-4814-517E-A6DD-748136C17D55.dita">Video |
43 Client API</xref> (<xref href="GUID-42D1182F-46D8-3C78-8D3C-C1BB465FCA1F.dita"><apiname>CVideoPlayerUtility2</apiname></xref>) is responsible |
43 Client API</xref> (<xref href="GUID-42D1182F-46D8-3C78-8D3C-C1BB465FCA1F.dita"><apiname>CVideoPlayerUtility2</apiname></xref>) is responsible |
44 for retrieving graphics surface handles from the video player controller and |
44 for retrieving graphics surface handles from the video player controller and |