Related Issues:
- Samsung: Initial support for Motion Photos (#439)
- Google: Initial support for Motion Photos (#1739)
- Metadata: Flag Samsung/Google Motion Photos as Live Photos (#2788)
Related Pull Requests:
- Live Photos: Add Support for Samsung Motion Photos (#3588)
- Samsung: Improved support for Motion Photos (#3660)
- Google: Initial support for Motion Photos (#3709)
- Google: Add support for Motion Photos (#3722)
Signed-off-by: Michael Mayer <michael@photoprism.app>
See issue comments for details. This also introduces a package constant
for the default ffmpeg command name and updates the tests.
Signed-off-by: Michael Mayer <michael@photoprism.app>
* Adds resolution limit
* Fixes 2 video filters and makes the env variable work
* Adds FFMPEG_RESOLUTION to all the docker-compose files
* Makes the resolution based on the longer side
* Fixes failing test
When I upgraded my phone to the Google Pixel 7, I noticed that the videos it takes have an extra video stream in them for their compressed HVC1 implementation. This means that all software transcoding of that format would fail, as it was transcoding the wrong video stream. This alteration fixed the issue for me, and will likely avoid video files with multiple video streams causing issues in the future.
Animated GIFs are transcoded to AVC because it is much smaller and
thus also suitable for long/large animations. In addition, this commit
adds support for more metadata fields such as frame rate, number of
frames, file capture timestamp (unix milliseconds), media type,
and software version. Support for SVG files can later be implemented in
a similar way.
