Package Details: decklink 11.1-1

Git Clone URL: (read-only)
Package Base: decklink
Description: Drivers for Blackmagic Design DeckLink, Intensity or Multibridge video editing cards
Upstream URL:
Licenses: custom
Submitter: alub
Maintainer: fthiery (goldensuneur)
Last Packager: goldensuneur
Votes: 9
Popularity: 0.679285
First Submitted: 2015-10-03 15:38
Last Updated: 2019-04-01 11:52

Latest Comments

1 2 3 4 5 6 ... Next › Last »

goldensuneur commented on 2019-04-01 11:59

It looks like they fixed the problems with kernel 5.0. It is know building and working normally.

Polarity commented on 2019-04-01 11:08

Looks like the next release is out.

Serus commented on 2019-03-15 20:06

I got an email back from BM stating they're aware of the problem and will be addressed in the next release.

guitaristtom commented on 2019-03-13 03:26

Well at least I'm not crazy about it not working with Kernel 5.0.0

I guess I'll have to wait to use my capture card again sigh. Hopefully, BM fixes it on their end soon.

lukas2511 commented on 2019-03-06 23:19

Mh. It seems that the sound module actually might be negatively affected by leaving the FPU disabled. I'm not sure. I'll use my patch for now as it's working for me and I don't need sound, but I'm hoping to see a new decklink release soon, also adressing the last build issue...

lukas2511 commented on 2019-03-06 23:05

@Serus Well, we can also just leave the FPU disabled. That might result in some slowdown, but would be completely legal. See the updated patch

I'm not sure if this might have some other unforeseen side-effects, but at least in my tests I don't really see any difference. Maybe some scaling setups or the alpha blends on the decklink duo would be a bit more problematic? No idea. Also hoping for a vendor-side fix.

Serus commented on 2019-03-06 22:41

@lukas2511 I did something similar you did.

But the license rewrite is illegal and not something we can put up here on the AUR.

I also confirmed it works with my Intensity Pro 4K, I also sent an email to BlackMagic explaining the situation, hoping they'll come up with a fix soon.

At this point in time the approved workaround is my earlier mentioned workaround.

lukas2511 commented on 2019-03-06 22:17

Got my other modules fixed. Decklink works fine with 5.0, the only real issue are those GPL-only symbols.

lukas2511 commented on 2019-03-06 21:42

Well... actually... maybe somebody could test this patch:

The affected symbols weren't mentioned in the pre-built module, I took the wrong name, it actually calls a function in blackmagic_lib.c, that way we actually can wrap every affected call.

The patch is done directly against /usr/src directory, didn't prepare anything for the PKGBUILD as I don't like rewriting the modules license for a release.

Other than loading the modules I can't test it myself as my decklink system has a few other modules with the same issue and I can't easily boot into 5.0 because of this.

For a release I'd suggest waiting for ZFSonLinux to write their workaround for the issue, maybe it's reusable for the decklink module and that way we wouldn't need to rewrite the license.

lukas2511 commented on 2019-03-06 20:33

Unfortunately the affected symbols are also used in the pre-compiled blackmagic library so we can't cleanly replace the affected code...

I have an idea on mind on how to fix this, but I'm hoping for a fix from Blackmagic as my fix would be very very ugly involving a binary patch to the shipped library... :-/