polysync
Multicam audio sync + director-style auto-edit. Align N recordings of the same event by audio cross-correlation, then cut or picture-in-picture them into a single MP4 — driven entirely by who's talking.
What makes it different from "yet another sync tool":
- Reversible sidecars, never re-encodes the originals. Sync writes a tiny
<input>.sync.jsonnext to each file holding a single offset. A 75-min 4K 3-camera shoot is 250+ GB; baking offsets into re-encoded copies would double that and lose quality. Downstream applies the offset withffmpeg -itsoffsetat consume time. Originals are touched read-only, always. - Envelope cross-correlation, not raw waveform. Matches the log-energy envelope, which both mics hear regardless of their frequency response — robust even when a second camera's on-board mic sounds nothing like the main one.
- Clock-drift aware. Cheap recorders drift 5–50 ppm; polysync fits the drift across the recording and reports it separately, so long-form lip-sync can correct it while camera-cut editing can ignore it.
- Handles the messy real cases. Auto-picks the loudest audio track (pro cameras often leave track 1 dead), partial-coverage clips that only span part of the session, and independent verification of the result.
Install
pip install polysync # once published
# or, from a checkout:
pip install -e ".[dev]"
Requires Python ≥ 3.9 and ffmpeg / ffprobe on your PATH
(brew install ffmpeg, apt install ffmpeg, …). Python deps: numpy, scipy.
Quickstart
# 1. Sync each angle to a reference camera (writes <file>.sync.json sidecars)
polysync sync CAM_A.mp4 CAM_B.mxf
polysync sync CAM_A.mp4 CAM_C.mxf
# 2. (optional) Verify the alignment — re-checks residual independently
polysync verify CAM_A.mp4 CAM_B.mxf CAM_B.mxf.sync.json
# 3. Build an auto-edit decision list (who's on screen each second)
polysync edit CAM_A.mp4 CAM_B.mxf CAM_C.mxf --out edl.json
# 4. Render — hard cuts, or with a picture-in-picture inset
polysync render-cuts edl.json --out final.mp4
polysync render-pip edl.json --out final.mp4 --pip bottom-right
A clip that only covers part of the session (a Riverside / phone / lavalier recording that started mid-way):
polysync sync REFERENCE.mp4 PARTIAL.m4a --partial
How it consumes the sidecar
delta_seconds is the source's t=0 in the reference's timeline (positive =
source starts later). To align by hand:
ffmpeg -itsoffset $(jq -r .delta_seconds CAM_B.mxf.sync.json) -i CAM_B.mxf \
-i CAM_A.mp4 -filter_complex "[0:v][1:v]hstack" out.mp4
The edit / render-* commands read every sidecar automatically.
Python API
from polysync import compute_sync # pure-numpy core, unit-testable
from polysync.sync import sync_files # file → sidecar
from polysync.verify import verify_files
from polysync.edit import build_edl
Status
Beta (0.1). Sync + verify are battle-tested on real Sony FX3/FX6 multicam interview footage; the auto-edit is audio-energy-driven (no face detection). Issues and PRs welcome.
License
MIT © 王建硕 (Jian Shuo Wang)
Metadata
Release files for polysync 0.3.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 | Provenance | |
|---|---|---|---|---|
| polysync-0.3.0.tar.gz | 26.5 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| polysync-0.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 56.1 kB
Release files / polysync-0.3.0.tar.gz
| Download URL | polysync-0.3.0.tar.gz |
|---|---|
| Size | 26.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1aa9f249fb188355c784c367a9030ceb509113c0b6309a03e3eb2f40eadfa7b7
|
|
BLAKE2b-256 checksum How to use checksums |
14b1774391ae5738abc8f69017cd3e2fbd71a84ebfa3a3e2a5b402b9da8d3ab0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 25, 2026.
Transparency logRelease files / polysync-0.3.0-py3-none-any.whl
| Download URL | polysync-0.3.0-py3-none-any.whl |
|---|---|
| Size | 29.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
266a28575b53687cbd95e867982ae5b657c8f677bd7893a688c9bfbcf38557a3
|
|
BLAKE2b-256 checksum How to use checksums |
7797f30a417b5b8347972c3f08c7b04fc54d3d921a81e70ca5726be19724683d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 25, 2026.
Transparency logSecurity for polysync 0.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for polysync-0.3.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 25, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.