Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
1

Decklink Fails if set to Decklink set to rec2020 and timeline set to rec709

Engaged ,
Feb 21, 2025 Feb 21, 2025

HDR output is currently broken for decklink

Premiere 25.1.0

Desktop Video 14.4.1

Decklink output is fine in rec709

Decklink USUALLY works in rec2020 if the Sequence is set to rec2100, though sometimes only at 60p

Decklink completely crashes if the sequence is Rec709 and output is set to Rec2020

Also HDR metadata is NOT being sent over HDMI.

Not the equipmant as working fine in Resolve.

This used to keep functioning correctly without having to change preferences when changing colourspace

Hopefully this can be made to work automatically based on the Sequence setings, just like it does in Resolve.

Hopefully HDR support can be prioritised a bit more now that it is becoming a de facto deliverable for a lot of distributers.

 

Bug Acknowledged
TOPICS
Color , Editing and Playback , Performance or Stability
833
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Feb 21, 2025 Feb 21, 2025

Hopefully this can be made to work automatically
> based on the Sequence setings, just like it does in Resolve

Yes, we too hope that Blackmagic's PPro plugins respond correctly to available colorspace information. [Adobe doesn't write the Transmit plugins, that enable BMD devices in PPro.]

Status Acknowledged
Translate
12 Comments
Engaged ,
Feb 21, 2025 Feb 21, 2025

Could be an AMD / Threadripper Pro / PCIe5 /  Windows 11 24H2 problem, or a BMD driver problem but I suspect it is and Adobe issue as After Effects has had poor Decklink support in recent releases as well. Fully appreciate it is low in the priority but hopefully someone can take ownership of this

Translate
Report
Adobe Employee ,
Feb 21, 2025 Feb 21, 2025

Hopefully this can be made to work automatically
> based on the Sequence setings, just like it does in Resolve

Yes, we too hope that Blackmagic's PPro plugins respond correctly to available colorspace information. [Adobe doesn't write the Transmit plugins, that enable BMD devices in PPro.]

Status Acknowledged
Translate
Report
Engaged ,
Feb 21, 2025 Feb 21, 2025

Thanks 

Also this is only HDMI, SDI is fine

That is surprising, but explains why it doesn't work the same in After Effects

Who does write the Transmit code? Science Ninja Team Gatchaman perhaps?

Or BMD? 

 

I thought my card had died. Spent a lot of time troubleshooting.

Pretty sure this is a recent bug, but as I haven't been working in HDR I may not have noticed. I do remember that it didn't crash before when I was testing it

I wil see if anyone can help on the BMD forums

Translate
Report
Engaged ,
Feb 21, 2025 Feb 21, 2025

Also, should the original poster not be the one to determine what the correct answer is?

I have had a lot of unrelated responses classed as correct.

This is a clarification but not really a correct answer, as the Transmit plug in has possibly not changed and something else has caused the bug with it. 

Translate
Report
Adobe Employee ,
Feb 21, 2025 Feb 21, 2025

Hello @tristansummers,

Thanks for the question. Regarding solutions, the OP has priority, so we can unmark the discussion as correct since you are not satisfied with that answer. 

 

In this case, I likely marked the answer as correct. My decision was based on an answer by the engineering manager, who let you know that BMD Transmit plug-ins are developed by Blackmagic, and that with issues like this, Adobe has little control over. 

 

If that is not the case, continue to provide information so that the team can reproduce your bug.

Sorry for the misunderstanding.

 

Thanks,
Kevin

 

Kevin Monahan - Sr. Community & Engagement Strategist – Pro Video and Audio
Translate
Report
Adobe Employee ,
Feb 21, 2025 Feb 21, 2025

> Who does write the Transmit code?


PPro writes and maintains the Transmit plugin API.

Blackmagic (and numerous other partners) write Transmit plugins, that work with that API. 

 

I suspect it is and Adobe issue as After Effects has had poor Decklink support in recent releases as well...

After Effects uses the same BMD plugins PPro does.

 

Note: This could be a recent issue, as PPro has recently introduced new colorspace handling.

@Kevin-Monahan , I'm the one who marked it correct; my team owns PPro's Transmit functionality, and we talk with BMD regularly.

Translate
Report
Adobe Employee ,
Feb 21, 2025 Feb 21, 2025

Tristan, can you provide a (hopefully, small) project w/media, that reliably causes crashes, in 25.1? 

[I sent a DM with a link to private upload space]

Translate
Report
Engaged ,
Feb 21, 2025 Feb 21, 2025

Many thanks and appreciation Kevin and Bruce for clarifying that Adobe teams support the API and BMD support the plug in. That makes more sense and hopefully communication between you can help improve the products' cooperation. 

I'm not uploading a project because it's not project specific. It's any clip in a 709 sequence trying to play out as 2020.

I'm guessing the after effects API doesn't support the HDR output toggle options that the transmit plug in has in premiere. It may well be my system or hardware that is at fault but thought I'd flag it as there is so much improvement and over hauling going on at present and I wouldn't want anything that got broken to impact too many people of it could easily be rectified. 

I also know 14.4.1 addressed some pcie5 issues, so it may be the driver has had unexpected side effects. 

I'm also aware there's always a risk of slightly less stability running threadripper.  

Thanks for keeping the ship afloat everyone.

Translate
Report
Adobe Employee ,
Feb 21, 2025 Feb 21, 2025

It's any clip in a 709 sequence...

Totally plausible, and...can we have a piece of example media, in a sequence, in which you're seeing the behavior? 

[If you'd rather not share the media via upload, then sending MediaInfo's analysis of the file might also help...]

Whenever possible, we'd rather do 'apples to apples' testing. No faith-based development! 🙂



Translate
Report
Engaged ,
Feb 21, 2025 Feb 21, 2025

Fully appreciate that and if it was in any way dependant on clip or project I would. 

But this is anything at all in standard seqs in empty new comp. 

I'll double check it's not none standard sizes for the preview codecs but I've just been dropping in my standard calibration stock clips

Translate
Report
Adobe Employee ,
Feb 22, 2025 Feb 22, 2025

if it was in any way dependant on clip or project I would. 

 

The behavior isn't something we've seen or heard of, and we use a broad variety of media, and BMD devices, across our teams. 

We're happy to pursue the issue further, provided a project, media, and steps to follow which reliably reproduce the issue.

Translate
Report
Engaged ,
Mar 04, 2025 Mar 04, 2025
LATEST

Hi

It may just be an error with the HDMI output on the card, or HDMI implementation of the driver.

Latest BMD update desktop video14.5

I can report that SDI 2160P is displaying correctly in Premere at 24p and does not crash if timeline is 709 and output is 2020. HDR flag is being sent over SDI. loks like the driver is good. but:

I can report that 2160p is not displaying colour correctly at 60p in Premiere, despite the 4kEx12G and Premiere specification supporting it.

I can report that Desktop Video 14.5 is allowing HDR output from the After Effects Beta.

So the Mercury Transmit plug in is still not performing correctly or fully stable but it is great to see HDR support in After Effects. Hopefully Tangent support for Lumetri will come one day to compensate for removing Color Finesse. 

Toggling back and forth to Premiere to grade does not fit a lot of workflows

Translate
Report