You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Photos taken on iPhone in heic format have arbitrary rotation as encoded in file. Image metadata (EXIF) contains orientation sensor info to enable display software to correct.
Viewing photo on device, in Windows, on web, or in OSX using a variety of image viewers all show correct orientation regardless of orientation of encoded image.
Photocloud does not seem to honor EXIF rotation data, hence photos are frequently incorrectly oriented (eg upside down or sideways). Affected photos need to be re-encoded to resolve.
Would be good if Photocloud could rotate photos properly before displaying.
PhotoCloud actually parses the EXIF data and rotates the photo accordingly if the EXIF data specifies a rotation. However, perhaps it's not working in your case for some reason. Which PhotoCloud version are you using please? Also, can you zip an image and attach it to this ticket please? I will then investigate the image myself.
@JohnFecko Which PhotoCloud version are you using please? Also, can you zip an image and attach it to this ticket please? I will then investigate the image myself.
Photos taken on iPhone in heic format have arbitrary rotation as encoded in file. Image metadata (EXIF) contains orientation sensor info to enable display software to correct.
Viewing photo on device, in Windows, on web, or in OSX using a variety of image viewers all show correct orientation regardless of orientation of encoded image.
Photocloud does not seem to honor EXIF rotation data, hence photos are frequently incorrectly oriented (eg upside down or sideways). Affected photos need to be re-encoded to resolve.
Would be good if Photocloud could rotate photos properly before displaying.
Thanks!
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: