No encoder options except x264 when I attach video capture cards

TCPippin

New Member
System: win 10
Video card: RTX 4060, with fresh drivers (clean install)

If I have no video capture cards in my PC, OBS offers me full spectrum of options - x264, HEVC, H.264.
But if I add Avermedia GC570D (PCI-mounted) or GC553 (USB 3.0), the only encoder on the list is x264.

I thought I had a hardware problem. Luckily, I have access to another win10 PC, with RTX 3070, so I ran a couple experiments there.
- First, I installed OBS on the loaner-PC both and put both my video capture cards there. OBS was working as intended.
- Then, I replaced RTX 3070 with my 4060. OBS was still working fine.
- Then, I put in my SSD and booted my own system on the loaner-PC. OBS gave no options but x264
- Finally, I put back 3070 instead of 4060 into loaner-PC. Still no options but x264

As far as I can see, that rules out any possible hardware problem, so it must be a software issue.
I've tried a clean install of OBS (including plugins), of Nvidia drivers, of Nvidia broadcast. I also tried "optimizing" OBS via Nvidia app - after it was done, it briefly showed "h.264" on the list, but after reboot it disappeared again.
I wish I had a recovery point before the problem started (I've been using this setup for my streams for years, and it only cropped up recently), but I don't have one.

Thoughts?
 
Sounds like it might be a configuration issue. Loaner worked fine until you stuck your OS drive in it.

Then, I put in my SSD and booted my own system on the loaner-PC. OBS gave no options but x264
- Finally, I put back 3070 instead of 4060 into loaner-PC. Still no options but x264
 
System: win 10
Video card: RTX 4060, with fresh drivers (clean install)

If I have no video capture cards in my PC, OBS offers me full spectrum of options - x264, HEVC, H.264.
But if I add Avermedia GC570D (PCI-mounted) or GC553 (USB 3.0), the only encoder on the list is x264.

I thought I had a hardware problem. Luckily, I have access to another win10 PC, with RTX 3070, so I ran a couple experiments there.
- First, I installed OBS on the loaner-PC both and put both my video capture cards there. OBS was working as intended.
- Then, I replaced RTX 3070 with my 4060. OBS was still working fine.
- Then, I put in my SSD and booted my own system on the loaner-PC. OBS gave no options but x264
- Finally, I put back 3070 instead of 4060 into loaner-PC. Still no options but x264

As far as I can see, that rules out any possible hardware problem, so it must be a software issue.
I've tried a clean install of OBS (including plugins), of Nvidia drivers, of Nvidia broadcast. I also tried "optimizing" OBS via Nvidia app - after it was done, it briefly showed "h.264" on the list, but after reboot it disappeared again.
I wish I had a recovery point before the problem started (I've been using this setup for my streams for years, and it only cropped up recently), but I don't have one.

Thoughts?

Good troubleshooting but you've reached an incorrect conclusion. To me it seems like you are probably not giving your GPU all the PCI-e lanes it needs to function properly, these are shared by other devices like video internal capture cards and SSDs.
 
Good troubleshooting but you've reached an incorrect conclusion. To me it seems like you are probably not giving your GPU all the PCI-e lanes it needs to function properly, these are shared by other devices like video internal capture cards and SSDs.
On the loaner PC, I've tried a very BUS-intensive setup: GC570D on PCI, and on USB I've had 3 GC553's and a 4K webcam.
When I was booting from loaner's M2, everything worked fine with either graphics card.
Booting loaner from my SATA SSD, I've encountered my issue yet again. Even stripping down to single GC570D or GC553 didn't help.

So I don't think it's a motherboard issue either.

Sounds like it might be a configuration issue. Loaner worked fine until you stuck your OS drive in it.

Yeah, but I'm out of ideas what to try except a full OS reinstall.
 
In case you don't see this thread. It's the first report I've seen of possible driver issues. I'm still running 566.36 (flawless) so it might be worth looking into further.

 
Back
Top