Package Details: decklink 14.4.1-2

Git Clone URL: https://aur.archlinux.org/decklink.git (read-only, click to copy)
Package Base: decklink
Description: Drivers for Blackmagic Design DeckLink, Intensity or Multibridge video editing cards
Upstream URL: https://www.blackmagicdesign.com/support/family/capture-and-playback
Licenses: custom
Submitter: alub
Maintainer: goldensuneur
Last Packager: goldensuneur
Votes: 24
Popularity: 0.000000
First Submitted: 2015-10-03 15:38 (UTC)
Last Updated: 2025-02-16 11:39 (UTC)

Pinned Comments

goldensuneur commented on 2020-03-02 19:00 (UTC)

I finally had time to investigate the issue. It looks like that as of 11.5, the DesktopVideoHelper.service has to be running for the capture card to work properly.

Latest Comments

« First ‹ Previous 1 .. 13 14 15 16 17 18 19 20 21 22 23 .. 25 Next › Last »

fthiery commented on 2018-02-12 09:32 (UTC)

Okay, so right now linux-lts (which just switched to 4.14) is the only working version.

OniLink commented on 2018-02-09 01:07 (UTC) (edited on 2018-02-09 02:48 (UTC) by OniLink)

TT;DR (too technical, didn't read): Linux 4.15 doesn't work with Blackmagic anymore because it removed some ancient code that Blackmagic still uses.

-

Uninstalled my previous hacky driver install as the Blackmagic was no longer recognized after a reboot. Tried to reinstall with the current version and ran into an error - as of 4.15.1, an old timer interface is removed.

If Blackmagic wants to get their code working on new Linux kernels, they need to replace the end of bm_timer_alloc at bm_util.c line 420 with

timer_setup(timer, (void(*)(bm_timer_t*))callback, 0);

return timer;

instead of the init_timer line and followup. Unfortunately this will break any code using the driver as it breaks expected behavior (data becomes unused, the callback gets sent a pointer to the timer instead), but that's on them. Trying to patch it like this and install leads to a crash as soon as the module blackmagic-io is inserted into the kernel, telling me I missed something probably. I couldn't find any use of this function in the driver code, though. It's likely a problem in Blackmagic's other software expecting certain behavior from the driver which necessarily changes due to this fix.

fthiery commented on 2018-02-01 12:09 (UTC)

I tried to patch dkms.conf to fix the path, but it's still not being called. It looks to be doing depmod && modprobe anyway, which we are also doing.

We need a dkms guru to sed/patch it so that dkms install and dkms remove do work. Currently i'm unsure whether the dkms stuff even has any effect at all (and the install script is doing everything by hand).

If anyone is interested, the files are in /usr/src/blackmagic-10.9.10a2/

I reworked the install script to cleanup better (e.g. remove /usr/src/blackmagic-*); please feedback it the thing also works for you. Seems to work for me. But this package is looking more and more like frankenstein.

fthiery commented on 2018-02-01 11:43 (UTC)

Apparently the dmks script is trying to load the modules

POST_INSTALL="../../lib/blackmagic/blackmagic-loader $PACKAGE_NAME $PACKAGE_VERSION"

The path is wrong, because it's here: /usr/lib/blackmagic/DesktopVideo/blackmagic-loader

So i'm guessing it's not just not executable, but not found at all. We are loading the modules manually anyway and it seems to be working...

Kakashi-sensei commented on 2018-02-01 11:14 (UTC)

To be honest, I haven't had the chance to test it personally. I trust your confirmation.

fthiery commented on 2018-02-01 11:10 (UTC)

I also see the warning, but it does seem to work anyway "Warning: The post_install script is not executable."

@Kakashi-sensei doesn't the board work at all ?

Kakashi-sensei commented on 2018-01-30 08:56 (UTC)

I'm getting the following error after each install of a dkms module: Warning: The post_install script is not executable.

fthiery commented on 2018-01-29 17:07 (UTC)

@OniLink thanks for testing, i updated the package and it does compile and insert against 4.14.15-1-ARCH.

Kakashi-sensei commented on 2018-01-28 21:31 (UTC)

Well, at least the package maintainer knows what to do?