I’ve edited photos of an event that I photographed and exported them to JPEG in full resolution using PhotoLab 8.
From these photos I made a selection and sent them to the event organizer.
Now I would like to use one photo of that small selection of JPEG images and export them again to a smaller size and with a watermark for usage on my social media.
In the PhotoLibrary tab I browse to the location where the selection of JPEG’s are stored. I select the image that I want to export and click the export button.
After a short while an icon with a red arrow appears next to the zoom slider. When I click the arrow a dialog appears (see image below).
Somehow the export reads information in de JPEG (or from somewhere else) where the original JPEG export in full size was stored. This in NOT the location of the JPEG of the selection that I was trying to export.
I closed PhotoLab, deleted the file OutputSettings.plist in that directory, started PhotoLab again and activated the Export dialog.
I noticed that the export options that I had added to the list of exports had disappeared. So that’s what the deleted file is for.
I added the export option again and was able to export the previously exported JPEG’s to smaller JPEG’s with watermark. Mission accomplished. Again, thanks.
But I don’t think this ‘hack’ is an option if run into this issue again on my next attempt to export a set of already exported JPEGs to smaller sizes JPEGs with a watermark.
To prevent this from happening I would have to make a backup of the file so I could restore the file after the export. But then I would also have to make the export that I would like to use again by hand each time I want or need to do this.
I understand that the RAW files should be the basis of all exports.
But sometimes I need to batch convert a smaller selection of the exported JPEGs to a smaller size and add a watermark to them at the same time.
It seems to me that this should be possible without the need to delete a file that holds all the export settings that I’ve created.
There should be no need for workarounds indeed, but sometimes the help to get the job done. For easier handling, I’d back up the files of a working configuration and compare those to the respective files, should the issue re-emerge. Then you can find out if the issue is caused by those files at all.
Anyways, you could address your issue to support.dxo.com and ask for assistance by creating a ticket, the template of which you’ll find at the lower end of said webpage.
