You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There was a feature request some time ago that has been closed (#1045) which stacks the RAW *.dng file and the associated JPG when the two files share the same name. This feature is great, but recent Google camera apps will save the original with the following structure:
PXL_(date)_(time).RAW-01.COVER.jpg (this being the compressed JPEG file)
PXL_(date)_(time).RAW-02.ORIGINAL.dng (this being the raw file)
Describe the solution you'd like
I think the idea of "stacking" the raw and compressed images is great, that way I don't see two of each image, and I can share the JPG and keep the DNG around for editing without visual clutter.
Describe alternatives you've considered
Somehow convincing Google that naming the photo output this way is archaic and we should just share the entire filename except the extension.
Additional context
This is something likely currently unique to pixel phone users, but could see this being somehow committed upstream into AOSP and then being adopted across multiple vendors.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There was a feature request some time ago that has been closed (#1045) which stacks the RAW *.dng file and the associated JPG when the two files share the same name. This feature is great, but recent Google camera apps will save the original with the following structure:
Describe the solution you'd like
I think the idea of "stacking" the raw and compressed images is great, that way I don't see two of each image, and I can share the JPG and keep the DNG around for editing without visual clutter.
Describe alternatives you've considered
Somehow convincing Google that naming the photo output this way is archaic and we should just share the entire filename except the extension.
Additional context
This is something likely currently unique to pixel phone users, but could see this being somehow committed upstream into AOSP and then being adopted across multiple vendors.
The text was updated successfully, but these errors were encountered: