Native Swift + Metal Architecture, Read-Only Project Migration, and One-Time Licensing


System Requirements, Performance Budgets, and Licensing
| Dimension | Oil Studio Specification | Engineering Details |
|---|---|---|
| OS & processor | macOS 15 or later · Apple silicon (M-series) | Native SwiftUI, AppKit, and Metal; zero Electron or web-wrapper overhead |
| Multi-track capture & sync | Screen, camera, mic, system audio & pointer telemetry | Native macOS display capture pipeline locked to a shared monotonic clock |
| Preview & memory budget | 60 fps direct-from-source preview; ≤ 1 GB RAM (15-min project) | No proxy generation wait; switchable Original, 1080p, or Fit Window preview quality |
| Export & color pipeline | ~5× realtime at 1080p60 (~1.5× at 4K60); MP4 (H.264/HEVC) & GIF | 180° shutter motion blur and end-to-end SDR BT.709 / sRGB color consistency |
| Project format & migration | .oilstudio package; read-only import of existing projects | APFS copy-on-write media cloning preserves footage, cursor paths, clicks, and zoom blocks |
| One-time license | Up to 2 Macs per license, zero subscriptions | Cryptographically signed lease works offline for up to 30 days; inactive seats free automatically after 30 days |
How does read-only project migration preserve cursor paths and zooms?
Open a supported existing recording project directly in Oil Studio (or run oilstudio import <path>) and Oil Studio stages a fresh .oilstudio package under ~/Movies/Oil Studio/ using APFS copy-on-write cloning, converting video tracks, camera footage, cursor coordinates, click timestamps, and zoom ranges.
Original project bundles are strictly read-only—Oil Studio never writes settings or cache files back into source packages, and reopening the same source reuses your converted project.
Why do playback, paused frames, and exported MP4s look identical?
Many editors use separate decoding paths for scrubbing, paused stills, and final export, causing washed-out gamma shifts. Oil Studio routes live playback, exact paused frames, and hardware-encoded MP4/GIF exports through the same custom Metal compositor in a unified SDR sRGB working space.
How does the website edition compare with the Mac App Store edition?
Both editions share the same recording, auto-zoom, on-device Whisper, redaction, and export engine. The website and Homebrew edition activates on up to two Macs with a license code, includes built-in automatic updates with safe-mode recovery, and supports the external oilstudio AI Agent CLI. The Mac App Store edition uses Apple’s App Sandbox and account receipt validation without a license code or external CLI.
When Oil Studio Is Not the Right Fit
- No Intel Mac, Windows, or macOS 14 support.Oil Studio targets Apple silicon unified memory and macOS 15 media APIs exclusively; there is no Windows, Linux, or browser build.
- Local file output, not cloud link hosting.Oil Studio exports clean MP4, GIF, and SRT files on your Mac rather than locking videos behind a monthly cloud hosting subscription.
Public verification & comparison links
Check notarized release checksums, full tool comparisons, and version history directly:
- Official Homebrew Cask tap on GitHubgithub.com
Public notarized DMG version numbers, download URLs, and SHA-256 hashes.
- Objective Mac screen recorder & editor comparisonsstudio.oiloil.org
Side-by-side feature boundaries, benchmarks, and 3-year ownership math across 9 Mac tools.
- Oil Studio public changelogstudio.oiloil.org
Full release history covering performance improvements, import fidelity, and new capabilities.
Common questions
01Can I try recording and editing before buying?
Yes. Download Oil Studio and test recording, auto-zoom, on-device Whisper captions, and editing for free without entering a card; activate a license when you are ready to export, with no forced watermarks.
02What happens if I replace a Mac without deactivating first?
You can deactivate a Mac instantly in Settings › License, or simply continue on your new machine—any device that has not renewed online for 30 days automatically frees its seat.