Open strugee opened 4 years ago
@strugee thanks for your report! That is a nice idea :)
@jancborchardt what would be the expected ux for this?
Yep, good point.
What we can do is simply show it as 1 picture in the overview, and show the preferred picture of the burst on click, but show both pictures in the slideshow.
To properly show burst mode photos, we could have a bar on the bottom displaying the other photos of that burst. But I'd say first is fixing the current strange display, and then afterwards we can look into how to do it better.
Anyone know what is in the field hrdp_makernote for images from Google Pixel 4a camera? Doesn't look like a Base64 encoded string?
@Bun-Bun this issue is about Nextcloud Photos, the web app, and has nothing to do with uploads.
Is your feature request related to a problem? Please describe.
The Google Camera app on my Pixel 3a XL, in certain circumstances, will generate photo "bursts". These are saved in a folder named after the image and with the photos in the burst inside the folder. For example:
As you can perhaps guess from the name, this burst was generated because I took a photo in portrait mode. One of them is the unprocessed original, and one of them has the portrait mode effect applied.
I upload these folders as-is to my Nextcloud, but the Photos app doesn't handle them very intelligently: they are treated as regular folders. This makes it annoying to browse folders with these burst subdirectories in them, because they're shown like regular folders.
I'm not sure what other times Google Photos generates these burst subdirectories.
Describe the solution you'd like
Ideally, Photos would recognize that the subdirectory was a burst, and it would display it as one photo. When opened, the interface would make it clear somehow that there are two alternative versions of the photo, and allow the user to switch between which one they're looking at. Note that this is how the Google Photos app on Android works; I assume the web version works the same way.
Describe alternatives you've considered
None thus far.
Additional context
I figured the data that Google Photos uses must be encoded in EXIF or IPTC metadata or something like that, so I did some digging. exiftool(1) dumps the following for the unprocessed photo (note: I filtered out a property called "Hdrp makernote" which was the same for both images and spewed multiple screenfuls of seemingly random characters):
I diff'd this output with the output of exittool(1) when run on the processed, portrait-mode image and here's what I got (filtering out some boring differences like file modification time as well as a property called "Cameras Camera Depth Map Focal Table" that just spewed a lot of random characters):
It appears that the "Burst ID"/"Camera Burst ID" (not sure how these are different) is a UUID that we can use to tie these photos together, i.e. determine that they were part of the same burst. "Special Type ID" seems to indicate that the photo is a portrait-mode photo. The Google Photos app lets you set which of the two alternative photos in the burst is the "primary" photo, so my guess is that the presence of "Burst Primary: 1" indicates that, but I need to do more testing to be sure.