Equirectangular 360 photos seem to be rendered as standard (large) images. There are several examples of content-sensitive handling for this type of image on the web. Facebook, for example, creates a continuously 2d-scrollable view-port onto the wrapped image, and allows an initial viewport to be specified on upload. Can we replicate such an interface?
https://pannellum.org/ is one example of a WebGL-based viewer seemingly designed for webapp integration.
Given local caching of images, maybe we can do an entirely local decision for when to swap in the image viewer, based on exif data?
Is there an obvious way to add initial-viewport metadata to a toot with 360 media? Appending polar coordinates to the URL?
[x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[ ] This bug happens on a tagged release and not on master (If you're a user, don't worry about this).
I don't know the answer to this question, but interested to have expert chime in -- does the switch from imagemagick to VIPS make this any easier/harder?
Equirectangular 360 photos seem to be rendered as standard (large) images. There are several examples of content-sensitive handling for this type of image on the web. Facebook, for example, creates a continuously 2d-scrollable view-port onto the wrapped image, and allows an initial viewport to be specified on upload. Can we replicate such an interface?
https://pannellum.org/ is one example of a WebGL-based viewer seemingly designed for webapp integration.
Given local caching of images, maybe we can do an entirely local decision for when to swap in the image viewer, based on exif data?
Is there an obvious way to add initial-viewport metadata to a toot with 360 media? Appending polar coordinates to the URL?
[x] I searched or browsed the repo’s other issues to ensure this is not a duplicate.
[ ] This bug happens on a tagged release and not on
master
(If you're a user, don't worry about this).