Hi Mike,

not sure wether this is a bug or a feature wish:
I just noted that copying my good old Nikon D1 NEF images with my beloved FlashPipe (to get them renamed and stored in a date-oriented structure) the date is picked from the 'last modified' entry instead of from the 'picture taken' date of the file properties. This leads to spreading all post-processed versions all over the place (i.e. date folder structure) instead of putting them together with their original versions. The 'picture taken' date (as shown e.g. by Explorer) is definitely present in the work copies.
Could you change that behavior in a way that if a 'picture taken' date is available then this is used for the target path instead of the 'last modified' date?

Let me know what you think - in this case I would wait for the fix instead of manually correcting things.

Best regards
Peter

Hi Mike,

As of v.2010.118: One feature request just popped up while I prepared a bunch of images for the Web:
Apparently the JPEG settings from Develop are just taken over by the Web size creation. This leads to inappropriately large web files (at given target pixel size) when you use a good quality setting for Develop (which I do).
So my request is a separate JPEG quality setting for the Web file creation - I just cut down the Web size to one quarter for the same image size by changing my Develop JPEG setting from 98 to 80 - and must make sure that I do not forget to reset it before the next 'real' Develop job ...

Thanks for listening 

Peter