Hello, I am making use of OBS Studio 30.1.2 capturing from an external source using an AJA capture PCIe card using the NTV2 drivers 17.0.1.23 on Windows 10 x64.
Recently I noticed an issue where the capture thread seems to stop, possibly because of a signal glitch in the source video feed. When this happens, black video appears in the capture frame until I manually intervene.
Based on the logs below, my feeling is that the AJA plugin may not be able to recover the capturing thread if the glitch is not resolved before the timeout is reached. Prior to the glitch being resolved, "Unknown" is returned when querying the driver for the video format, and I think this makes the AJA plugin just give up it's attempts at restarting the capture thread.
Here are the messages generated in the logfile when this occurs.
When this happens, I can open the source properties dialog and toggle the input dropdown selection, causing OBS to try the capture thread again which fixes the black video in the capture frame. These are the log messages generated when I do this...
I was wondering what thoughts people had regarding this issue. Would it make sense to request a change to the AJA plugin such that it will continually retry the capturing thread so that it will eventually resume displaying whenever the glitch in the source video feed has resolved?
Recently I noticed an issue where the capture thread seems to stop, possibly because of a signal glitch in the source video feed. When this happens, black video appears in the capture frame until I manually intervene.
Based on the logs below, my feeling is that the AJA plugin may not be able to recover the capturing thread if the glitch is not resolved before the timeout is reached. Prior to the glitch being resolved, "Unknown" is returned when querying the driver for the video format, and I think this makes the AJA plugin just give up it's attempts at restarting the capture thread.
Here are the messages generated in the logfile when this occurs.
Code:
04:13:51.368: AJASource::CaptureThread: New Video Format detected! Triggering 'aja_source_update' callback and returning...
04:13:51.369: AJASource::CaptureThread: Current Video Format: 720p59.94, | Want Video Format: 2Kp23.98
04:13:51.618: AJASource::Capturethread: Thread loop stopped
04:13:51.625: AJASource::ReadWireFormats - Detected pixel format YUV-8
04:13:51.626: AJASource::ReadWireFormats - Detected video format Unknown
04:13:51.626: aja_source_update: Unknown video/pixel format(s): Unknown / NTV2_FBF_8BIT_YCBCRWhen this happens, I can open the source properties dialog and toggle the input dropdown selection, causing OBS to try the capture thread again which fixes the black video in the capture frame. These are the log messages generated when I do this...
Code:
13:28:29.202: AJASource::ReadWireFormats - Detected pixel format YUV-8
13:28:29.202: AJASource::ReadWireFormats - Detected video format 720p59.94
13:28:29.203: AJASource::CaptureThread: Started!
13:28:29.203: AJASource::CaptureThread: Starting capture thread for AJA source SDI Input 3
13:28:29.205: AJASource::ResetVideoBuffer: Video Format: 720p59.94 | Pixel Format: YUV-8 | Buffer Size: 1843200I was wondering what thoughts people had regarding this issue. Would it make sense to request a change to the AJA plugin such that it will continually retry the capturing thread so that it will eventually resume displaying whenever the glitch in the source video feed has resolved?