We are running 3 Vaddio RoboSHOT 30E NDI PTZ cameras using a Birddog PTZ Keyboard controller streaming through OBS to Facebook and YouTube (using the sorayuki multioutput plugin). We also are using Birddog multiviewer and NDI Tools Monitor to be able to view all 3 cameras at once. When we stream we automatically record as well.
We are experiencing an issue where the OBS (version 27.2.3 - 64 bit) display goes black as if the application has crashed but it is still running in the background. If we are streaming we see that streaming has been interrupted but the recording process is still running (although it is stuck on the view that was active when we lost the display). There is no crash log generated and in the normal run log we see over 2,800 lines of 'WASAPI: Device '{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}' failed to start'. In the startup section this device identification seems to be tied to global audio devices 'Desktop Audio' and 'Desktop Audio2'; both of which seem to have issues starting:
-----
08:35:59.436: ------------------------------------------------
08:35:59.489: All scene data cleared
08:35:59.489: ------------------------------------------------
08:35:59.497: [win-wasapi: 'Desktop Audio'] update settings:
08:35:59.497: device id: {0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}
08:35:59.497: use device timing: 1
08:35:59.504: [WASAPISource::TryInitialize]:[{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}] Failed to enumerate device: 80070490
08:35:59.504: WASAPI: Device '{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}' failed to start
08:35:59.553: [Loaded global audio device]: 'Desktop Audio'
08:35:59.553: - monitoring: monitor and output
08:35:59.553: [win-wasapi: 'Desktop Audio 2'] update settings:
08:35:59.553: device id: {0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}
08:35:59.553: use device timing: 1
08:35:59.553: [WASAPISource::TryInitialize]:[{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}] Failed to enumerate device: 80070490
08:35:59.553: WASAPI: Device '{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}' failed to start
08:35:59.565: [Loaded global audio device]: 'Desktop Audio 2'
08:35:59.565: - monitoring: monitor and output
-----
Our audio input is coming from a mixer into the USB port of the computer. The same mixer is defined in Widows setting as our desktop audio input device as the computer does not have an onboard microphone.
We have attempted to stream without using the Birddog and NDI tools monitors and still had the same experience. We don't see any pattern to actions taken when this occurs and we have experienced this behavior just once in a nearly 2 hour stream and also seven times in a stream lasting less than an hour. We have also noted this behavior when just setting up our production (scene editting, etc) before we even begin to stream.
We are looking for guidance in what we can do to stop OBS from behaving like this so we can present an uninterrupted production. We appreciate any help that can be provided.
We are experiencing an issue where the OBS (version 27.2.3 - 64 bit) display goes black as if the application has crashed but it is still running in the background. If we are streaming we see that streaming has been interrupted but the recording process is still running (although it is stuck on the view that was active when we lost the display). There is no crash log generated and in the normal run log we see over 2,800 lines of 'WASAPI: Device '{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}' failed to start'. In the startup section this device identification seems to be tied to global audio devices 'Desktop Audio' and 'Desktop Audio2'; both of which seem to have issues starting:
-----
08:35:59.436: ------------------------------------------------
08:35:59.489: All scene data cleared
08:35:59.489: ------------------------------------------------
08:35:59.497: [win-wasapi: 'Desktop Audio'] update settings:
08:35:59.497: device id: {0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}
08:35:59.497: use device timing: 1
08:35:59.504: [WASAPISource::TryInitialize]:[{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}] Failed to enumerate device: 80070490
08:35:59.504: WASAPI: Device '{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}' failed to start
08:35:59.553: [Loaded global audio device]: 'Desktop Audio'
08:35:59.553: - monitoring: monitor and output
08:35:59.553: [win-wasapi: 'Desktop Audio 2'] update settings:
08:35:59.553: device id: {0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}
08:35:59.553: use device timing: 1
08:35:59.553: [WASAPISource::TryInitialize]:[{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}] Failed to enumerate device: 80070490
08:35:59.553: WASAPI: Device '{0.0.0.00000000}.{c3ab3aed-26fe-48db-a7a7-1d486a53a409}' failed to start
08:35:59.565: [Loaded global audio device]: 'Desktop Audio 2'
08:35:59.565: - monitoring: monitor and output
-----
Our audio input is coming from a mixer into the USB port of the computer. The same mixer is defined in Widows setting as our desktop audio input device as the computer does not have an onboard microphone.
We have attempted to stream without using the Birddog and NDI tools monitors and still had the same experience. We don't see any pattern to actions taken when this occurs and we have experienced this behavior just once in a nearly 2 hour stream and also seven times in a stream lasting less than an hour. We have also noted this behavior when just setting up our production (scene editting, etc) before we even begin to stream.
We are looking for guidance in what we can do to stop OBS from behaving like this so we can present an uninterrupted production. We appreciate any help that can be provided.
