Skip to content
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

Store applied style name(s) in XMP file #13608

Closed
kanwarplaha opened this issue Feb 11, 2023 · 5 comments
Closed

Store applied style name(s) in XMP file #13608

kanwarplaha opened this issue Feb 11, 2023 · 5 comments

Comments

@kanwarplaha
Copy link

Is your feature request related to a problem? Please describe.

I have several styles that I apply to the photos, often multiple. However, this information is lost when the same edited image is retrieved later. As of now, I have to remember and add the applied styles in metadata editor. This does not scale and it cumbersome. Same with tags.

Describe the solution you'd like

Applied styles be added/stored in XMP file to allow recall of what styles caused a particular look of an image from the past.

Alternatives

Metadata editor - works but does not scale
Tagging - same as metadata editor

Additional context

None.

@pehar1
Copy link

pehar1 commented Feb 11, 2023

Tags are already saved in xmp sidecar files. Saving style names IMO is not a good idea. In most cases styles represent only the starting point for further modifications and many modules can be applied subsequently, so the look may be very different.

@kanwarplaha
Copy link
Author

kanwarplaha commented Feb 12, 2023 via email

@pehar1
Copy link

pehar1 commented Feb 12, 2023

The xmp sidecar file contains the full history (all modules with all settings). Adding style names means adding redundand information (best case) or inconsistent information (if module parameters have been changed afterwards). Also styles can be modified or even deleted after you applied them. In the latter case the stylename entry would point to something which does not exist.

@github-actions
Copy link

This issue has been marked as stale due to inactivity for the last 60 days. It will be automatically closed in 300 days if no update occurs. Please check if the master branch has fixed it and report again or close the issue.

Copy link

github-actions bot commented Feb 9, 2024

This issue was closed because it has been inactive for 300 days since being marked as stale. Please check if the newest release or nightly build has it fixed. Please, create a new issue if the issue is not fixed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants