-
Notifications
You must be signed in to change notification settings - Fork 1
FAQ and Troubleshooting
No. Tamp plans the bitrate to land under your target and verifies the result, re-encoding if it overshot. If a target is genuinely impossible for a clip, it tells you instead of producing a too-big or unwatchable file — see "Target too small".
No. All encoding happens locally with a bundled FFmpeg. There's no telemetry and no account. The only optional network request is the GitHub update check, and it sends nothing about you. See Privacy.
Yes — compression is fully local. Only the optional update check needs the internet, and it's off by default.
Right next to the original, with a (tamped …) name. Optionally it's also
copied to your clipboard. See
Output files.
That's by design: Tamp hides its own (tamped …) outputs from the recordings
list while the original exists, so the list stays "things to compress." Find
every output in the Converted tab.
Make sure your preset's Target MB is at or under the platform's limit (e.g. Discord's free limit is 10 MB; the built-in preset already targets that). If the file is fine but too long to look good that small, split it into parts.
Yes — run it through several presets. But if Move original to Trash is on, the original is gone after the first conversion, so Tamp allows only one. Turn that toggle off to keep the original and export multiple formats. See Behavior.
If Move original to Trash is on, Tamp moved it to the Trash (recoverable) after compressing. The compressed copy stays in your history.
Tamp reuses an existing output when the input and settings match (a fingerprint in the file name). Change any setting to force a fresh encode. See reuse.
Not yet. The internal platform layer is ready, but Linux needs a clipboard/tray strategy and a CI target. Today's builds are macOS (Apple Silicon) and Windows.
No. Tamp lives only in the menu bar (macOS) or system tray (Windows). Open it with the icon or the toggle shortcut.
The Windows build isn't code-signed yet. Click More info → Run anyway. It installs per-user, no admin needed. See Installing on Windows.
Current macOS builds are signed with a Developer ID and notarized by Apple, so they open with no warning. If you hit a Gatekeeper prompt, you're on an old unsigned build — grab the latest from Releases, or right-click the app → Open → Open once.
- Tamp only lists files in your watched folders. Point it at wherever your recorder saves: Watched folders.
- If you see a "couldn't read a folder" notice, that folder is offline or permission-denied (common for network shares) — it'll reappear once reachable.
- Your finished outputs live in the Converted tab, not the Videos list.
A long or high-resolution clip may not fit your target even at minimum quality. Tamp tells you rather than producing mush. Options: lower the Max FPS or downscale (Max width / Scale %) in the preset, pick a bigger target, or split it into parts so each part fits.
With Use GPU encoder on, Tamp prefers the fast hardware encoder. For tight targets it switches to slower, more precise two-pass software encoding — that trade-off is intentional. You can toggle the encoder in Behavior. See hardware vs software.
The file was moved or deleted outside Tamp after it was recorded/converted. Re-record or re-convert as needed.
It rides on desktop notifications. If notifications are off, Preferences shows a recovery card (Enable notifications / Open System Settings). To disable the warning entirely, set its threshold to 0 under Shortcuts.
Tamp keeps rotating local logs with every FFmpeg command and error. Open the folder via tray menu → Open Logs. When filing an issue at github.com/ValeriyMaslenikov/tamp/issues, include your OS, the app version (bottom of Preferences), what you did, and the relevant log lines.
Getting Started
Using Tamp
Settings
Help