Prerequisites¶
The Conform module's export engines rely on two third-party tools that must be installed separately. Neither is included with Scrub or Adobe Premiere Pro.
| Tool | Required For | Free? |
|---|---|---|
| FFmpeg | Trimming non-R3D clips | Yes — open source |
| REDCINE-X PRO (REDline) | Exporting R3D (RED camera RAW) clips | Yes — requires RED account |
If you only use Adobe Media Encoder for exports, neither tool is required.
FFmpeg¶
FFmpeg is a free, open-source media tool used by Scrub to trim clips with frame-accurate precision. It must be installed and accessible on your system before using the FFmpeg engine.
Install on macOS¶
The recommended method is Homebrew. If you don't have Homebrew installed, install it first:
Then install FFmpeg:
Homebrew installs the binary to /usr/local/bin/ffmpeg (Intel) or /opt/homebrew/bin/ffmpeg (Apple Silicon). Scrub's Auto detection checks both locations, so a standard Homebrew install is found on Intel and Apple Silicon alike. If Auto can't reach the folder (Premiere's sandbox sometimes blocks it), use Browse to point to the path shown by which ffmpeg.
Verify the installation:
You should see version info starting with ffmpeg version 7.x....
macOS Gatekeeper Warning¶
macOS may block FFmpeg when Scrub tries to call it from the command line, even if you can run it yourself in Terminal. This happens when the binary carries a quarantine flag from the download.
Fix — run this once in Terminal:
# Intel Mac (Homebrew default)
xattr -d com.apple.quarantine /usr/local/bin/ffmpeg
# Apple Silicon (Homebrew default)
xattr -d com.apple.quarantine /opt/homebrew/bin/ffmpeg
If you installed FFmpeg manually to a different location, replace the path with wherever your ffmpeg binary lives. You can find it with:
Then run:
Note
FFmpeg installed via Homebrew usually doesn't need this — Homebrew strips the quarantine flag automatically. You're most likely to hit this if you downloaded a pre-built binary from ffmpeg.org manually.
Install on Windows¶
Option 1 — winget (built into Windows 10/11, recommended):
Open Terminal or PowerShell as Administrator and run:
This installs FFmpeg and adds it to your PATH automatically.
Option 2 — Chocolatey:
If you have Chocolatey installed:
Option 3 — Manual install:
- Download the latest build from ffmpeg.org/download.html (choose the Windows release from gyan.dev or BtbN)
- Extract the zip to
C:\ffmpeg - The binary should be at
C:\ffmpeg\bin\ffmpeg.exe— this is where Scrub auto-detects it
Optionally, add C:\ffmpeg\bin to your system PATH so you can run ffmpeg from any terminal.
Verify the installation:
After Installing¶
In Scrub's Conform settings, connect the binary using Auto or Browse — see Connecting the Binary to Scrub below. On macOS the binary lives in a hidden folder, so you'll likely need the ⌘⇧G Browse trick described there.
REDCINE-X PRO (REDline)¶
REDCINE-X PRO is RED's official post-production application for R3D (RED camera RAW) footage. It includes REDline, a command-line tool that Scrub uses to debayer and export R3D clips.
Note
REDCINE-X PRO is only required if your project contains .R3D files from RED cameras. If you're not working with RED footage, you can skip this entirely.
Download¶
REDCINE-X PRO must be downloaded directly from RED's website. A free RED account is required.
- Go to red.com/downloads
- Sign in or create a free RED account
- Download REDCINE-X PRO for your platform
There is no package manager installation for REDCINE-X PRO — the installer from RED's site is the only method.
Install on macOS¶
- Open the downloaded
.dmgfile - Drag REDCINE-X PRO to your Applications folder
- Launch it once to accept the license agreement
REDline will be located at:
Verify REDline is accessible:
macOS Gatekeeper Warning¶
Even if REDCINE-X PRO opens fine, macOS may still block the REDline binary when Scrub tries to call it from the command line. This is a separate Gatekeeper restriction — the app and its internal binaries each carry their own quarantine flag.
Fix — run this once in Terminal:
The -dr flags recursively remove the quarantine attribute from the entire app bundle, including REDline. After running this, Scrub can call REDline without macOS blocking it.
If you're unsure of the install path, you can find it with:
Then substitute that path into the xattr command above.
Note
If REDCINE-X PRO itself was also blocked when you first opened it, you may need to allow it in System Settings → Privacy & Security → Allow Anyway before the xattr command will fully take effect.
Install on Windows¶
- Run the downloaded installer
- Follow the on-screen prompts (default install location is fine)
REDline will be located at:
Verify REDline is accessible:
After Installing¶
In Scrub's Conform settings, connect REDline using Auto or Browse — see Connecting the Binary to Scrub below. On macOS REDline is hidden inside the REDCINE-X PRO.app bundle, so you'll need the ⌘⇧G Browse trick described there.
Connecting the Binary to Scrub¶
Once FFmpeg or REDCINE-X PRO is installed, you point Scrub at the binary in Conform → Settings (the gear icon), next to the FFmpeg or REDLINE path field. There are two ways: Auto and Browse.
Auto-detect (try this first)¶
Click Auto. Scrub scans the standard install locations and fills in the path if it can confirm the binary is there.
Auto often can't see system folders — this is normal
Premiere runs Scrub in a sandbox that is frequently blocked from reading /Applications (macOS) and C:\Program Files / C:\ProgramData (Windows). When that happens, Auto reports "not found" even though the tool is correctly installed. Don't worry — just use Browse instead (below). Scrub never overwrites a path you set manually, so a failed Auto will never erase a path you picked with Browse.
Browse — Windows¶
- Click Browse.
- Navigate to the binary and select it:
- FFmpeg:
C:\ffmpeg\bin\ffmpeg.exe(or wherever you installed it) - REDline:
C:\Program Files\REDCINE-X PRO 64-bit\Redline.exe
- FFmpeg:
- Scrub saves the path and remembers it between sessions.
On Windows the file picker reaches these locations directly — no special steps needed.
Browse — macOS¶
This is the part that trips most people up. macOS hides system folders like /usr and /opt, and it treats applications as sealed bundles — so the file picker will not show the FFmpeg or REDline binary if you just click around. Use Go to Folder instead:
- Click Browse — the macOS open dialog appears.
- Press ⌘ + Shift + G (Go to Folder).
- Paste the full path to the binary:
- FFmpeg (Intel Mac):
/usr/local/bin/ffmpeg - FFmpeg (Apple Silicon):
/opt/homebrew/bin/ffmpeg - REDline:
/Applications/REDCINE-X Professional/REDCINE-X PRO.app/Contents/MacOS/REDline
- FFmpeg (Intel Mac):
- Press Return, then Open to select the binary.
REDline lives inside the app bundle
On macOS, REDCINE-X PRO is an application bundle, and REDline sits inside it at Contents/MacOS/REDline — which Finder hides by default. The ⌘⇧G path above goes straight to it. (In Finder you can also right-click REDCINE-X PRO → Show Package Contents → Contents → MacOS to see it.)
Not sure of the exact name or path on your machine? Run this in Terminal and use whatever it lists:
If REDCINE-X PRO is installed somewhere non-standard, find REDline with:
Don't forget the Gatekeeper step
After connecting REDline (or FFmpeg) on macOS, also run the one-time xattr quarantine-removal command from the Gatekeeper sections above — otherwise macOS may block Scrub from calling the binary even though the path is set correctly.
Quick Reference¶
| Tool | macOS Default Path | Windows Default Path |
|---|---|---|
| FFmpeg | /usr/local/bin/ffmpeg | C:\ffmpeg\bin\ffmpeg.exe |
| REDline | /Applications/REDCINE-X Professional/REDCINE-X PRO.app/Contents/MacOS/REDline | C:\Program Files\REDCINE-X PRO 64-bit\Redline.exe |
Both paths are where Scrub's Auto detection looks first. If your install is in a non-standard location, use Browse to set the path manually — Scrub saves it and remembers it between sessions.