Capture Inputs Freeze

[pilzinho]

At a client of ours the inputs of the Decklink capture card occasionally freeze/the textures are not updated anymore. They have to restart the application to make it work again. We've never encountered this error anywhere else so far.

Setup:

• Unity version: 2022.2.5f1
• AVPro DeckLink version: 1.9.7
• Operating system version: Windows 10
• CPU: AMD Ryzen Threadripper PRO 5955WX 16-Cores
• GPU: NVIDIA RTX A4000, DirectX 11
• RAM: 48GB
• Hardware model: 2x DeckLink Quad HDMI Recorder
• Desktop Video version: 12.5.1
• One input is 3840x2160 (4K 60 10-bit 4:2:2 YUV) the other ones are 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)

Logs
The only suspicious lines in the logs which we haven't seen anywhere else before are these ones which show up regularly for different inputs:

[DEBUG] [UNITY] [AVProDeckLink] Changing device 'Videoserver 3' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)  
[ERROR] [UNITY] Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set
Stacktrace:
DeckLink.Update
Device.Update
FormatConverter.Update
FormatConverter.DoFormatConversion
ComputeShader.Dispatch
Application.CallLogCallback

Here's an excerpt from the Player.log file:

[AVProDeckLink] Changing device 'Videoserver 2' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 3' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 1' input 3840x2160 (4K 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 5' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 4' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set
[AVProDeckLink] Changing device 'Videoserver 2' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 1' input 3840x2160 (4K 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 3' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 5' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 4' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set
[AVProDeckLink] Changing device 'Videoserver 2' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 3' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 1' input 3840x2160 (4K 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set
[AVProDeckLink] Changing device 'Videoserver 5' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 4' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set
[AVProDeckLink] Changing device 'Videoserver 1' input 3840x2160 (4K 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 3' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 2' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 5' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 4' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set
[AVProDeckLink] Changing device 'Videoserver 1' input 3840x2160 (4K 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 2' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 5' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
[AVProDeckLink] Changing device 'Videoserver 4' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
[AVProDeckLink] Changing device 'Videoserver 3' input 1920x1080 (HD1080p 60 10-bit 4:2:2 YUV)
d3d11: Creating a default shader resource view with dxgi-fmt=0 for a texture that uses dxgi-fmt=24
Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set
Compute shader (AVProDeckLink_V210_to_RGBA(Clone)): Property (constBuffer) at kernel index (0) is not set

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.