Question / Help How does OBS Studio 64bit Capture from the Live Gamer Portable?

[TimeSlot]

So I'm an idiot and have been using the LGP completely wrong this whole time. I thought I could feed a 1080p signal and receive a 720p 60FPS signal through downscaling, but it appears that you only get true 60fps from having a 720p Source. Which lead me to realize that OBS 64bit LGP (C875) Native Support automatically sets the FPS to 60 when it is fed a 720p Signal (Originally I thought it was 1080p 30fps or nothing through HDMI).

How does OBS 64bit receive the capture from the C875?

When AMD updated their drivers to ReLive it caused the HDMI HDCP to be constantly active, which makes it so I can't capture unless I roll back to 16.9.2, and RECentral can be patched to allow an HDCP signal. You can capture the RECentral preview window with OBS and get around this, however, the quality is crap and is much more delayed. I'd rather not have to get an HDMI splitter to remove HDCP just so I can update my GPU's drivers.

 

[Adrian Schofield]

OBS uses the vendors drivers to interface with the capture hardware.

I'm not sure what you mean about HDCP, if you are capturing a console then you can usually switch off HDCP for gaming content. If you are trying to record HDCP protected footage then you are asking for help in the wrong place.

 

[TimeSlot]

Yea I suppose this is the wrong place, not because I'm trying to capture HDCP protected footage but rather HDCP is being forced on at all times through my Video Card and so the LGP wont display it unless bypassed, much like the PS3, which the LGP comes with a bypass in the form of a Component Adapter.

The reason I believe it is an HDCP issue is that by using the (unofficial) patched version of RECentral that bypasses HDCP, I get a signal, just like I do with my PS3. I'm not trying to record movies or anything, I am however trying to Bypass the HDCP protection that has recently been forced on with the newer AMD graphics card drivers ( At least that's the case with my RX 480) and rolling back to the Sep 2016 drivers fixes this issue.

Thanks anyways.