Update SDK14.4, Playback failed

Hello,
I have encountered a confusing issue. I have been using SDK (Ver: 12.8) to handle the SDI output of my videos, which worked smoothly on devices such as Duo and 8K Pro. Recently, after upgrading the SDK to the latest version 14.4, I encountered output problems. When using the DisplayVideoFrameSync method to display video content, the new SDK returns an error code 0x80000005. I tested several SDK versions: 14.0, 14.1, and 14.2 all functioned normally, but the error started occurring from version 14.3 onwards. I hope to upgrade to 14.4 to proceed with researching SMPTE 2110 and using 2110 IP Converters. Do you have any suggestions?

I have found that there are some differences in the usage of the new SDK. The new SDK has added the IDeckLinkVideoBuffer interface, and the submitted IDeckLinkVideoFrame needs to implement IID_IDeckLinkVideoBuffer, which should be the cause of the problem.
My usage scenario is as follows: receiving network video streams, decoding them using IntelMediaSDK, and outputting them to the SDI channel. To avoid multiple copies of YUV raw data, I encapsulated a custom IDeckLinkVideoFrame and modified the GetBytes interface, allowing the decoded data to be directly submitted to DeckLink. Now, if I still want to maintain this approach, does it mean that I must also implement IID_IDeckLinkVideoBuffer? Are there any demos available for reference in this regard?

I have identified another critical compatibility issue: the 14.4 SDK is no longer interoperable with legacy driver versions (e.g., 12.8). Notably, the 12.8 SDK previously demonstrated seamless compatibility with earlier drivers, which was a significant advantage for our deployment.
Our product delivers audio-video decoding and output services, providing only the software layer while customers handle installation of servers, DeckLink hardware, and drivers independently. Some legacy clients still rely on driver versions as old as 12.4 or earlier, and historical software upgrades have always maintained full compatibility.
However, the current scenario necessitates a more complex upgrade strategy—potentially requiring us to advise clients to update their drivers. Do you have any recommended approaches to mitigate this transition?
Detailed Error Log from DeviceList Demo:
# ./DeviceList
/lib64/libDeckLinkAPI.so: undefined symbol: CreateVideoConversionInstance_0002
DeckLinkAPI Version: 12.8.0
=============== DeckLink 8K Pro ===============

Attribute List:
Device Interface: PCI
Device Persistent ID: c75e8f80
Device Topological ID: 580100
Sub-device Count: 4
Sub-device Index: 0
Serial Port Available: No
Audio Channel Count: 64
Input Mode Detection Supported: Yes
Duplex Mode: Half
Internal Keying Support: No
External Keying Support: No
HDMI Timecode Support: None
Error querying 'Has Monitor Out' attribute - Error Code: 0x80000003
Error retrieving mezzanine type - Error Code: 0x80000003

Failed to obtain IDeckLinkOutput interface - Error Code: 0x80000004
Failed to obtain IDeckLinkInput interface - Error Code: 0x80000004

Hello Degang,

As you noticed, the issue is caused by changes made to the buffer allocator, which started from version 14.3.

I recommend reviewing the Desktop Video 14.3 SDK Migration Guide,

It would also be helpful to review the posts and responses below from Cameron regarding these issues:

Memory Usage by EnableVideoInput

Frames no longer arrive with allocator

Desktop Video 14.3 drivers not backwards compatible

Thanks a lot

Hello Degang,

As you noticed, the issue is caused by changes made to the buffer allocator, which started from version 14.3.

I recommend reviewing the Desktop Video 14.3 SDK Migration Guide,

It would also be helpful to review the posts and responses below from Cameron regarding these issues:

Memory Usage by EnableVideoInput

Frames no longer arrive with allocator

Desktop Video 14.3 drivers not backwards compatible