admin/webrtc_m130
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

DxgiOutputDuplicator AcquireNextFrame timeout can be 0

Browse Source 
Timeout of AcquireNextFrame() can be 0. Though MSDN does not state it clear, I
tried it on my laptop, it works well, with almost zero capture time.
The screenshot is at https://drive.google.com/open?id=0B0OFNI4uoZGRNVZxekxCbm0ycmc.

BUG=682112

Review-Url: https://codereview.webrtc.org/2712353002
Cr-Commit-Position: refs/heads/master@{#16953}
This commit is contained in:
zijiehe 2017-03-01 11:45:37 -08:00 committed by Commit bot
parent 2100c0ba13
commit 634fcb32e3
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
webrtc/modules/desktop_capture/win/dxgi_output_duplicator.cc
View File

@ -33,8 +33,8 @@ namespace {
// Timeout for AcquireNextFrame() call.
// DxgiDuplicatorController leverages external components to do the capture
// scheduling. So here DxgiOutputDuplicator does not need to actively wait for a
// new frame. 1 millisecond is the minimium value AcquireNextFrame() accepts.
const int kAcquireTimeoutMs = 1;
// new frame.
const int kAcquireTimeoutMs = 0;
DesktopRect RECTToDesktopRect(const RECT& rect) {
return DesktopRect::MakeLTRB(rect.left, rect.top, rect.right, rect.bottom);