⚓ Anchor Sub Sync
Anchor is a GPU-accelerated tool that automatically synchronizes subtitle files (.srt, .ass) to video files using audio alignment. It uses OpenAI's Whisper (via WhisperX), or optionally NVIDIA's Parakeet, to listen to the video track, applies some alignment techniques and perfectly aligns every subtitle line.
⚡ Core Capabilities
- 🔊 Audio Sync: Auto-align subtitles to video using Whisper, or the optional Parakeet engine (no reference text needed).
- 📑 Reference Sync: Automatic Sync using a perfectly timed reference subtitle. Pair a whole season in one screen.
- 📍 Point Sync: Fix linear drift by matching distinct lines against a reference subtitle.
- 🎥 Change Frame Rate: Retime a subtitle from one frame rate to another (e.g. 23.976 to 25), from a picker or with
--from-fps/--to-fps. - 🩺 Sync Check: Find out whether a subtitle is in sync, offset or drifting, and optionally fix it. Changes nothing unless you ask.
- 🌐 Translation: Context-aware translation using NLLB, with dual-speaker preservation and auto-formatting.
- 📝 Transcriptions: Generate subtitles directly from the video.
- 📦 Container Tasks: Extract, Embed, or Strip subtitles from media
- 🔥 Burn-in: Permanently burn subtitles into video
- 🧽 Clean & Fix: Repair and clean subtitle files
- 🔄 Convert: Convert between subtitle formats
- 📥 Download: Automatically find and download matching subtitles
- 🔌 API Mode: Expose Anchor's translation engine as a local API server, compatible with Subtitle Edit's Auto-Translate feature.
🚀 Requirements
- OS: Linux | Windows | MacOS
- GPU: GPU Recommended, CPU only is possible (but slower)
- Python: 3.10 or 3.11
- ffmpeg / ffprobe: required for audio probing, metadata language detection, and audio extraction
📦 Installation
1. Install Anchor
Install the tool directly from the repository.
pip install anchor-sub-sync
⚠️ Important: Because this tool relies on hardware acceleration, standard pip install often pulls the wrong drivers (CPU versions). If it does not work out of the box, please follow these steps in order.
2. Install PyTorch (choose per hardware)
Before installing PyTorch, run a few quick checks to detect your hardware:
# NVIDIA / CUDA
nvidia-smi || true
python3 -c "import torch; print('cuda', torch.cuda.is_available(), getattr(torch.cuda, 'get_device_name', lambda i: '')(0))"
# Apple Silicon (MPS)
python3 -c "import torch; print('mps', torch.backends.mps.is_available())"
Then install the appropriate build:
- NVIDIA GPU with CUDA drivers installed:
pip install torch torchaudio torchvision --index-url https://download.pytorch.org/whl/cu121
- Apple Silicon (MPS) - follow PyTorch MPS instructions (example):
pip install torch torchaudio torchvision --index-url https://download.pytorch.org/whl/mps
- AMD / ROCm: follow the official PyTorch ROCm install instructions for your distribution (see https://pytorch.org).
pip install torch torchvision torchaudio --index-url https://download.pytorch.org/whl/rocm7.1
⚠️ AMD GPU acceleration requires a ROCm-compatible CTranslate2 build. The standard
pip install ctranslate2only supports NVIDIA CUDA and CPU. Anchor will automatically detect this at startup and fall back to CPU if the standard build is installed. To enable full AMD GPU acceleration, you must build CTranslate2 with ROCm support from source — see the AMD CTranslate2 ROCm guide. Without it, Anchor still works correctly on CPU.
- CPU-only systems:
pip install torch torchaudio torchvision
Notes:
- Only install the CUDA wheel if you have an NVIDIA GPU and matching drivers; installing a GPU wheel on a CPU-only system can produce subtle runtime errors.
- If you encounter the
torchvision::nmserror, force-reinstall matching PyTorch/TorchVision wheels (see Troubleshooting below).
3. Finalize Dependencies (Critical)
Some libraries may downgrade during installation. Run this command to ensure the GPU translation engine is up to date and compatible with your drivers:
pip install --upgrade ctranslate2
⚠️ AMD ROCm users: Skip this step if you have built CTranslate2 from source with ROCm support. Running
pip install --upgrade ctranslate2will replace your custom build with the standard CUDA-only wheel, reverting GPU acceleration back to CPU.
🔌 API Mode (Subtitle Edit Integration)
Anchor can run as a local translation API server, compatible with Subtitle Edit's Auto-Translate feature. This lets you use Anchor's NLLB translation engine directly from within Subtitle Edit.
Start the API server with:
anchor --api
The server will idle with no VRAM usage and automatically load the translation model on the first request, unloading it again after the configured idle timeout.
⚙️ Configuration
The API server is configured via ~/.anchor/config.json:
"api_server": {
"host": "127.0.0.1",
"port": 5000,
"idle_timeout_seconds": 60
}
| Setting | Description |
|---|---|
host |
127.0.0.1 for local access only. Change to 0.0.0.0 to allow access from other machines on the network. |
port |
The port the API listens on. |
idle_timeout_seconds |
How long (in seconds) the model stays in VRAM after the last request before being unloaded. |
🖥️ Subtitle Edit Setup
- In Subtitle Edit, open Auto-translate (Video → Auto-translate).
- In the engine dropdown, select thammegowda-nllb-serve.
- Set the URL to
http://<host>:<port>/translate(e.g.http://192.168.1.50:5000/translateif accessing from another machine). - Select your source and target languages and click Translate.
⚠️ If running Anchor on a different machine than Subtitle Edit, make sure to set
hostto0.0.0.0in the config.
🔄 Running in the Background
Linux — using nohup:
nohup anchor --api > ~/.anchor/api.log 2>&1 &
echo $! > ~/.anchor/api.pid
To stop it:
kill $(cat ~/.anchor/api.pid)
Linux — as a systemd service (runs on boot):
First, find the full path to the anchor binary:
which anchor
Create /etc/systemd/system/anchor-api.service:
[Unit]
Description=Anchor Subtitle API
After=network.target
[Service]
User=YOUR_USERNAME
ExecStart=/home/YOUR_USERNAME/.local/bin/anchor --api
Restart=on-failure
RestartSec=10
[Install]
WantedBy=multi-user.target
Replace YOUR_USERNAME and the ExecStart path with the output from which anchor. Then enable it:
sudo systemctl daemon-reload
sudo systemctl enable --now anchor-api
Windows — using PowerShell:
Start-Process anchor --api -WindowStyle Hidden
How It Works - Under the Hood
A short summary: Anchor listens to the video with WhisperX (or the optional Parakeet engine), matches the subtitle's words to what was said, and places every line from those matches (phoneme alignment, global word alignment, drift correction and timeline interpolation) to produce millisecond-accurate subtitle sync.
- Transcription: WhisperX for high-quality transcripts + forced alignment, or Parakeet for accurate word times.
- Phoneme Alignment: Maps audio to phonemes for word-level timing.
- Global Alignment: Matches the script's words to the spoken words even when lines were added, cut or repeated, and tolerates names spelled differently, to find anchors.
- Drift Correction: Well-matched lines are trusted on their own; single-word matches must agree with the drift of the strong ones, and the drift trend is followed through long scenes and at both ends.
- Cleanup: Interpolation for lines without a match + overlap-fixer ("Zipper") for clean subtitles.
Full explanation (expand)
Many syncing tools rely on simple waveform matching or standard speech-to-text, which often results in "drift" (where subtitles slowly get out of sync) or fails when the actor changes a line.
The engine combines WhisperX with a multi-stage Elastic Alignment Algorithm. Here is what is happening during those processing steps and why it matters.
- Why WhisperX instead of Faster-Whisper? Standard faster-whisper is incredible at transcription, but it often "hallucinates" timestamps. It guesses roughly when a sentence started, often missing by 0.5 to 1.0 seconds.
WhisperX adds a crucial post-processing step called Forced Alignment.
The Difference: Instead of just listening for words, it maps the audio to specific Phonemes (the distinct units of sound, like the "t" in "cat").
The Result: The tool doesn't just know what was said; it identifies word-level timing precision down to the millisecond. This provides the bedrock for perfect sync.
- The Alignment Logic (Step-by-Step) Once transcription is complete, the custom syncing pipeline merges the provided script with the actual audio.
📏 Aligning Phonemes: The system maps the raw audio sounds to the text characters. This ensures that even if the actor speaks quickly or mumbles, the tool catches the exact moment the sound occurs.
📐 Global Alignment (e.g., 6153 vs 6063 words): Scripts rarely match the final audio perfectly. Actors add-lib, scenes get cut, or words are repeated.
Standard tools fail here because they look for a 1:1 match.
This tool performs a global alignment, mathematically calculating the best fit between the two datasets even when the word counts differ. Names the recogniser spells differently (it hears "Vanetti" for "Venetti") are matched to the script's spelling, while look-alike words ("three" and "these") are kept apart.
🔍 Drift Filter: Over a long video, audio timing can "drift" (often due to frame rate conversions like 23.976fps vs 24fps). A line whose words are mostly found, in order, is trusted as it is. A line matched by only a word or two must agree with the drift its well-matched neighbours show, so one stray word cannot drag a line off. Inside a long scene the drift keeps changing, so it is followed instead of averaged away.
⚓️ Valid Anchors (e.g., 618 Anchors): The system identifies "Anchors"-points of absolute certainty where the audio and text match perfectly with high confidence.
Rejection: It automatically discards "Outliers" (matches that seem statistically unlikely or erroneous), ensuring the timeline is pinned down only by high-quality data.
🔨 Reconstructing Timeline (Interpolation): Using the Anchors as fixed points, lines without a match of their own are placed between their neighbours' shifts, and every line keeps its original duration. This ensures that the dialogue between the perfect matches flows naturally and stays in sync.
🧹 Running The Zipper (Overlap Cleanup): Subtitle overlaps are messy and hard to read. "The Zipper" is a final polish pass that detects when two subtitle events collide. It trims the earlier line so there are at least 50 ms between them (and never shorter than 600 ms), resolving conflicts automatically.
Why use this over other tools? Most tools treat subtitles as a static block of text. This system treats them as a dynamic, elastic timeline. By using Phoneme-level anchoring combined with Drift Correction, the tool can sync messy, imperfect scripts to audio with a precision that manual matching simply cannot achieve.
🌍 Automatic Cross-Language Sync
Anchor 1.1+ can now synchronize subtitles even when they are in a different language than the audio (for example, English audio with Portuguese subtitles). This is done by creating a temporary "ghost" translation of your subtitles into the audio language, syncing that translation to the audio, and then applying the improved timestamps back to your original file.
How it works (expand)
-
Detection: Anchor detects a mismatch between the audio language and the subtitle file language (e.g., Audio: EN, Subtitle: PT).
-
Translation: Anchor uses a fast neural translation model (NLLB via CTranslate2) to create a temporary translated subtitle file in the audio language.
-
Sync: The temporary "ghost" translation is synchronized against the audio track using the normal alignment pipeline.
-
Restoration: The accurate timestamps are transferred back to your original subtitle file, preserving the original text while fixing timing.
The result is your original subtitle text, timed accurately to the foreign-language audio.
🧠 Translation Models
Anchor uses NLLB-200 (No Language Left Behind) via the ctranslate2 engine for high speed and low memory usage. You can override the automatic choice with the -t / --translation-model flag.
Note: The first time you use a translation model it will be downloaded automatically (approx. 1GB - 3.5GB depending on model). Models are cached locally for reuse.
Supported Translation Models
The following pre-built CTranslate2 models are supported and can be passed directly to -t:
JustFrederik/nllb-200-distilled-600M-ct2-int8OpenNMT/nllb-200-distilled-1.3B-ct2-int8OpenNMT/nllb-200-3.3B-ct2-int8
For convenience, Anchor also supports shorthand names that map to reasonable defaults:
| Shorthand | Model |
|---|---|
small |
JustFrederik/nllb-200-distilled-600M-ct2-int8 |
medium |
OpenNMT/nllb-200-distilled-1.3B-ct2-int8 |
large |
OpenNMT/nllb-200-3.3B-ct2-int8 |
Example usages:
anchor -t small
anchor --translation-model OpenNMT/nllb-200-1.3B-ct2-int8
And ensure you have enough disk space for model downloads.
⚡ Performance Test with model large-v3
These figures were measured on an earlier version, before the repair pass for suspicious Whisper segments and before the optional Parakeet engine. Current times differ, mainly with --asr; a 44-minute episode with Parakeet takes roughly 1.5 to 2.5 minutes including the repair of missed lines.
- GPU (NVIDIA RTX 2000E): synced a 44-minute episode in ~82 seconds.
- CPU (Intel i5-12600H): synced the same 44-minute episode in ~16 minutes.
- Notes: Results vary by hardware, drivers, and model precision. Haven't tested other devices extensively; it should work on AMD and Intel GPUs as well.
⚡ Performance Benchmarks
Tests performed on a 44-minute video file (English). With music and gun fire scenes. Hardware: NVIDIA RTX 2000E Ada Generation (16 GB)
| Model | Translation | Time | Speed | Anchors Found | User Score | Notes |
|---|---|---|---|---|---|---|
| Large-v3 | 3.3B | 98s | ~27x | 514 | 10 / 10 | Translation of 669 lines added 16s. |
| Large-v3 | N/A | 82s | ~32x | 600 | 10 / 10 | The gold standard for accuracy, but slower. |
| Medium.en | N/A | 62s | ~42x | 598 | 10 / 10 | Best Balance. Perfect sync, identical to Large-v3 but 25% faster. |
| Small.en | N/A | 44s | ~60x | 603 | 9.9 / 10 | Fastest usable. Twice as fast as Large-v3. Minor sync drift (<0.1s). |
| Base.en | N/A | 35s | ~75x | 585 | 9.7 / 10 | Very fast, but prone to drift on non-speech sounds (e.g., gunshots). |
📉 CPU Performance Benchmarks
Tests performed on a 44-minute video file (English). Hardware: 12th Gen Intel Core i5-12600H
| Model | Translation | Time | Speed | Anchors Found | User Score | Notes |
|---|---|---|---|---|---|---|
| Large-v3 | N/A | ~16 min | ~2.7x | 599 | 10 / 10 | Baseline. Too slow for daily use on CPU. |
| Medium.en | 1.3B | 12.5 min | ~3.5x | 518 | 10 / 10 | Translation of 669 lines added ~60s. |
| Medium.en | N/A | 11.5 min | ~3.8x | 595 | 10 / 10 | Accurate, but the extra 6-minute wait didn't add much value. |
| Small.en | N/A | 5.7 min | ~7.6x | 601 | 10 / 10 | 2x faster than Medium with better anchor detection. |
| Base.en | N/A | 4.1 min | ~11x | 579 | 9.7 / 10 | Decent, but not significantly better than Tiny to justify the extra time. |
| Tiny.en | N/A | 3.7 min | ~12x | 572 | 9.5 / 10 | Incredibly fast. Good overall sync, but slightly less precise start times (ms delay). |
📥 Subtitle Download
Automatically or manually download subtitles for a specific file or all files in the directory.
Available Providers:
- SubDL (If credentials set on the config file)
- OpenSubtitles (If credentials set on the config file)
- Addic7ed
- Podnapisi (Disabled by default. It slows down every subtitles search significantly without providing extra value. Can be enabled on the config file)
🎯 Smart Scoring System
When searching for subtitles, Anchor doesn't just blindly download the first result. It uses a weighted scoring engine to analyze your local video filename against the API results, bubbling the perfect match to the top of the list and burying incompatible files.
Here is a simplified breakdown of how the scoring works:
| Match Criteria | Score Impact | Description |
|---|---|---|
| Hash Match | + High |
The Holy Grail. The video file hash matches the subtitle hash exactly, guaranteeing perfect sync. |
| Source | + Medium |
Matches the source type (e.g., WEB, BluRay). |
| Release Group | + Medium |
Matches the specific ripper/group. |
| Cut | + Medium |
Matches the specific cut (e.g., Theatrical, Extended). |
| Network | + Medium |
Matches the specific network. |
| SDH/Forced Preference | +/- |
Awards or deducts points based on your prefer_sdh and prefer_forced configuration setting. |
| Wrong Episode | -100 |
Instant Rejection. If the season or episode numbers do not match perfectly, it is heavily penalized to prevent downloading the wrong file. |
🛠️ Troubleshooting
"Aborted" (Core Dump) on Launch
If the tool crashes instantly without an error message, it is a library path issue common on Linux. Run this command before starting anchor:
export LD_LIBRARY_PATH=$(python3 -c 'import os; import nvidia.cublas.lib; import nvidia.cudnn.lib; print(os.path.dirname(nvidia.cublas.lib.__file__) + ":" + os.path.dirname(nvidia.cudnn.lib.__file__))')
(Tip: Add the line above to your ~/.bashrc file to make it permanent.)
"Operator torchvision::nms does not exist"
This means you have a mismatch between PyTorch and TorchVision (usually one is CPU and one is GPU). Fix it by forcing a reinstall:
pip install --force-reinstall torch torchvision torchaudio --index-url https://download.pytorch.org/whl/cu121
"Numpy is not compatible"
If you see errors related to numpy (e.g., module 'numpy' has no attribute...), downgrade it to a stable version:
pip install "numpy<2.0" "pandas<2.0"
_curses missing on windows
pip install windows-curses
AMD GPU: Transcription/Translation Running on CPU Instead of GPU
Anchor detected your AMD GPU but is running on CPU. This is expected behaviour if the standard pip install ctranslate2 wheel is installed, as it has no ROCm support.
To verify which mode Anchor selected, check the startup output:
- ✅
ROCm-compatible CTranslate2 detected. GPU acceleration enabled.— GPU is active. - ⚠️
CTranslate2 has no ROCm support in this install. Falling back to CPU.— CPU fallback is active.
To enable GPU acceleration on AMD GPU, build CTranslate2 with ROCm from source:
# See full instructions at:
# https://rocm.blogs.amd.com/artificial-intelligence/ctranslate2/README.html
Additionally, on some distros (e.g. Fedora), torchaudio may fail to find ROCm libraries. Fix it by exporting:
export LD_LIBRARY_PATH=$(python3 -c 'import torch; import os; print(os.path.dirname(torch.__file__))')/lib:$LD_LIBRARY_PATH
(Add to ~/.bashrc to make it permanent.)
🎬 Usage
Navigate to the folder containing your subtitles and video files, then run:
anchor
Command line options
You can override the automatic hardware detection or control specific settings using flags:
| Option | Alias | Description |
|---|---|---|
| --audio-model | -a | Force a specific Whisper model (e.g., tiny, medium, large-v3-turbo). |
| --batch-size | -b | Manually set the batch size (e.g., 8, 16). Useful for optimizing VRAM usage. |
| --translation-model | -t | Force a specific translation model (overrides automatic selection). |
| --asr | Speech recognition engine for audio sync: auto (default), whisper or parakeet. See Parakeet engine below. |
|
| --subtitle | -s | Runs unattended sync on a single subtitle file (provide path to .srt, .ass, etc.) |
| --reference | -r | For unattended sync, provide reference subtitle file path for reference sync |
| --video | -v | For unattended sync, provide path to the video file if the script fails to auto-match |
| --overwrite | -o | Replace existing files. Without it Anchor never overwrites anything: a taken output name gets a counter (file.synced.1.srt). With it the original subtitle (for Embed and Strip, the original video) is replaced. |
| --backup | -B | With -o: keep a .bak copy of the original first (an older .bak is never replaced). |
| --help | -h | Show the help message and exit. |
| --version | -V | Show the version and exit. |
| --cpu | Force CPU execution, bypassing GPU detection. | |
| --check-hardware | Re-run hardware detection and refresh the cached profile. | |
| --api | Start the local translation API server (see API Mode). | |
| --check | With -s: only check whether the subtitle is in sync with its video (nothing is written; exit code 3 when it is not). See Sync Check below. |
|
| --fix | With --check: act on the advice without asking. Subtitles in sync are skipped, a suggested frame rate change is applied (after verifying it), otherwise Audio Sync runs. |
|
| --from-fps | For unattended frame rate change (with -s and --to-fps): the frame rate the subtitle was made for, e.g. 23.976. |
|
| --to-fps | For unattended frame rate change (with -s and --from-fps): the frame rate of your video, e.g. 25. |
|
| --language | -l | For unattended mode, provide the target language code (e.g. 'en', 'pt', 'fr') for translation or download |
| --download | -d | For unattended mode, automatically download subtitles. Provide -v with the video file path, or anchor downloads subtitles for all videos in the directory. |
| --missing | With -d: only download what is missing. A video that already has a subtitle for a requested language (<video>.<lang>*.srt next to it) is skipped for that language, and skipped entirely when none is left. |
Examples
Force a specific model:
anchor --audio-model large-v3-turbo
Force batch size (to prevent crashes or increase speed):
anchor --batch-size 8
Combine flags:
anchor -a medium -b 16
Run unattended sync:
anchor -s A.3.Minutes.Example.Video.en.srt -v A.3.Minutes.Example.Video.mkv
Run unattended sync with the Parakeet engine (installs it on first use):
anchor -s A.3.Minutes.Example.Video.en.srt -v A.3.Minutes.Example.Video.mkv --asr parakeet
Interactive reference sync shows your subtitles in two panes, targets on the left and references on the right. Pick files with
Space: each pick gets a number, and the target numbered 1 is synced to the reference numbered 1, and so on. / filters a pane by text
(for example .pt.), A picks everything shown, so a whole season is: / .pt. A, Right, / .en. A, Enter.
Run unattended reference sync:
anchor -s A.3.Minutes.Example.Video.en.srt -r A.3.Minutes.Example.Video.pt.srt
Change a subtitle's frame rate (for example a subtitle made for 23.976 fps that must match a 25 fps video):
anchor -s A.3.Minutes.Example.Video.en.srt --from-fps 23.976 --to-fps 25
From the menu (Change Frame Rate) you pick the subtitle files and then the From and To rates in a side-by-side picker. The result is saved next to the original and named after the new frame rate (A.3.Minutes.Example.Video.en.25fps.srt), so it never replaces the output of a sync. With -o the original is overwritten instead.
Anchor never overwrites a file it did not just create. If the output name is taken, a counter is added (Movie.en.synced.srt,
then Movie.en.synced.1.srt, .2. and so on); this covers every task, including the videos made by Embed, Strip and Burn-in
(Movie.embedded.mkv, Movie.stripped.mkv, Movie.burn.mkv) and .bak backups. Only -o replaces files: with it the original
subtitle (or, for Embed and Strip, the original video) is overwritten, and -B keeps a .bak copy first.
Check whether a subtitle is in sync (nothing is written):
anchor -s A.3.Minutes.Example.Video.en.srt -v A.3.Minutes.Example.Video.mkv --check
Run unattended translation:
anchor -s A.3.Minutes.Example.Video.en.srt -l pt
Run unattended download for all files:
anchor -d
Run unattended download for a specific file:
anchor -d -v A.3.Minutes.Example.Video.mkv
Run unattended download for all files for specific languages:
anchor -d -l en,fr
Download Portuguese subtitles only for the videos that do not have one yet:
anchor -d -l pt --missing
🩺 Sync Check
Menu entry 5, or anchor -s <subtitle> [-v <video>] --check. Anchor transcribes the audio, finds where each subtitle line is
spoken and reads how the offset behaves over the whole video. It changes nothing and writes no file. The verdict is one of:
| Verdict | Meaning | Suggested fix |
|---|---|---|
| In sync / mostly in sync | Small offset everywhere | none |
| Constant offset | One shift for the whole file, e.g. +3.1 s | shift, or Audio Sync |
| Drifting | Starts right (or not) and the offset grows steadily | Change Frame Rate when the slope matches a pair such as 25 to 23.976, otherwise Audio Sync |
| Out of sync (steps) | The offset changes in jumps: another cut, removed scenes, a partly synced file | Audio Sync or Reference Sync |
| Not comparable | Too few lines found in the speech: wrong video, language or a damaged file | check the pairing |
Run from the menu, it then offers what to do about the finding, using the transcription it just made: the suggested
frame rate change, Audio Sync, or nothing. A frame rate change is suggested only when exactly one frame rate pair explains the drift
(the video's own frame rate must be the target). Pairs that differ by 0.1%, like 23.976 to 25 and 24 to 25, cannot be told apart by
measuring, so then Anchor says so and recommends Audio Sync instead of guessing. A subtitle that does not belong to the video
(not comparable) gets no offer. Unattended (--check) it only reports. Add --fix to let it act on its own advice: anchor -s movie.en.srt -v movie.mkv --check --fix.
Subtitles in sync are skipped; a suggested frame rate change is applied only after it has been checked again against the same
transcription (if it does not bring the subtitle in sync, Audio Sync is performed instead); with no suggestion, Audio Sync is performed. A subtitle that does not belong
to the video is skipped and gives exit code 3. Output files are named as usual (.25fps.srt, .synced.srt), never overwriting unless -o is given.
A table shows the offset for eight equal parts of the video. Positive means the subtitle shows up early. It skips the
gap repair of an audio sync, so it is faster (about 35 s for a 44-minute episode with Parakeet; Whisper takes longer), and it uses
the same engine choice (--asr) and cross-language handling. In unattended mode the exit code is 3 when the subtitle is not in sync, so a script can react.
🦜 Parakeet engine (optional)
Audio sync can use NVIDIA's Parakeet speech recognition model (parakeet-tdt-0.6b-v3) instead of WhisperX to find where
the words are spoken. In our tests it placed cues more accurately and ran faster (about 4 s against 10 s for five
minutes of audio), but it only covers 25 European languages (including English, Portuguese, Spanish, French, German and
Italian) and it drops some short shouted lines in loud scenes. Anchor therefore keeps Whisper for every other language
and uses a short Whisper pass only where the subtitle has cues Parakeet did not hear.
--asr |
What happens |
|---|---|
auto (default) |
Uses Parakeet only if it is already installed and the audio language is supported. Otherwise Whisper. It never installs anything. |
parakeet |
Installs Parakeet on first use, then uses it for every supported file. Unsupported languages, or any Parakeet failure, fall back to Whisper for that file. |
whisper |
Never uses Parakeet. |
Using --asr parakeet for the first time creates an isolated environment in ~/.anchor/parakeet-venv (so it cannot
disturb PyTorch or WhisperX) and downloads the model on the first run. Expect about 3.4 GB of packages on an NVIDIA GPU
under Linux (mostly CUDA libraries), about 0.3 GB for the CPU build, plus about 3 GB for the model. On Windows, macOS and
AMD GPUs the CPU build is used (about 41 s per five minutes of audio). Delete ~/.anchor/parakeet-venv to remove it. The
--asr option only affects audio sync.
⚙️ Development
Run the tests (about 2 seconds, no GPU or models needed) with pip install -e ".[dev]" then python -m pytest. They pin the choices
that keep the sync accurate, so a failure means you changed one on purpose or by accident; see tests/README.md.
To modify the code locally:
git clone https://github.com/ellite/anchor-sub-sync.git
cd anchor-sub-sync
pip install -e .
🖼️ Screenshots
Contributors
❌ Uninstallation
If you installed Anchor via pip (GitHub), uninstall with:
pip uninstall anchor-sub-sync
If you used an editable install during development (pip install -e .), also remove the cloned repository directory and any virtual environment you created:
# from the project directory
deactivate # if in a venv
rm -rf venv/ # or the name of your virtualenv
rm -rf anchor-sub-sync/ # delete the cloned repo if desired
To remove model caches or large downloaded files, delete the relevant cache directories (varies by model/backends), for example:
rm -rf ~/.cache/whisper ~/.cache/whisperx
⚓ Links
Metadata
Release files for anchor-sub-sync 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| anchor_sub_sync-2.0.0.tar.gz | 171.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| anchor_sub_sync-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 326.0 kB
Release files / anchor_sub_sync-2.0.0.tar.gz
| Download URL | anchor_sub_sync-2.0.0.tar.gz |
|---|---|
| Size | 171.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8af1f5bdfac056df2a0e1f9391b95f62d80cedc2d8d1afdf31ce4ab876cb7c37
|
|
BLAKE2b-256 checksum How to use checksums |
27c7333a732b96ec81328d3c2362d7a40194fc6447a2934ef69ed698d6096cda
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Release files / anchor_sub_sync-2.0.0-py3-none-any.whl
| Download URL | anchor_sub_sync-2.0.0-py3-none-any.whl |
|---|---|
| Size | 154.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a09a599e0e4d62eec539a437019b49a18f7e2285fecfaece6b7347ac674914be
|
|
BLAKE2b-256 checksum How to use checksums |
4a4176d73f8b50058aee9a0ae5712fcbea4cb35cea50cd28d97198a13a703f18
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|