AV:Datapath Vision Lossless Captures
This page will show you how to configure your Datapath's Vision software to get near-perfect captures, directly from your console's output with no scaler. You can also use the Vision as an "HDMI" capture card, with simply an HDMI to DVI adapter. It won't accept audio though, so you'll need an audio extractor for HDMI sources.
**Required Hardware:**
- Datapath Vision** E1, E1S or E2s Capture cards: https://ebay.us/7AD9jb
For HDMI, you'll also need:
- HDMI Audio Extractor**: https://www.retrorgb.com/hdmi-2-0b-1x2-splitter-audio-extractor.html
- 3FT HDMI to DVI Cable**: https://amzn.to/3eVSwLI
A note about "E" vs "Es": The main difference is the non-s models might have issues capturing 1080p60 with both the Vision window and OBS (or capture software) window open at the same time, due to the 480MB/s bandwidth (as opposed to the E1s' 650MB/s). It would definitely have issues if you somehow had three windows accessing it as well. There shouldn't be issues below 1080p60 and this isn't a likely scenario; You only need to keep the Vision open to retain analog video capture settings. HDMI/Digital inputs can just be accessed through your capture software.
You can do some back of the envelope calculations to confirm exactly what it can handle:
width x height x bits per pixel x fps / 8 / 1024 / 1024 The result of that calculation needs to be below 480MB/s For NV12, bpp is 12, for YUY2, bpp is 16, for RGB24, bpp is 24, and for RGB32/XRGB, bpp is 32.
Also, older VGA versions of the Datapath cards _may_ work with these same instructions below, but your results may vary
The digital receiver in the VisionRGB cards are extremely sensitive to bad cables, cheap adapters, and long cable runs. This often results in pink or green "speckles" across the screen in higher resolutions. If you're using your Vision for HDMI capture, I _strongly_ recommend running the signal through an HDMI splitter or audio extractor to "normalize" the signal. The ones linked above do _not_ affect picture quality, or colorspace.
**Required Software:**
**Prepping for Capture**
- Digital Capture:** If you're capturing from an HDMI or DVI source, there's not much that needs to be done. As stated above, I strongly recommend sending an HDMI signal through an audio extractor, both to allow access to the audio and to normalize the signal. The only other setting you might ever need to change is the color domain, between RGB and YUV in the Window\\Input Settings tab (screenshots below). You'll definitely know right away if it's set wrong, as the colors will look _very_ off. That's pretty much all you'll need to know for digital capture though! If you're not using it to capture analog signals, you can close this page...you're pretty much done! The only other thing to note, is the same tab you'll find the color setting will also list the detected resolution, which can come in handy.
- Analog Capture:**
Before even opening the capture software, you'll need to start by determining the _exact_ resolution of the game you're trying to capture. Some consoles like the Genesis will be easy, as all games output at 320x256, except the ones on this list FirebrandX created. Other console resolutions might be harder to find, so sometimes I end up loading an emulator, setting the video to 1:1 and taking a screenshot. Then I just reference that resolution. In this example, I'll use a Genesis game that always runs at 320x256, just to keep it easier. You'll sometimes run into games that switch between 240p and 480i, as well as games with multiple modes! I'll try and do an advanced version of this guide for those scenarios, but for now, let's stick to the basics.
**Configuring Vision**
Now that you know the resolution, load up the Vision software and get ready for one of the weirdest bugs I've ever seen in software (I'll get to that in a bit).
\- Power on your console and load the game you're looking to capture.
\- Load the Vision software and go to Window \\ Input Settings
\- Hit the "reset" button and note the resolution. Make SURE you've loaded the game and are in a main gameplay section before doing this, as many games use different resolutions for title screens or menu's! Note the width and height listed - They will be different from the game resolution, but are important.
\- The color adjustments need to be set to YUV for component and I normally leave it on Auto for RGB.
[[[File:DatapathVisionInput1.png)](https://cdn.retrorgb.com/wp-content/uploads/2019/02/DatapathVisionInput1.png]]
\- Switch to the "Window" tab.
[[[File:DatapathVisionWindow1.png)](https://cdn.retrorgb.com/wp-content/uploads/2019/02/DatapathVisionWindow1.png]]
\- Set the resolution to match _exactly_ what was listed in the Input tab. - Check off "Exclude Borders" - Set capture format to 8-8-8 - I leave scaling at "fast". I don't think it matters for what we're doing (1:1 configuration). - Hit Apply
\- Go back to the Input tab
Now we need to determine the Horizontal Size. The easiest way to do this is by checking the R3 wiki to see if someone has already calculated this: http://r3.fyi/ For Sega Genesis 320, it's already been determined that the exact hsize required is 427.50. Unfortunately, the Vision software has to round up to single numbers, sometimes making perfect configuration impossible. For Genesis, I usually use 427, but you can try 428 if you have issues.
If there isn't already a determined hsize, you can try to find another game with the same horizontal resolution (samples). For example a SNES game running at 256x240 will have an hsize of 341. That means (in the context of this guide) any other 256 game should have an hsize of 341.
If all else fails, you can try eyeballing it. As long as you've followed the steps above (reset and set the window size properly), you can attempt to change the hsize and Horizontal Position until the game _just_ fits the window. I've tried this a few times and it was hit-or-miss. Once, I guessed the exact size and it was perfect, but most of the time it's slightly off. After you've gotten the hsize...
\- Enter the hsize determined; 427 for this game - Move the Horizontal Position slider until the game perfectly fills the window. 85 was right for me, but it might be slightly different.
\- Set the Vertical Position to wherever it looks good. I usually leave it on 11 or 12 - You can crop if you'd like, but I do all of that in other software. - I don't touch any of the other settings.
[[[File:DatapathVisionInput2.png)](https://cdn.retrorgb.com/wp-content/uploads/2019/02/DatapathVisionInput2.png]]
Now we have to determine phase. This will be different pretty much _every_ time. Different consoles, different filter settings, toggling the sync stripper...pretty much _everything_ effects phase and you should count on tweaking it each time you're ready to capture. By far the easiest way to dial in phase is by loading up a checkerboard pattern. You can then just move the phase slider until there's no noise on the screen. Sometimes there's no perfect position though and I assume that has to do with the Datapath card only adjusting one number at a time. In those cases, just try to get it as good as possible.
[[[File:DatapathVisionPhase.png)](https://cdn.retrorgb.com/wp-content/uploads/2019/02/DatapathVisionPhase.png]]
If you don't have the ability to load a checkerboard pattern, try to find a screen with lines on it and see if you can dial it in that way. One trick I use is the Windows magnifier. Load it up, but make _sure_ you uncheck "smooth edges", or the image won't look right! Also, I suggest the "docked" view, to make things easier to manage. [[[File:WindowsMagnifier-300x149.png)](https://cdn.retrorgb.com/wp-content/uploads/2019/02/WindowsMagnifier.png]]
Now hover your mouse over the Vision window with the magnifier loaded and dial in the phase until there's no noise on the screen.
[[File:DatapathManualPhase.png) [images/DatapathManualPhase2.png ![]](https://cdn.retrorgb.com/wp-content/uploads/2019/02/DatapathManualPhase2.png]]
Everything else is easy compared to phase. I know this seems like a lot so far, but once you've gotten used to it, dialing in the settings takes seconds. Phase is always a pain.
Now, as promised, here's one of the weirdest bugs I've ever seen in software. In order to save these settings, you first need to hit _cancel_, then "no". Seriously. Here's screenshots:
First hit the cancel button: [[[File:DatapathInputCancel.png)](https://cdn.retrorgb.com/wp-content/uploads/2019/02/DatapathInputCancel.png]]
Now, hit "no", you don't want to "undo" the changes. [[[File:DatapathVisionNo.png)](https://cdn.retrorgb.com/wp-content/uploads/2019/02/DatapathVisionNo.png]]
Messed up right? If you had hit "apply" or "cancel" instead, all of your settings would have changed and you'd have to re-set everything.
To make matters worse, I've saved these settings to a file through the Vision window, just to have that file save on it's own with different settings at some point. It's my strong suggestion that you just reference the R3 wiki for hsize and hposition, tweak hposition as needed and dial in phase.
Now, make sure to leave this window open!!! Even when you open other software to access it, the configured window _must_ stay open!!!
I promise after doing this a few times, it'll seem much easier!!! Honestly, once you've determined the settings, it's just a matter of tweaking phase each time.
Click here to go to the next section: Scaling Your Video Captures, or click here to go to the main capture page.