Question / Help Avermedia capture card audio issues

Arenn

New Member
I had to spend a few hours tweaking audio settings to set this thing up initially, and basically ended up with a triple-redundant audio capture setup to push the game audio out to stream it properly. This setup worked for about the last month, and now suddenly I boot it up today and nobody can hear the game audio. The triple-redundancy means I can hear the game audio in my TV and my headset, so I know my computer is getting it and it's getting through most of my audio captures to be heard by me, so I cannot for the life of me figure out what could have changed or broken in OBS. I attached the first few logs from today because I restarted OBS multiple times trying to get it to work and I'm unsure which one might contain helpful information.
 

Attachments

  • 2020-02-19 15-05-26.txt
    11.6 KB · Views: 22
  • 2020-02-19 15-09-29.txt
    13.1 KB · Views: 17
  • 2020-02-19 15-15-13.txt
    15.8 KB · Views: 15

Narcogen

Active Member
All logs show the same:

15:09:30.558: [WASAPISource::WASAPISource] Device '{0.0.0.00000000}.{1ee1cf06-bc4e-4a10-af4f-6fc36b6f96c4}' not found. Waiting for device
15:09:30.580: WASAPI: Device 'Microphone (Yeti Stereo Microphone)' initialized
15:09:30.581: [WASAPISource::TryInitialize]:[Microphone (Realtek High Definition Audio)] Failed to activate client context: 88890004
15:09:30.581: [WASAPISource::WASAPISource] Device '{0.0.1.00000000}.{26d451a5-2832-4ec7-b2de-b052315ca2b2}' not found. Waiting for device


OBS is asking for access to your audio device and is unable to get it. It could be this device doesn't exist, isn't connected, or has exclusivity on and another application is using it. The line for your Yeti indicates it is working, but there is no successful initialization message for the other source. The lack of a name there may indicate OBS is trying to connect to a device that no longer exists. System default devices have been known to change across reboots or Windows updates.
 
Top