For those who were wondering: yes, iOS 7's EXIF data was to blame. I guess. Apple changed something that was causing Image::ExifTool to spit out "MakerNotes offsets may be incorrect!" and then refuse to write the rotated output file. But apparently this is an ignorable error (the proper term for which is "not an error"), and to tell ExifTool to ignore not-an-error errors, you have to specify IgnoreMinorErrors => 1, because hey, that's completely reasonable, right? Everything is awesome.
And the other interesting thing we have learned here is: if an image embedded in a web page has an EXIF rotation property, Safari on iOS will rotate it before displaying it, but Safari on OSX (and every other browser everywhere else) will display it unrotated.
Regardless of orientation the presentation is unfortunate as it reminds one of bacon served in a cocktail glass full of warm bacon fat or of that lesser known Maplethorpe piece, "Piss Bacon".
Comments are closed because this post is 9 years old.
Ceiling bacon?
You're in Australia?
Finest light fixture I've ever seen.
So - does Bacon really make EVERYTHING better?
Bacon 1, Gravity 3,083,724,872,678
iPhone autorotate error.
What?
˙ɹoɹɹǝ ǝʇɐʇoɹoʇnɐ ǝuoɥdı
It looks right on my phone's browser...
That's very weird! The thumbnail is displayed upside down on the page, but "view image" shows it right-side-up.
Ditto. Every other possible way of viewing the image shows it right-side up on my machine (Windows 7, Firefox & Chrome) but it's upside-down in situ.
Exiftool says "Orientation : Rotate 180". Image and its embeded thumbnail are upsidedown when I view them in feh under Linux.
iOS 7 must have fucked up the exif somehow because nothing on my server side script has changed in years. God dammit.
Happy SXSW!
Or your camera felt that it was upside down when you took the picture.
Or you're a pinhead.
For those who were wondering: yes, iOS 7's EXIF data was to blame. I guess. Apple changed something that was causing Image::ExifTool to spit out "MakerNotes offsets may be incorrect!" and then refuse to write the rotated output file. But apparently this is an ignorable error (the proper term for which is "not an error"), and to tell ExifTool to ignore not-an-error errors, you have to specify IgnoreMinorErrors => 1, because hey, that's completely reasonable, right? Everything is awesome.
And the other interesting thing we have learned here is: if an image embedded in a web page has an EXIF rotation property, Safari on iOS will rotate it before displaying it, but Safari on OSX (and every other browser everywhere else) will display it unrotated.
Regardless of orientation the presentation is unfortunate as it reminds one of bacon served in a cocktail glass full of warm bacon fat or of that lesser known Maplethorpe piece, "Piss Bacon".