Skip to content

Commit 3b39fa1

Browse files
AvasamAvasam
authored
Added new Capture Method system for more capture options + utils (#141)
* Add D3DShot types from python/typeshed#8652 * New Capture Method system
1 parent 6b928ca commit 3b39fa1

37 files changed

+1549
-260
lines changed

‎README.md

+24-4
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ This program can be used to automatically start, split, and reset your preferred
6161

6262
## Avg. FPS
6363

64-
- Calculates the average comparison rate of the capture region to split images. This value will likely be much higher than needed (unless you [Force Full-Content-Rendering](#Full-Content-Rendering)), so it is highly recommended to limit your FPS depending on the frame rate of the game you are capturing.
64+
- Calculates the average comparison rate of the capture region to split images. This value will likely be much higher than needed, so it is highly recommended to limit your FPS depending on the frame rate of the game you are capturing.
6565

6666
## OPTIONS
6767

@@ -72,9 +72,29 @@ This program can be used to automatically start, split, and reset your preferred
7272
- Histograms: An explanation on Histograms comparison can be found [here](https://mpatacchiola.github.io/blog/2016/11/12/the-simplest-classifier-histogram-intersection.html). This is a great method to use if you are using several masked images.
7373
- Perceptual Hash: An explanation on pHash comparison can be found [here](http://www.hackerfactor.com/blog/index.php?/archives/432-Looks-Like-It.html). It is highly recommended to NOT use pHash if you use masked images. It is very inaccurate.
7474

75-
### Full Content Rendering
76-
77-
- Certain windows (namely hardware accelerated ones) won't always render their content. To work around this, you can "Force Full Content Rendering". This option is not recommended unless you really need it. It will cause a 10-15x performance drop based on the size of the complete window that's being captured (not the selected region, but rather the actual window size). It can also mess with some applications' rendering pipeline.
75+
### Capture Method
76+
77+
- **BitBlt** (fastest, least compatible)
78+
A good default fast option. But it cannot properly record OpenGL, Hardware Accelerated or Exclusive Fullscreen windows.
79+
The smaller the selected region, the more efficient it is.
80+
- **Windows Graphics Capture** (fast, most compatible, capped at 60fps)
81+
Only available in Windows 10.0.17134 and up.
82+
Due to current technical limitations, it requires having at least one audio or video Capture Device connected and enabled. Even if it won't be used.
83+
Allows recording UWP apps, Hardware Accelerated and Exclusive Fullscreen windows.
84+
Adds a yellow border on Windows 10 (not on Windows 11).
85+
Caps at around 60 FPS.
86+
- **Direct3D Desktop Duplication** (slower, bound to display)
87+
Duplicates the desktop using Direct3D.
88+
It can record OpenGL and Hardware Accelerated windows.
89+
About 10-15x slower than BitBlt. Not affected by window size.
90+
overlapping windows will show up and can't record across displays.
91+
- **Force Full Content Rendering** (very slow, can affect rendering pipeline)
92+
Uses BitBlt behind the scene, but passes a special flag to PrintWindow to force rendering the entire desktop.
93+
About 10-15x slower than BitBlt based on original window size and can mess up some applications' rendering pipelines.
94+
- **Video Capture Device**
95+
Uses a Video Capture Device, like a webcam, virtual cam, or capture card.
96+
There are currently performance issues, but it might be more convenient.
97+
If you want to use this with OBS' Virtual Camera, use the [Virtualcam plugin](https://obsproject.com/forum/resources/obs-virtualcam.949/) instead.
7898

7999
### Show Live Similarity
80100

‎res/design.ui

-5
Original file line numberDiff line numberDiff line change
@@ -1008,11 +1008,6 @@
10081008
<string>Check for Updates on Open</string>
10091009
</property>
10101010
</action>
1011-
<action name="actionLoop_Last_Split_Image_To_First_Image">
1012-
<property name="text">
1013-
<string>Force Full Render</string>
1014-
</property>
1015-
</action>
10161011
<action name="actionAuto_Start_On_Reset">
10171012
<property name="text">
10181013
<string>Check For Updates On Open</string>

‎res/settings.ui

+73-39
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@
77
<x>0</x>
88
<y>0</y>
99
<width>289</width>
10-
<height>540</height>
10+
<height>621</height>
1111
</rect>
1212
</property>
1313
<property name="sizePolicy">
@@ -19,13 +19,13 @@
1919
<property name="minimumSize">
2020
<size>
2121
<width>289</width>
22-
<height>540</height>
22+
<height>621</height>
2323
</size>
2424
</property>
2525
<property name="maximumSize">
2626
<size>
2727
<width>289</width>
28-
<height>540</height>
28+
<height>621</height>
2929
</size>
3030
</property>
3131
<property name="cursor">
@@ -46,40 +46,12 @@
4646
<x>10</x>
4747
<y>180</y>
4848
<width>271</width>
49-
<height>101</height>
49+
<height>181</height>
5050
</rect>
5151
</property>
5252
<property name="title">
5353
<string>Capture Settings</string>
5454
</property>
55-
<widget class="QCheckBox" name="force_print_window_checkbox">
56-
<property name="enabled">
57-
<bool>true</bool>
58-
</property>
59-
<property name="geometry">
60-
<rect>
61-
<x>6</x>
62-
<y>73</y>
63-
<width>204</width>
64-
<height>20</height>
65-
</rect>
66-
</property>
67-
<property name="toolTip">
68-
<string>Force a full render of the capture window, which is required for some applications to be captured</string>
69-
</property>
70-
<property name="whatsThis">
71-
<string/>
72-
</property>
73-
<property name="text">
74-
<string>Force Full Render (slower Max FPS)</string>
75-
</property>
76-
<property name="checked">
77-
<bool>false</bool>
78-
</property>
79-
<property name="tristate">
80-
<bool>false</bool>
81-
</property>
82-
</widget>
8355
<widget class="QSpinBox" name="fps_limit_spinbox">
8456
<property name="geometry">
8557
<rect>
@@ -143,12 +115,64 @@
143115
<bool>false</bool>
144116
</property>
145117
</widget>
118+
<widget class="QComboBox" name="capture_method_combobox">
119+
<property name="geometry">
120+
<rect>
121+
<x>6</x>
122+
<y>97</y>
123+
<width>251</width>
124+
<height>22</height>
125+
</rect>
126+
</property>
127+
</widget>
128+
<widget class="QLabel" name="capture_method_label">
129+
<property name="geometry">
130+
<rect>
131+
<x>6</x>
132+
<y>75</y>
133+
<width>151</width>
134+
<height>16</height>
135+
</rect>
136+
</property>
137+
<property name="text">
138+
<string>Capture method:</string>
139+
</property>
140+
</widget>
141+
<widget class="QLabel" name="capture_device_label">
142+
<property name="geometry">
143+
<rect>
144+
<x>6</x>
145+
<y>126</y>
146+
<width>151</width>
147+
<height>16</height>
148+
</rect>
149+
</property>
150+
<property name="text">
151+
<string>Capture device:</string>
152+
</property>
153+
</widget>
154+
<widget class="QComboBox" name="capture_device_combobox">
155+
<property name="enabled">
156+
<bool>false</bool>
157+
</property>
158+
<property name="geometry">
159+
<rect>
160+
<x>6</x>
161+
<y>148</y>
162+
<width>251</width>
163+
<height>22</height>
164+
</rect>
165+
</property>
166+
<property name="placeholderText">
167+
<string>Scanning for existing devices...</string>
168+
</property>
169+
</widget>
146170
</widget>
147171
<widget class="QGroupBox" name="image_settings_groupbox">
148172
<property name="geometry">
149173
<rect>
150174
<x>10</x>
151-
<y>290</y>
175+
<y>370</y>
152176
<width>271</width>
153177
<height>241</height>
154178
</rect>
@@ -175,10 +199,21 @@
175199
</rect>
176200
</property>
177201
<property name="toolTip">
178-
<string/>
179-
</property>
180-
<property name="whatsThis">
181-
<string notr="true"/>
202+
<string>L2 Norm:
203+
This method should be fine to use for most cases.
204+
It finds the difference between each pixel, squares it, sums it over the entire image and takes the square root.
205+
This is very fast but is a problem if your image is high frequency.
206+
Any translational movement or rotation can cause similarity to be very different.
207+
208+
Histograms:
209+
An explanation on Histograms comparison can be found here
210+
https://mpatacchiola.github.io/blog/2016/11/12/the-simplest-classifier-histogram-intersection.html
211+
This is a great method to use if you are using several masked images.
212+
213+
Perceptual Hash:
214+
An explanation on pHash comparison can be found here
215+
http://www.hackerfactor.com/blog/index.php?/archives/432-Looks-Like-It.html
216+
It is highly recommended to NOT use pHash if you use masked images. It is very inaccurate.</string>
182217
</property>
183218
<item>
184219
<property name="text">
@@ -192,7 +227,7 @@
192227
</item>
193228
<item>
194229
<property name="text">
195-
<string>Perceptual Hash</string>
230+
<string>pHash</string>
196231
</property>
197232
</item>
198233
</widget>
@@ -646,7 +681,6 @@
646681
<tabstop>loop_splits_checkbox</tabstop>
647682
<tabstop>fps_limit_spinbox</tabstop>
648683
<tabstop>live_capture_region_checkbox</tabstop>
649-
<tabstop>force_print_window_checkbox</tabstop>
650684
</tabstops>
651685
<resources/>
652686
<connections/>

0 commit comments

Comments
 (0)