-
-
Notifications
You must be signed in to change notification settings - Fork 668
-
-
Notifications
You must be signed in to change notification settings - Fork 668
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
Image orientation not detected in compose UI #1068
Comments
@muesli We need more information, what instance was this on? If it was on your instance, is horizon running? Are you sure the exif data contains the proper orientation? |
Sorry, should have mentioned that: this is on pixelfed.social. From EXIF: Also, Mastodon correctly identifies the image orientation. |
Can confirm. I should also note that using "rotate" in any image viewer in Windows and then rotating back makes Pixelfed.Social show correct orientation for uploaded photo. |
any news on this ? |
@dansup Does that mean this has gotten fixed recently? |
Just a heads up, tried it again and still not working on pixelfed.social. |
Can you provide an example of a photo that gets uploaded with the incorrect rotation? |
Great, of course GitHub fails at rotating the image, too 😆 Regardless of that, any photo viewer, instagram, flickr or Mastodon will correctly render the photo, respecting the provided EXIF Orientation information. Edit: Click the upper photo and your browser will also correctly render the original file. I guess GitHub just strips the EXIF headers from the thumbnail. |
OK, I think I managed to reproduce somewhat...
So that image is only incorrect on Github and in the compose UI. Weird... |
Well, what can I say? It seems to be working for me now, too, which makes me think pixelfed.social just got updated? Glad I provided a screenshot of what was happening for me until a few minutes ago on pixelfed.social in the comment above, otherwise I'd doubt my own sanity now 😆 |
It may also be a browser thing? https://phiffer.org/etc/exif-orientation-test/ |
Also a heads up: even when it's showing up correctly, the filters of the image show a stretched version of it. |
Also in Chrome I can get both the correct and incorrect rotations (depending on whether I downloaded the thumbnail or direct link). |
At any rate, I feel like this is happening only in the Compose UI so I've reopened it and changed the title for now. |
I gave Pixelfed a try today, set it up and it looks very promising. But this bug is the first "No-Go" yet which I've discovered with my first test post ;-) Uploaded 4 Photos directly from my iPhone, having my Pixelfed site open in Safari. The orientation is shown correctly on the iPhone! But on other Browsers (MAC/Safari, MAC/Chrome) one is correct, two are lying "on the side" as already shown here before, one is "head over" 180° wrong. It seems the orientation information seems not to be recognized by Pixelfed. Also when I click "edit" on my post in the browser view, I can't see the pictures, every picture space shows just "No Preview Available". |
I'm also having this problem. A raw picture from iPhone, and its orientation is detected by macOS QuickLook and Preview (plus other software). Uploading the image to Pixelfed fails to detect the correct orientation. The image is always turned 90 CCW. |
@dansup Unfortunately, this is not a solution. Here is the same image. The left one was rotated in Pixelfed. In this case I cannot rotate without cropping. 16:9 mode allows only horizontal rectange, not vertical, so that most of the image is lost. The closest option is 1:1 crop, but that's obviously not a solution. The image on the right was rotated using some Windows image viewer (any viewer, honestly). Please re-open the issue. ComposeUI is worse than rotating before upload, unfortunately. |
Trying to upload portrait photos, the orientation doesn't get correctly detected and they're displayed as landscape both in the "Create Post" dialog as well as on the feed once uploaded.
The text was updated successfully, but these errors were encountered: