forked from jywarren/image-sequencer
-
Notifications
You must be signed in to change notification settings - Fork 210
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
ability to write metadata into exif tags #169
Labels
Comments
GitMate.io thinks a possibly related issue is #118: Assorted improvements to be broken into separate issues. |
This would be pretty cool! |
Possible implementation modules: |
@jywarren can you please elaborate on this one a little? |
This was was just to try to come up with a standard namespace and
convention for the metadata generated by all the steps, and to write that
into a custom EXIF tag in the image, as you go. That way, there is some
"trace" of how the image was produced via the steps. Does that make sense?
Sort of an evidence trail, or showing your work.
…On Thu, Jun 28, 2018 at 10:50 AM Varun Gupta ***@***.***> wrote:
@jywarren <https://github.com/jywarren> can you please elaborate on this
one a little?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJzXHycVrt7eSjDAtU5sQO7IQmkzBks5uBO0UgaJpZM4SBG5j>
.
|
@jywarren Yeah I get this!! So we are embedding the sequence data in the image itself, right? |
yep!
…On Thu, Jun 28, 2018 at 2:44 PM Varun Gupta ***@***.***> wrote:
@jywarren <https://github.com/jywarren> Yeah I get this!! So we are
embedding the sequence data in the image itself, right?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#169 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABfJyglghYDs5wOp4dyEplSr9I2myepks5uBSPygaJpZM4SBG5j>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: