Releases: smacke/ffsubsync
Releases · smacke/ffsubsync
0.4.26
What's Changed
- Allow progress to work for multiple syncs even if alignment fails for a particular input;
- Allow specifying ffmpeg exe path using --ffmpeg-path;
- Updates for Python 3.12;
- fix: don't report sync as successful if best score is in negatives by @ajitid in #186
- Turn on Audio Sync for audio extraction process by @dvh312 in #192
New Contributors
Full Changelog: 0.4.25...0.4.26
0.4.22
This release includes miscellaneous sync improvements, compatibility fixes, and other bugfixes. It also includes functionality for using a new algorithm, called "golden section search", for inferring the framerate ratio between the reference and input subtitles. To use, pass the --gss
flag -- it may help in some cases where subtitles are still out of sync, if the issue is that the scaling is different from the predefined ratios ffsubsync tries.
0.4.11
- Misc sync improvements:
- Have webrtcvad use '0' as the non speech label instead of 0.5;
- Allow the vad non speech label to be specified via the --non-speech-label command line parameter;
- Don't try to infer framerate ratio based on length between first and last speech frames for non-subtitle speech detection;
0.4.10
- Lots of improvements from PRs submitted by @alucryd (big thanks!):
- Retain ASS styles;
- Support syncing several subs against the same ref via --overwrite-input flag;
- Add --apply-offset-seconds postprocess option to shift alignment by prespecified amount;
- Filter out metadata in subtitles when extracting speech;
- Add experimental --golden-section-search over framerate ratio (off by default);
- Try to improve sync by inferring framerate ratio based on relative duration of synced vs unsynced;
0.4.9
- Make default offset seconds 60 and enforce during alignment as opposed to throwing away alignments with > max_offset_seconds;
- Add experimental section for using golden section search to find framerate ratio;
- Restore ability to read stdin and write stdout after buggy permissions check;
- Exceptions that occur during syncing were mistakenly suppressed; this is now fixed;