feat(server): crop and rotate

[zdimension]

This PR adds support for using the Orientation EXIF field from the sidecar (which can be modified without touching the original file).

It also adds two actions to the web viewer that "demo" that feature:

Issues:

• the web viewer displays images in two ways: as thumbnails, and through the zooming component. The zooming component doesn't seem to take the EXIF orientation in account, so the image displays in its "raw" orientation when one zooms.
  • people on the Discord server have suggested to also render the "edited" version of the original image, in original resolution. This would mean images with EXIF orientation would have an original resolution "thumbnail" render that would be used for viewing. This would make it easy to display images without having to constantly process the rotation client-side.
• after changing the rotation, the thumbnail needs to be refreshed. This is currently done by triggering a thumbnail regeneration task and refreshing the img tag's source field after 500 milliseconds.

[michelheusschen]

Please revert this change

[zdimension]

it seems like on main this points to an outdated commit: e2e/test-assets points to https://github.com/immich-app/test-assets/tree/39f25a96f13f743c96cdb7c6d93b031fcb61b83c but the commit hash has changed when the PR was merged

[michelheusschen]

We rely on the checksum field to detect changes in the thumbnail and bypass the cache. Refreshing based on the time might work in this component, but it will cause caching issues everywhere else. Mobile might have a similar caching issue.

[zdimension]

I agree that it's not pretty; but @jrasm91 told me on Discord the ideal way would through a web socket event but that since we don't currently have one for thumbnail generation, refreshing like that was a good enough hack until it's done.

How would you do it?

[danieldietzler]

I'm personally fine just having a workaround here and then we'll hopefully have websocket events soon

[michelheusschen]

I don't see how a websocket event will solve caching issues in other components/pages. We include the checksum for thumbnail requests, but the checksum doesn't change in this case so the cached thumbnail is still used.

[jrasm91]

Maybe we should use a counter/nonce instead of the checksum

[danieldietzler]

Oh sorry now I get your point. You're absolutely right, yes.

[zdimension]

so, uh, sorry, but what should I change here?

[danieldietzler]

The code looks very good to me