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

(Bug): Write Node with "override" enabled only modifies existing files #666

Closed
8 of 11 tasks
sihagen opened this issue Sep 16, 2021 · 4 comments
Closed
8 of 11 tasks
Assignees
Labels
type:bug Something isn't working

Comments

@sihagen
Copy link

sihagen commented Sep 16, 2021

  • I'm using the latest version of Natron (not required but recommended)
  • I've restarted Natron and the issue persists
  • I've run Natron via the command line and the issue persists
  • I've followed the contributing guidelines to the best of my understanding
  • My issue is not on the issue tracker and is not a duplicate of a forum thread
  • This bug is reproducible
  • This issue is not a feature request or a pull request

Natron version

Natron 2.4

Operating system

Windows 10 Home (21H1)

System specs

No response

Did you install Natron using the official installer?

  • Yes, I used the official installer
  • No, I installed from a binary archive
  • No, I compiled Natron from sources
  • No, I installed Natron via another method

If you installed to a custom '(non-default)' location please include it here':'

No response

What were you trying to do?

When enabling the overwrite option in a write node, exisiting files (e.g. in an image sequence) are not 'overwritten'. Rather the files are changed and their metadata is partially altered, but for e.g. not the date of creation.

What did you expect to happen? What happened instead?

I expect Natron to replace the existing files with new ones (including new date of creation etc.).

Step-by-step reproduction instructions

1. Render a single file or an image sequence
2. Re-render the project. Now the date of creation remains the same, even though it is a new file with a (propably) new content.

Additional details

No response

@sihagen sihagen added the type:bug Something isn't working label Sep 16, 2021
@devernay
Copy link
Member

To be more precise, we are talking about the filesystem creation date (as shown by ls -lU on Linux).
Modification date is OK, and the "capDate" OpenEXR metadata (aka DateTimeOriginal) is updated correctly.

@rodlie
Copy link
Contributor

rodlie commented Sep 23, 2021

Will test on Windows now (for some reason I didn't see this issue).

@rodlie
Copy link
Contributor

rodlie commented Sep 23, 2021

just tested png/tiff/exr on Windows 10. The modification date is changed, the creation date is untouched. Everything seems fine to me, we overwrite the file not recreate it.

@devernay
Copy link
Member

I'm working on it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants