Ok so I'm going to summarize a bit here from my own and shared experiences with these cards.
#1
First let's kill this idea, not enough power. I've had the card run for hours on end, even forgot i left the cam on over night after stream and it was still capturing just fine. This with usb 3 power charge etc disabled in bios.
- In addition Enabling usb 3 power in bios doesnt fix anything either.
- This doesnt mean the card should run with other devices on same hub, but not for not enough power as reason.
- Also see #4.
#2 Running the card *along* with separate, usb hub with it's own dedicated power supply in a usb port next to the capture card, not good enough. Capture card transmission will be disrupted
#3 Must be usb 3.0 - The card can work just fine usb 3.1 and rightly so as it provides twice the bandwidth. But even so, usb 3.0 alone is capable of 100+ mb so for our purposes, it's not an issue with bandwidth over usb 3.
- Avermedia's own tool (usb 3.0 diagnosis tool) detects my usb 3.1 as not supported, yet funnily enough it says 3.0 ports, from same chipset mind you, is supported.
- So much for updated software support.
#4 Drivers. All of the drivers are basically beta.
- in addition also adding windows service to supposedly check which usb port the card is connected to, for god know's what purpose. It's pulling some cpu, albeit minor, it seems to be quite useless, and doesnt help with any issues, more over it seems to halt obs from initializing the card correctly many times. At least for me who have 2 of these cards, i prefer to just disable/delete the service.
#5 Windows as platform. In the latest anniversary update they added some horrible stuff that adds fps problems that can be fixed by doing a registry tweak and basically disabling/removing the xbox app thru powershell. I already run a removal script on pc startup but initially this just added fuel to the fire as monitors here was turning them self off on seemingly random.
- There could be a things to tweak in windows registry to help the capture card stability to avoid problems with alt-tabbing etc.
-Tweaking about with usb3.0 power registry tweaking doesn't help. CC will still halt at random alt-tabs, not all tho.
#6 On a obs freezed frame, because that's what it is, when typically have just alt-tabbed to something, or it just "happened on it's own", unless other stuff is causing a problem such as the latest w10 update, i can still get response from the capture card when moving cursor on to it's 'screen' and going about business there.
- It's typically just that, obs froze on the frame as a window change occured.
- It's not a matter of latency. 1-4ns response from my game pc when idle[overclocked], is as close to perfect as it gets.
- I've seen other people with absolutely crazy pc builds, still has issues with other capture cards in obs, even much more expensive ones.
tldr: avermedia needs to get their shit together, OBS is wonderful and every update to it makes me happy.