I’m using the latest RT 5.4 ( Version: 5.4 Branch: 5.4 Commit: a5e8eb9c8 Commit date: 2018-03-20), but experienced some issues that original metadata from a RAW (.NEF) file is NOT being saved in the output file.
E.g. I open a .NEF file, do some adjustments with RT in the Edit Window, click on ‘Save’ ([Ctrl S]), Choose ‘TIFF (16bit)’ as output format, ‘Save immediately’, and the file is saved.
Although essential camera metadata, lensdata, timestamp are saved, GPS and IPTC (partial) is NOT copied into the output file!
Also things like CopyrightFlag=True are changed into ‘unknown’.
Yes, I’ve checked the settings @ ‘Metadata copy mode’ = ‘Copy unchanged’; so I expect all the metadata to be written into the output file. Correct?
Just a simple question: is this issue going to be fixed any time soon, or do I have to wait for another 5.5 release?
Although I like the capabilities of RT 5.4 (as compared to Nikon’s ViewNX-i where in some cases noise reduction works better with RT), the presence of all metadata in my output files (TIFF) is essential in my personal workflow.
And coping & pasting the missing metadata every time by hand is very cumbersome.
I see RT 5.5 is near. I can’t wait…
But as regarding to the issue of not copying GPS and other IPTC metadata into the output file; is this issue now solved?
As in: does RT 5.5 commits all original metadata from a RAW file into an output file?
I’ve checked this:
?
I was just asking a question. Why so defensive?
Ok, so please enlighten me; what is the nature/goals of RT then, that is apparently forbidden to ask why metadata of a RAW file which is being converted, is partly stripped from its original parameters?
I’ve read " RawTherapee is a powerful, cross-platform program for developing digital photos in raw formats" and think it has already evolved into a powerful piece of software.
But… with still some bugs. (like this one). And I have reported this about 8 months ago.
Not defensive, just a little oblique. Basically, people do things on their free time. It isn’t good to nag. It will get looked at when it gets looked at. It is already an issue on Github with comments and a milestone. What more can you ask? Be patient.
if my answer sounds defensive, that might be because your post was quite aggressive, and maybe you didn’t realize that.
you are certainly free to ask questions. in fact, you did ask, and got an answer. twice. but apparently you didn’t like it, so you asked again with the tone of an annoyed customer (“deal breaker”, “no 5.5 for me” etc). so, I was reminding you that we have no customer, that we signed no deal, and that we will still sleep tonight even if 5.5 is not for you.
as @afre wrote, we are doing this in our free time,
mostly for fun. we try to take care of issues, and we appreciate users’ feedback, but there is no guarantee that things will be done.
or better: one key advantage of free software is that you can do something about it. if the issue is so critical for you that waiting is not an option, you can hire someone to do the work, for example. you don’t even have to contribute the code back, if you keep it for yourself.
so, I hope this clarifies my point. and one more thing:
again, thanks a lot for the report, but this also sounds like “annoyed customer”, just FYI.
how/where/when can I check if this issue is fixed?
