Audio capture app

M

merlin6

New Member
I have a problem with the source "Audio capture app".
Recently, a few times my stream was interrupted and in the log I found this information:

[WASAPISource::ProcessCaptureData] window disappeared
Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' invalidated. Retrying (source: SnowRunner)
[game-capture: 'Save. games'] ----------------- d3d11 capture freed ----------------
[WASAPISource::TryInitialize]:[[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]] Failed to find window
 
T

TheHaricover

New Member
I got a similar issue :

Code: 
17:14:57.973: [WASAPISource::ProcessCaptureData] window disappeared
17:14:58.277: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' invalidated.  Retrying (source: GAMINGAudio)
17:15:01.278: [WASAPISource::TryInitialize]:[[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]] Failed to find window
17:15:15.002: [WASAPISource::ProcessCaptureData] window disappeared
17:15:15.003: Device '[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]' invalidated.  Retrying (source: Streamer.bot)
17:15:15.057: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:192.168.1.116]:56353` has disconnected with code `1000` and reason: Disconnecting
17:15:18.004: [WASAPISource::TryInitialize]:[[VIRTUAL_AUDIO_DEVICE_PROCESS_LOOPBACK]] Failed to find window

My preview freezes and the bitrate goes to 0 kbps but everything else (or so it seems) stays like it should be, green square, sound bars moving, etc.
Ofc the stream goes down and if I touch anything related to OBS, it enters a "doesn't respond" phase where everything stops working and I must force quit OBS. The soft still uses my GPU though.

It seems to be linked to a windows API used for capturing sound, probably in the "Application Audio Capture" (which is in beta I know).
 
T

TheHaricover

New Member
Well I was wrong.

Code: 
17:34:27.568: [game-capture: 'GAMING'] We're DXGI1.4 boys!
17:34:27.568: [game-capture: 'GAMING'] d3d12_init_11on12: creating 11 device: queue=0x1B7ADA360E0
17:34:27.584: [game-capture: 'GAMING'] d3d12 shared texture capture successful
17:34:27.584: [game-capture: 'GAMING'] Remembering D3D12 queue from present: queue=0x1B7ADA360E0
17:34:27.585: [game-capture: 'GAMING'] Remembering D3D12 queue from first direct submit after present: queue=0x1B7ADA38660
17:34:27.591: [game-capture: 'GAMING'] shared texture capture successful
17:36:28.747: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:127.0.0.1]:58218` has disconnected with code `1006` and reason: Une connexion existante a dû être fermée par l’hôte distant.
17:36:58.540: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:127.0.0.1]:58512
17:36:58.566: [obs-websocket] [WebSocketServer::onMessage] Client [::ffff:127.0.0.1]:58512 appears to be running a pre-5.0.0 protocol.
17:36:58.573: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:127.0.0.1]:58512` has disconnected with code `4010` and reason: You appear to be attempting to connect with the pre-5.0.0 plugin protocol. Check to make sure your client is updated.
17:36:58.607: [obs-websocket] [WebSocketServer::onOpen] New WebSocket client has connected from [::ffff:127.0.0.1]:58513
17:41:27.755: [obs-websocket] [WebSocketServer::onClose] WebSocket client `[::ffff:127.0.0.1]:58513` has disconnected with code `1006` and reason: Une connexion existante a dû être fermée par l’hôte distant.

So now it's the websocket ! Except it probably isn't. It seems like a coincidence, like the WASAPI before.

It seems OBS doesn't log anything about the freeze and the bitrate going to zero which I don't know if it's possible or not
 
T

TheHaricover

New Member
I tested a few things and it seems this issue comes from the GPU not being able to keep up. I don't really understand why OBS crashes though.
Either that or the NVIDIA AI filters have issues with OBS and makes it crash.

Without the nvidia background removal or the face tracker, OBS seems really fine
 
You must log in or register to reply here.
Top