motmeister

I have a question related to the request for batch import. When a raw file is imported (.dng, .nef, etc), if you were to simply develop as is, will the resulting photo in the workflow lose any future developing capabilities? Consider the following hypothetical (future) workflow: 1. Batch import multiple raw files and automatically develop them as is and add an entry for each photo into the thumbnail view. 2. Using affinity, for each photo individually, enter the develop persona and tweak/save them to your taste. 3. Allow a new option of batch export of selected thumbnails as is, in other words, whatever the current developed/merged version of each selected photo is, that's what will get exported. Obviously there are going to be considerations of writing multiple files in one pass to the cloud, and perhaps ios11 may facilitate this in the new "file system". This seems to be a logical approach to a workflow, at least for me. If I take 100 photos in the field, then want to develop and save the results, this is what I've been doing. But one photo at a time is a very slow tedious process. I have also seen comments elsewhere about how the .afphoto file type isn't intended for storage, but that distinction isn't made for the desktop version. The Save and SaveAs functions there both save to .afphoto. The iPad in conjunction with a suitably-sized cloud or personal NAS (network attached storage) has plenty of room for storing .afphoto files. If you take that into consideration, why can't the thumbnails point to afphoto files? Is the affinity internal version of a photo on the iPad effectively an afphoto file? These are just questions... But consideration of the answers might jog a better batch approach loose.