eos-movrec on Mac & Linux in 2026: What Actually Works Now (2026)

Quick Answer: The eos-movrec tutorials still ranking on Google are from 2015 (the old Ubuntu PPA guide) — they don’t work on modern systems. As of 2026 there are two realistic paths for Mac and Linux users with old Canon DSLRs: the actively maintained community fork on GitHub (shootthemoonfilms/eos-movrec, with Qt builds for Windows, Linux, and Mac — note: a community fork, not the original author’s release), and the gphoto2 + ffmpeg → OBS pipeline, which replaces eos-movrec entirely for webcam/streaming use. This page covers both, honestly. If you’re after the original 2015-era Homebrew method, that’s preserved separately in the older Mac install guide — read that only if you’re on a period-correct old macOS.

Pick your path below — fork for the classic app experience, gphoto2 pipeline for the modern streaming setup.

Forget the 2015 PPA tutorial

The ubuntuhandbook.org tutorial from June 2015 ranks by default because nothing newer targeted the keyword — but its PPA is dead and its steps don’t survive a modern Ubuntu or macOS. Everything below was verified against sources current to 2026. Don’t waste an afternoon on decade-old install instructions.

Path 1: The Community Fork (Closest to Classic eos-movrec)

The GitHub repository shootthemoonfilms/eos-movrec is a community fork of the original probonopd/eos-movrec that has been updated within the last year, with Qt-based builds covering Windows, Linux, and macOS. To be clear: this is not an official release — it’s the community keeping the software alive, and you should read the README and check recent commit activity before installing, as you would with any community project. What it gets you is the familiar eos-movrec workflow (connect camera over USB, capture Live View to MJPEG AVI) on an OS the original never properly supported. Steps in brief: install the fork’s build for your platform from its GitHub releases page, connect the camera in PTP mode over a data-capable USB cable (cable checklist applies on every OS), and grant any camera/USB permissions your OS requests on first launch.

Path 2: gphoto2 + ffmpeg → OBS (the Modern Replacement)

If your goal is using the old Canon as a webcam or stream source rather than recording AVIs, you may not need eos-movrec at all. The gphoto2 + ffmpeg pipeline (as implemented by projects like dslr-usb-stream) captures the camera’s Live View via gphoto2, pipes it through ffmpeg, and feeds it into OBS as a virtual camera — on both macOS and Linux. Conceptually: gphoto2 --capture-movie streams MJPEG frames to stdout, ffmpeg repackages them, and OBS picks up the virtual-cam device. This stack is actively maintained (unlike the 2015 PPA), runs natively on Apple Silicon via Homebrew, and sidesteps every eos-movrec platform quirk — at the cost of a command-line setup instead of a GUI.

Path 3 (Mac Classic): Camera Live + CamTwist

An older but still-cited Mac method pairs Camera Live (which exposes the tethered Canon as a Syphon video source) with CamTwist (which turns a Syphon feed into a virtual webcam). This was documented for USB-tethered Canons on the Cambridge in Colour forums and remains a valid fallback on older Intel Macs. On current macOS versions, though, CamTwist’s age shows — try Path 1 or Path 2 first, and keep this one in reserve for legacy hardware.

Which Path for You?

  • Want the eos-movrec app experience on Mac/Linux? → Path 1, the community fork.
  • Want the camera in OBS/Zoom as a webcam? → Path 2, gphoto2 + ffmpeg. Most robust on modern systems.
  • On an old Intel Mac (pre-2020)? → Path 3 may still work, or the 2015-era Homebrew guide if your macOS is old enough.
  • On Windows? → You don’t need this page — use the standard Windows download.

Cross-Platform Gotchas

Whichever path you choose, the physical layer is identical across OSes: PTP communication mode in the camera menu, a data Mini-B cable (not charge-only), direct USB port with no hub, and no competing program holding the camera (quit cloud-sync camera upload and photo importers — see the conflict guide). Linux users: you may need a udev rule or dialout-group membership for USB access; Mac users: approve the USB/camera permission prompts or the app silently gets nothing. Frame-rate expectations are the same everywhere too — about 22 fps ceiling, covered in the low-FPS guide. More platform fixes live in the troubleshooting hub.

Frequently Asked Questions

Q: Does eos-movrec work on Mac?

The original 2010-era builds were Windows-focused, but the active community fork on GitHub (shootthemoonfilms/eos-movrec) provides Qt-based builds including macOS. Alternatively, the gphoto2 + ffmpeg pipeline below works on Mac today.

Q: Does eos-movrec work on Linux in 2026?

The 2015 Ubuntu PPA tutorial still ranking in search results is long stale. Current options: build the shootthemoonfilms fork from source, or skip eos-movrec entirely and use gphoto2 + ffmpeg to stream the Live View feed into OBS.

Q: Is the shootthemoonfilms fork official?

No — it’s a community fork, not affiliated with the original eos-movrec author (probonopd). It’s simply the most actively maintained descendant, which is why this page points to it. Treat it like any community software: check the README and recent commits before installing.

Q: What’s the simplest Mac path: fork or gphoto2?

If you want the familiar eos-movrec interface, try the fork’s macOS build first. If you mainly need the camera as a webcam/OBS source, the gphoto2 + ffmpeg route is more robust and better documented for modern macOS.

Q: How is this different from the old Homebrew install guide?

The older Mac guide on this site covers the 2015-era Homebrew method, which no longer works on current macOS. This page covers what works now: the maintained fork and the gphoto2 pipeline. Link between them depending on your macOS version.

Q: Will these methods work on Apple Silicon Macs?

The gphoto2 + ffmpeg pipeline does (both are native on Apple Silicon via Homebrew). For the Qt fork, check its GitHub releases page for ARM builds — availability varies by release, and running under Rosetta is a fallback, not a guarantee.