Bad performance on '2.4 Stable' with channels at 4K50p

[Sidonai-1]

Observed Behavior

When configuring more than one channel with decklinks 8KPro set at 4K 50p, performance tanks and decklink output is not smooth. Tried with ProRes 422 files but any file at any resolution has the same effect.

This is with normal UHD50p video modes, even before playing anything:

This is with custom video modes, smaller than full UHD, playing a couple of files.

Version 2.4.0 1e25c7a Stable and previous RC1 both have this issue.

Issue is not present at 4k 25p

Issue is still present if audio-embedded=false, but it improves slightly.
Issue happens with normal 4k video-modes as well as custom ones.

Expected behaviour

Version 2.4.0 80f8ee7 Dev does not suffer from this issue. (04/08/2023 16:38)

Full UHD:

Custom video-modes:

Steps to reproduce

1. Set 2 decklinks to 4K50p
2. Play video files with audio

Environment

• Server version: 2.4.0 1e25c7a Stable
• Operating system: W10
• BMD Driver version: 12.9
• Videos: ProRes 422 25/50p
• HP Z8 - Xeon Gold 6136 (x2) 24C/24T (Hyperthreading OFF / NUMA Nodes OFF)
• Config:

 <channels>
    <channel>
      <video-mode>2688x1536px50</video-mode>
      <consumers>
        <decklink>
          <wait-for-reference>auto</wait-for-reference>
          <wait-for-reference-duration>4</wait-for-reference-duration>
          <device>1</device>
          <video-mode>2160p5000</video-mode>
          <subregion>
            <src-x>0</src-x>
            <src-y>0</src-y>
          </subregion>
          <buffer-depth>10</buffer-depth>
          <embedded-audio>true</embedded-audio>
        </decklink>
      </consumers>
    </channel>
	 <channel>
      <video-mode>1536x1536px50</video-mode>
      <consumers>
        <decklink>
          <wait-for-reference>auto</wait-for-reference>
          <wait-for-reference-duration>4</wait-for-reference-duration>
          <device>2</device>
          <video-mode>2160p5000</video-mode>
          <subregion>
            <src-x>0</src-x>
            <src-y>0</src-y>
          </subregion>
          <buffer-depth>10</buffer-depth>
          <embedded-audio>true</embedded-audio>
        </decklink>
      </consumers>
    </channel>
	<channel>
      <video-mode>1080i5000</video-mode>
     <consumers>
        <decklink>
          <video-mode>1080i5000</video-mode>
		  <device>5</device>
          <buffer-depth>10</buffer-depth>
          <embedded-audio>true</embedded-audio>
        </decklink>
      </consumers>
    </channel>
  </channels>

  <video-modes>
    <video-mode>
      <id>2688x1536px50</id>
      <width>2688</width>
      <height>1536</height>
      <time-scale>50000</time-scale>
      <duration>1000</duration>
      <cadence>960</cadence>
     </video-mode>
      <video-mode>
      <id>1536x1536px50</id>
      <width>1536</width>
      <height>1536</height>
      <time-scale>50000</time-scale>
      <duration>1000</duration>
      <cadence>960</cadence>
    </video-mode>
  </video-modes>

[Julusian]

I'm wondering if this is a consequence of 3816e08.
Could you try that build and the one before to see if this could have introduced it?

[Sidonai-1]

I'm wondering if this is a consequence of 3816e08. Could you try that build and the one before to see if this could have introduced it?

I think your suspicions are correct.

version 3816e08 has this issue. And the previous one, 57f29cc works fine.

[Julusian]

That commit is reverted for windows, hopefully that is enough to resolve this