-The Intensity Shuttle follows a protocol whose exact format is still
-unknown, and the driver is still in alpha stage. (There is no API or
-ABI stability, for one, and everything is really messy and uncommented.)
-In particular, it will often do something on init that makes the card
-seemingly reset and disconnect off the bus (and then reset).
-This being said, once it's actually up, I've done ten-hour 720p60
-captures on my Lenovo X240 without a single drop. It seems to want about
-10–15% of one CPU core.
+The BlackMagic cards follow a protocol whose exact format is still
+unknown, and the driver is still in beta stage. (The API/ABI is nearing
+stability, but is still not really locked.)
+
+It seems to want about 10–15% of one CPU core; a significant chunk of this is
+copying data from the kernel over to userspace, which can be skipped by means
+of zerocopy USB if you have a very recent libusb (>= 1.0.21) and a recent
+kernel (>= 4.6.0). There's a decode step which also takes some time and memory
+bandwidth, but it supports custom memory allocators, so that once the USB
+packets are available to userspace, you can decode directly into e.g. pinned
+GPU memory.