// the take
oeip is a GPGPU abstraction layer for piping video — camera, screen capture, video files, RTMP streams — through DX11/CUDA processing directly into Unity3D or UE4 textures, without a CPU round trip. It's aimed at devs building AR/video-mixing tools inside a game engine who need real-time throughput instead of the usual 30fps media-pipeline ceiling. The author has already moved on to a successor project (aoce), so this is really a reference implementation at this point.
The core design decision is right: most engine video plugins pull frames to CPU memory and hand them back to the engine's own rendering context, which is the actual bottleneck at 90fps — oeip keeps frames in GPU memory and shares textures straight into Unity3D/UE4. It unifies DX11 HLSL/ComputeShader and CUDA behind one layer interface, each with declared inputs/outputs like a dataflow graph, so you're not hand-rolling backend-specific code per platform. It also wires in real functionality beyond the toy-demo level: RTMP push/pull streaming and a darknet (YOLO) integration for GPU-side video analysis.
The README says outright it's no longer maintained and points readers to a rewrite (aoce) — anyone adopting oeip is choosing a dead end over the thing the author considers the real version. It's Windows/DX11/CUDA 10.1-only; the Vulkan backend mentioned in the design goals never shipped, so there's no path off Windows or off Nvidia hardware. The build itself is fragile: a plain zip download doesn't compile, you need a shallow git clone plus manually fetching a separate third-party DLL repo and copying files into place by hand — there's no package manager or scripted setup. Documentation is Chinese-only with no English README, which will stop most non-Chinese-speaking devs before they get to the DX11/CUDA setup pain.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →