从像素缓冲区到设备上下文的最快方法(Fastest method for blitting from a pixel buffer into a device context)

 晚上好， 
 
 我在内存缓冲区中有几个32位图像，我希望快速将其“blit”到设备上下文。 速度是一个问题，因为缓冲区将被不断地操纵，需要反复进入DC。 
 
 缓冲区的颜色深度为32位，因此它已经是DIB预期的SetDIBits（）格式。 然而，这是相当麻烦的，因为在操作之前不能将SetDIBits（）的位图目标选择到DC中。 因此，我需要不断更换DC的位图，调用SetDIBits（），将位图交换回DC，然后将DC blit到Window的DC。 对我来说，这似乎是CPU上的大量工作量和Windows API中的过多分支; 对于最佳性能来说太过分了。 
 
 我有兴趣使用DirectX，如果它没有强迫我使用设备上下文进行2D操作，或者在显示之前将纹理上传到视频内存，因为图像的内容不断变化。 
 
 我的问题很简单（尽管篇幅很长）。 对于我来说，将图像从内存中的像素缓冲区blit到屏幕上的最快方法是什么？ 直接访问DC的像素缓冲区会很棒，但我知道这不会发生。 
 
 感谢您阅读我的长篇文章。 

Good evening,
 
I have several 32-bit images in memory buffers that I wish to "blit" to a device context, quickly. Speed is an issue here because the buffer will be manipulated constantly and need to be blitted to the DC repeatedly.
 
The color depth of the buffer is 32-bits, so it is already in the DIB-expected format of SetDIBits(). However, this is rather cumbersome since the bitmap target of SetDIBits() cannot be already selected into the DC prior to the operation. So I will need to constantly swap out the DC's bitmap, call SetDIBits(), swap the bitmap back into the DC, and then blit the DC to the Window's DC. To me, that just seems like a LOT of workload on the CPU and too much branching in the Windows API; way too much for optimal performance.
 
I would be interested in using DirectX if it didn't force me to use Device Contexts for 2D operations, or uploading textures to video memory before displaying them, because the contents of the image are constantly changing.
 
My question is simple (despite the long writeup). What would be the fastest way for me to blit an image from a pixel buffer in memory onto the screen? Direct access to the pixel buffer of a DC would be great, but I know that's not going to happen.
 
Thanks for reading my long writeup.

原文：https://stackoverflow.com/questions/4721078