Package Base Details: decklink

Git Clone URL: https://aur.archlinux.org/decklink.git (read-only, click to copy)
Submitter: alub
Maintainer: goldensuneur
Last Packager: goldensuneur
Votes: 24
Popularity: 0.000153
First Submitted: 2015-10-03 15:38 (UTC)
Last Updated: 2024-04-12 20:17 (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 2 3 4 5 6 7 8 9 .. 24 Next › Last »

rama_g commented on 2021-09-14 15:30 (UTC)

awesome, also working here on 5.14.3-arch1-1 -- happy to be able to update the system, was holding off until now since I rely on the decklink drivers, using it everyday -- thanks for the package update! FWIW it did require a reboot for the device to be found by BlackmagicDesktopVideoSetup.

YAOMTC commented on 2021-09-13 04:19 (UTC) (edited on 2021-09-13 08:27 (UTC) by YAOMTC)

Can confirm it works for me too with 5.14.2.arch1-2. Thanks for updating the PKGBUILD.

EDIT: Though, the audio stutters quite badly. I'll have to see if I can get that fixed...

EDIT2: happens on Windows too, I think it may have to do with PCI bandwidth available. I get a warning about dropped frames when I record with MediaExpress. But there's not as many dropped frames when I record a 720p60 signal vs 1080p60.

EDIT3: yeah that was it. Unplugging the TV tuner card I never use gave me the PCI bandwidth the card needs to work properly.

frostwork commented on 2021-09-10 13:22 (UTC) (edited on 2021-09-10 13:37 (UTC) by frostwork)

edit - sorry, I don't know the half markdown syntax here. deleted my PKGBUILD patch.

edit2: sorry for the lame workaround - uploaded a PKGBUILD gist here: https://gist.github.com/frostworx/6f1c12bdf5c0f319bcbd0ef18e3e301b

edit3: I can confirm that the decklink works fine with 5.14.2-xanmod1-1 with the patched drivers

frostwork commented on 2021-09-10 13:09 (UTC)

thx for the quick reply! just gave it a quick try. The patch applies fine, but when manually building the build fails with "bmio_serial.c:174:28: Fehler: Initialisierung von »unsigned int ()(struct tty_struct )« von inkompatiblem Zeigertyp »int ()(struct tty_struct )« [-Werror=incompatible-pointer-types]" (the other module blackmagic-12.1a9 has the same error). the Werror can be disabled by adding "-Wno-error=incompatible-pointer-types" to the EXTRA_CFLAGS in the Makefiles. Both modules build fine then. Haven't tested functionality, as I'm almost off for a short trip \o/ :) Good luck and thanks a lot for maintaining the PKGBUILD! :)

goldensuneur commented on 2021-09-10 13:04 (UTC)

thx, I'll try the patch later today after work. If it builds on my machine I'll push a new revision to the decklink package.

frostwork commented on 2021-09-10 12:56 (UTC)

fyi: a blackmagic dev posted a patch in the thread mentioned before here: https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=144876#p788448 haven't tested it yet

frostwork commented on 2021-09-07 03:27 (UTC)

fyi, upstream forum issue thread: https://forum.blackmagicdesign.com/viewtopic.php?f=12&t=144876

YAOMTC commented on 2021-08-26 01:23 (UTC)

About a month ago I had sent in my card to their technical support team, thinking it might have been a hardware issue. The other day I finally heard back from them, and they said it was working on Windows. They said they did not have a Linux machine to test with (despite advertising Linux support on the box) and were not able (allowed?) to run a live DVD. They are now shipping it back to me.

frostwork commented on 2021-08-19 14:42 (UTC)

@scaramanga I just coincidentally found out that the drivers are currently broken (I barely use the card) and therefore found your comment. Thanks for the heads-up & contacting upstream! :)

scaramanga commented on 2021-08-14 10:32 (UTC)

Short update: After almost a week Customer Support told me they won't help with Linux "due to the high level of user customisation and configurability", but referred me to the Developer Support team.

There they actually helped and provided a fix. It sounded like there should be an official update to the driver some time soon, but they didn't say a date.