When your capture results look offset from what you expected given your Omnivore Overlay placement, here is how you can quickly trouble shoot this issue.
Why does this happen ?
There are two main reasons. Your computer Display DPI Scaling Setting is not set to 100%, but instead its set to something like 125%. Or, the player you are using is causing problems because of its settings, display mode or maybe just how it was written where its overriding your Windows Display Settings. Some players are peskier than others.
Which is the quickest way to determine which it is ? That is in part up to you.
- You can check and adjust your DPI settings and do another test capture.
- Do a test capture on a know piece of video with a known player.
Option 1 – Adjust DPI Settings to 100%
If the computer display is not set to 100% DPI, there is not a 1:1 relationship between what Omnivore is capturing and what you are seeing via placement of the Omnivore Overlay.
In Window 7 this is easy to fix. Right click desktop > Select Personalize > Display
If yours is set to 125%, change it to 100% and do a test capture while in Image Capture mode.
If you get the results you expected, problem solved.
In Window 10, this can be more tricky. In some versions of Windows 10, they have removed access to the DPI setting, so you have to do a regedit to modify it. Always back up your registry first.
But before you do that, I would do Option #2
Omnivore comes with a 2 test capture videos located on the main Omnivore partition under Omnivore > Help > Videos
Open one of these 2 videos and do a test image capture then view the results.
If the results of this test show your Omnivore Capture isn’t offset, then your computer display settings shouldn’t be the issue. Instead, you just have one of those pesky players that is doing something funky.
Determining how to get your Pesky Player to allow you to Capture WYSIWYG or at a 1:1 Scale.
Since every player is different, its going to take pocking around and trying a few things.
1) Check the players settings for scaling options
2) Try different display modes. Quad, Full Screen etc. I have seen one mode work and not another from the same player, without changing settings.
3) Try launching a second copy of the player and test capture from that 2nd player. Often, the first instance of the player will use GPU/VRAM resources, and the second will use CPU/RAM.
« Back to the Knowledgebase