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
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
The text was updated successfully, but these errors were encountered:
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.
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.
Natron version
Natron 2.4
Operating system
Windows 10 Home (21H1)
System specs
No response
Did you install Natron using the official installer?
If you installed to a custom '(non-default)' location please include it here':'
No response
What were you trying to do?
What did you expect to happen? What happened instead?
Step-by-step reproduction instructions
Additional details
No response
The text was updated successfully, but these errors were encountered: