Question / Help Capture Device worked perfectly earlier, but now OBS hates it?

[Otherbuttons]

Earlier today I had my freshly installed EZcap working fine on OBS Studio. It worked logically, I could change settings, it worked, it was all good, and I could stream my Wii.

And then I turned off OBS. When I came back to it 30 minutes later, it wouldn't for the life of it pick up the device. Nothing had been changed at all. I kept fiddling and resetting, but nothing is fixing it. If it even slightly worked, OBS would completely lose it if I changed any settings.

Example of it working, and what it's doing now.
Sometimes if I set it to 720x576 it does this (actually detects the thing), but that's not even the right resolution and changing it makes it go away again.

I've tried:
• Resetting my PC. It did nothing.
• Reinstalling the Drivers. This is the closer I've gotten, but when I tried to change any settings, OBS got rid of it.
• Every setting I can think of. Sometimes it would pick it up, then wouldn't, and when I went back it wouldn't again.
• New Scenes. Nothing.
• 32 Bit. Sometimes I'd get sound, but nothing else. This also happened randomly.

I should add, OBS does this a lot with my Webcam too. Luckily I found that unplugging and plugging in my cam fixes it.
I've tried this with the new device, to no avail. The EZcap seems to be working fine too, and with OBS' issues in the past I honestly think it's OBS.

Here's my log files.

Any help what-soever would be amazing, please. I can't for the life of me figure out what's going on.

 

[Fenrir]

From what I can tell, that error is pointing to driver failure for the device itself. The error you're getting is:

DShow: HDevice::ConnectPins: failed to connect pins (0x80070491): There was no match for the specified key in the index.

A quick search seems to indicate that this means the driver is operating outside the spec of what window DirectShow supports.

In short, capture cards that cheap are cheap for a reason. They barely function at best, have terrible drivers and even worse hardware. There is unfortunately not much we can do but suggest getting a decent capture card to replace it.

 

[Otherbuttons]

From what I can tell, that error is pointing to driver failure for the device itself. The error you're getting is:

DShow: HDevice::ConnectPins: failed to connect pins (0x80070491): There was no match for the specified key in the index.

A quick search seems to indicate that this means the driver is operating outside the spec of what window DirectShow supports.

In short, capture cards that cheap are cheap for a reason. They barely function at best, have terrible drivers and even worse hardware. There is unfortunately not much we can do but suggest getting a decent capture card to replace it.

Ah bugger. I'm so confused as to why it was working absolutely perfectly earlier? Nothing was wrong at all. And the card seemed to work. I might test it on xsplit or the laptop it used to work on tomorrow and see if it's the card or not.

I'd get a better card if I could afford one. This did me good for a while.

Thanks for the reply though, I appreciate it. <3

 

[sam686]

Sometimes if I set it to 720x576 it does this (actually detects the thing), but that's not even the right resolution and changing it makes it go away again.

1. Black capture... You might want to configure crossbar to make sure the correct input is selected (composite, s-video). For some capture device, crossbar settings might need to be set every time USB reconnects or computer restarts.
2. Configure Video, make sure the correct video standard is selected (NTSC_M for United States, North America), Using NTSC should allow 480p.

 

[Otherbuttons]

1. Black capture... You might want to configure crossbar to make sure the correct input is selected (composite, s-video). For some capture device, crossbar settings might need to be set every time USB reconnects or computer restarts.
2. Configure Video, make sure the correct video standard is selected (NTSC_M for United States, North America), Using NTSC should allow 480p.

Yeah, that's how I got it working in the beginning. But the Wii I'm using only goes that red in game. So it doesn't pick up the wii there, and one gets rid of it if I switch it to 480.

This is the problem: I know how to get it working. It worked. And then 30 minutes later OBS is bring so fragile about touching any settings.

Like I said, I'll check if it's the device or OBS when I get up though.