Repository navigation
Portrait and rotated videos now export upright. Update if your app imports clips recorded on an iPhone.
Fixed
-
Portrait and rotated videos export upright.
- What was wrong: a camera stores a portrait recording as landscape pixels plus a rotation tag (the track's
preferredTransform), and the front camera may add a mirror. kadr never read that tag, so every portrait iPhone clip exported and previewed sideways, stretched to fill the frame. - What changed: each clip is now turned upright before it is scaled to fill. This applies to plain chains, transitions (slide included), Tracks and free-floating clips, clips with transforms or keyframes, filters and compositors, reversed clips, and the preview player and thumbnails.
- Mixed orientations: clips with different orientations can share one video, and each keeps its own.
- What was wrong: a camera stores a portrait recording as landscape pixels plus a rotation tag (the track's
-
A plain clip no longer inherits the previous clip's transform. On the keyframe path, a clip with no transform that followed a transformed clip on the same track kept that transform. It now returns to its own layout.
Behaviour note
When every source is stored upright, nothing changes.
For a rotated source, kadr now builds a video composition so the rotation can be applied. If the preset can't encode it, the export throws KadrError.exportFailed instead of writing a passthrough copy, which would have been sideways. This is the same rule 1.1.1 introduced for transitions and crop.
Known gaps
- A custom
MultiInputCompositorstill receives source frames as stored, unrotated. VideoClip.metadata.resolutionreports the stored size, not the displayed size.
Both are tracked for a later release.
Full changelog: v1.1.1...v1.1.2