Shinblindrezo
Member
Oh yeah, and if you find that only 1 of your 2 CPUs are ever being used during a broadcast, you'll have to disable NUMA in the BIOS.
[unsupported] Datapath Vision Capture
- Thread starter Muf
- Start date
Thanks very much, pretty comfortable with 8.1, so will give it a shot with OBS Studio. Streaming from the PC with 2 monitor setup - sounds like I need to clone the gaming monitor to the DVI output of the 970 connected to the Datapath card.
We have limited technical skills so simpler the better for us.
Shinblindrezo
Member
You might want to look into investing on a small HDMI splitter. I use a cheapo that I bought years ago for about 20 euros. Works perfectly. That way you don't get any screen tear that you would get on a dual monitor setup.
(PC HDMI output) <- HDMI cable -> (Splitter input)
<- "HDMI to DVI" cable -> (Datapath input)
(Splitter Output) <
<- HDMI cable -> (Monitor input)
You could also get a DVI splitter, but those are ridiculously expensive, for some reason.
Shinblindrezo
Member
MSPaint to the rescue!!
Thought about a splitter (which I've had in the past) but currently using the Displayport with G-sync from the 970 for the monitor. Any way to preserve the monitor output?
Boildown
Active Member
I simply clone my display instead of using a splitter. If you read the thread, I posted pretty much everything. Here's a good place to start, then read the next couple of pages: [unsupported] Datapath Vision Capture
The E1 says "DGC-139A" on the circuit board, according to the pdf datasheet. The E1S says "DGC-139C", as that's what's on mine.
I still do NVEnc for local recordings and simultaneously do x264 for streaming to Twitch on the dual xeon beastie. Still tweaking it, but not sure I'll ever get to Slower preset. It does Slow super easily, hardly any duplicated frames at all (less than 1/10th of 1%, probably all of which are generated at startup). Anyways, the NVEnc recordings just leave me that much more CPU for the x264 bit, and never crashing is an added benefit. I see no reason not to.
I don't think either monitor nor window capture performance applies when doing a capture card capture. Its a pear to your apples and oranges.
The E1 says "DGC-139A" on the circuit board, according to the pdf datasheet. The E1S says "DGC-139C", as that's what's on mine.
I still do NVEnc for local recordings and simultaneously do x264 for streaming to Twitch on the dual xeon beastie. Still tweaking it, but not sure I'll ever get to Slower preset. It does Slow super easily, hardly any duplicated frames at all (less than 1/10th of 1%, probably all of which are generated at startup). Anyways, the NVEnc recordings just leave me that much more CPU for the x264 bit, and never crashing is an added benefit. I see no reason not to.
I don't think either monitor nor window capture performance applies when doing a capture card capture. Its a pear to your apples and oranges.
Shinblindrezo
Member
Interesting, I always remembered cloning the display would induce tearing on one of the outputs. It's been a long time since I tried, though, so I guess things have changed. Isn't there a slight performance hit for being cloned, though? I should seriously test this out... Perhaps even do away with the splitter.
As for Display Port, I don't really have any experience with it. :(
As for Display Port, I don't really have any experience with it. :(
Last edited:
Thanks, I see the DGC-139C on my card. If the the MB arrives today will install with with 8.1. Thanks.
Boildown
Active Member
Classic. Don't think Studio has the Datapath plugin available so I haven't messed with it yet.
I think the tearing is created when you don't precisely match the cloned screens, including framerate. Lately I've been using the Custom Resolution Utility (CRU) to precisely match the Datapath's input to whatever I'm sending the monitor. Just setting the resolution and framerate usually leaves some minor differences. Haven't extensively tested it though.
Not sure about performance hit. If its there its minor. I actually assumed the splitter would introduce a frame or two of latency itself.
I think the tearing is created when you don't precisely match the cloned screens, including framerate. Lately I've been using the Custom Resolution Utility (CRU) to precisely match the Datapath's input to whatever I'm sending the monitor. Just setting the resolution and framerate usually leaves some minor differences. Haven't extensively tested it though.
Not sure about performance hit. If its there its minor. I actually assumed the splitter would introduce a frame or two of latency itself.
Boildown
Active Member
Not sure this is accurate anymore. This auction for an "E1": http://www.ebay.com/itm/Datapath-Vi...-Capture-Card-PCIe-PC-APPLE-NEW-/201548255770 has some nice images that clearly show the part being "DGC-139C". So that looks like it might not be a good indicator of which model it is. Or he's selling an E1S as an E1. But both the box and the manual clearly indicate E1 as well, so I doubt it.
Thanks
I don't think the serial # thing is accurate like Boildown said here is a E1S for 100$ but it's local pickup only. See the 139E on there? So is the serial a real reliable way to tell which one it is E1 or E1S? http://www.ebay.com/itm/Datapath-Vi...daa8caf&pid=100033&rk=2&rkt=4&sd=291655917770
Having Aero enabled in windowed mode does help with the tearing. I have a 2pc setup that suffered from the same issue of tearing in windowed mode, is my enough it was fixed by enabling aero. Something to do with dwm service having vsync and buffering built in to the aero theme.
Last edited:
Boildown
Active Member
Call Datapath? Otherwise I'd believe the drivers that its an E1.
On my E1S I would push it to about 115Hz, but past that, it wouldn't work. An E1 may or may not be even slower, depending on which bottleneck I was hitting. I doubt you could hit 144Hz. One of the major bottlenecks is that it only supports a single-link DVI link, and it may be the DVI signalling itself that is breaking down at that refresh rate.
Other people have had problems getting it to work with G-Sync. It would be interesting to hear if you got it to work or not. If I were you I'd see how far you can push it in normal mode before turning on G-Sync. Also, read my posts about my experience pushing my E1S to high refresh rates. If you have to cap your monitor at 100Hz instead of 144Hz, that's still pretty good IMO.
Boildown
Active Member
This is a lower level issue than that.
Are you currently using DVI-DL card Boildown ?
OK. Planning to set both the gaming monitor and cloned output to the E1S at 100 hz and see how the quality of the gaming monitor is affected by the reduction from 144 hz (which is pretty deluxe).
Plan to stream at 720p at 60 hz - just looking for a system to generate a reliable decent stream (like everyone else I guess).
The rest of the ECC RAM will be here the rest of the week