Media (Intel® Video Processing Library, Intel Media SDK)
Access community support with transcoding, decoding, and encoding in applications using media tools like Intel® oneAPI Video Processing Library and Intel® Media SDK
Announcements
The Intel Media SDK project is no longer active. For continued support and access to new features, Intel Media SDK users are encouraged to read the transition guide on upgrading from Intel® Media SDK to Intel® Video Processing Library (VPL), and to move to VPL as soon as possible.
For more information, see the VPL website.
3058 Discussions

IDirect3DDevice9::UpdateSurface vs LockRect/UnlockRect

celli4
New Contributor I
‎05-15-2013 06:35 PM
311 Views

I am experimenting with encoding from system memory, and I had the following thought.

Just wondering if anybody at Intel thinks there would be speed benefits to using UpdateSurface() to load D3D surfaces from system memory during encoding rather than use LockRect()/UnlockRect() as per the examples.

Thanks

Cameron

0 Kudos

Link Copied

1 Reply
Petter_L_Intel
Employee
‎05-15-2013 11:27 PM
311 Views

Hi Cameron,

As far as I know this is not something we have explored. But that approach seems to be somewhat constrained, since you would somehow have to store your system memory surfaces in a D3D surface container. Anyways, I've personally not explored this.

If you find a suitable way of doing this which brings good performance, feel free to share your findings on this forum.

BTW. if you are using system memory surfaces as input to the encoder.you do not have to lock surface ahead of copying data into it.

Regards,
Petter 

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.