Read/Save Adobe-style exposure and white balance

Submitted by Richard Yorke on Sun, 08/31/2014 - 07:32
Forums: 
General discussion

Thanks for the new 0.9.3 Beta which has some good improvements :-) However, now that it is not setting pictures to an earlier process version, I see I still have a problem of it changing exposure and white balance values so that I have to select overwrite or import changed meta data settings for pictures already in Lightroom. I can stop this by unticking the 2 boxes to Read/Save Adobe-style exposure and white balance, but I can't select read not save. If I have already got the image in Lightroom I don't want its settings to be changed by external programs, but if the Lightroom settings can be read and so improve the appearance of the image in FRV I would like to be able to do that so 3 options would be ideal, Read/Save, Read/Not Save and Neither Read or Save.
That is for files already in Lightroom, if the file has not been imported into Lightroom it would be good if the settings could be carried over.

lexa

Sun, 08/31/2014 - 10:38

Thank you for the suggestion. Added to TODO list.

BTW, we cannot determine, have you imported the file into lightroom, or not, so you'll need to change Read/Save options yourself.

--

Alex Tutubalin/FastRawViewer team

Richard Yorke

Sat, 09/06/2014 - 07:56

Yes, I had envisaged the problem that you would not automatically know if the picture had been edited in Lightroom, which was why I had suggested the three options to be selected manually. However, after further thoughts on the subject, it might be worth having a temporary internal flag that is set if an XMP file is present, then when an image is closed an XMP file is written if there was not one to start with, when the Read/Not Save option was set. This would then ensure that if an image was opened a second time there would be a starting point based on all the changes made the first time round, but that no previous XMP was overwritten, so no data destroyed. The Neither Read or Save option would still not save under any circumstances, and so would stop unwanted XMP files being written at any point. The option might then be better named Read/Not over-write.
Another tweak that you could apply connected with this is the A key, not just toggling between, Exposure correction or not, but to have 3 options, Nothing, Exposure correction read from existing XMP, exposure correction with current FRV adjustments
 

lexa

Sat, 09/06/2014 - 09:44

Things *already* too complex with XMP WB/Exposure handling (because FRV stores own WB/exposure data in XMP, not only Adobe's format).

Separate settings for Ignore, Read, Read and Write are simple enough for average user.

If we will set 'some internal flag' for session time, FRV's behaviour will change for different session pattern (Open file - go to next - return to previous will be differ from 'open file, close program, open file again).

If we will keep this flag in XMP file, it will be out of sync if we open file in FRV, close FRV, open file in Adobe, adjust, close, open file in FRV.

So, separate settings for 'read adobe's data/ write adobe-compatible data' is simple and unerstandable enough. Anything more complex is too complex for average user (and for FRV developers).

Sidenote: generally it is possible to have *four* different set of Exposure/WB settings. Two in XMP sidecar file (in FRV format and in Adobe format), an two in XMP block embedded in RAW file.

--

Alex Tutubalin/FastRawViewer team

Richard Yorke

Sat, 09/06/2014 - 10:32

Enough said! I am just throwing possible ideas at you, in case they are easy to implement or point you in a direction you had not thought of. They are not necessarily things I feel should be done. Simplicity and speed still comes top of my list! My next big item on the wish list, that you have already said you will look into later, is keywording :-)

lexa

Sat, 09/06/2014 - 11:03

Yes, keywording in Adobe-compatible format is in TODO list. No exact schedule yet.

--

Alex Tutubalin/FastRawViewer team

Add new comment