Automated release: version and notes generated from pull requests merged since 2.10.6.
Fixed
- A rotated file is measured and composited at the size it is shown. ffmpeg applies a 90° or 270° display rotation before the filter graph, and
probe.pystill reports the stored width and height.overlay.py --scale-percenttook half of that stored width (a 50% logo on a 320×180 phone file shown as 180×320 was 160 px, almost the whole frame).--platformmargins used the same stored size, so TikTok's 14% right margin was 14% of the landscape width.broll.pyscaled the cutaway to the stored frame and clipped it onto the portrait one.cropdetect.pyreportedsource_width/source_heightas the stored size while the rectangle was in the displayed frame (a 176×320 crop against a 320×180 source).look.py --safewarned that a 9:16 phone file stored as 16:9 was the wrong shape for TikTok. The displayed size is what those tools use now. - The colour-emoji probe survives a path that contains a colon, and a Windows font path is not split on the drive letter.
subtitles=C:/...is read as the optionCplus a following option, so the probe that decides whether libass can draw colour emoji failed on every Windows temp directory and reported the capability unknown. The samefc-listlineC:\Windows\Fonts\seguiemj.ttf: Segoe UI Emojiwas split on the first colon, so the font file wasCand a monochrome fallback was never found. The probe now uses the filter-path escape, and the listing is split on colon-space, which is the separator fontconfig prints. - fix: measure rotated frames at the size they are shown (#344)
What's Changed
- fix: measure rotated frames at the displayed size, and escape emoji probe paths by @kajisho5 in #344
Full Changelog: v2.10.6...v2.10.7