-
-
Notifications
You must be signed in to change notification settings - Fork 116
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't delete live/motion photos data #158
Comments
Seems like this live/motion data is simply added at the end of the JPEG image, and not part of the image.
jpegoptim 'decodes' the JPEG file and then rebuilds in from scratch, so extra data added after the end of the image will be "lost". I supposed it would be possible to add option to tell jpegoptim to preserve any "extraneous" data after end of the JPEG image in the input file... |
I guess the new Ultra HDR Image format form Google is the next candidate, The extentional HDR data will be lost after the optimisation processing done by jpegoptim, because the additional data does not conform to the original JPEG specifications. |
Hi! As my photo gallery has grown to 40GB, i wanted to finally run
jpegoptim
over it to shrink it just a bitTook a random photo, and results were good... 3.2mb -> 1.4mb .... too good...
I realised that many of my photos have live/motion data... and I want this! But jpegoptim seems to strip it away
Here is an example:
Try to download it and view it in Google Photos (i hope github doesn't compress this), and then do same after jpegoptim (desktop-web https://photos.google.com will also work!)
Please make it not strip it away 🙏
The text was updated successfully, but these errors were encountered: