Happened to read a post from @uncoy about incorporating FastRawWiewer (FRV) in the workflow for Culling, Rating and Multi-image view & comparison, priced at about 25$
I would like to describe how do I intend to incorporate this tool in my workflow, hope that some of you experienced with this software could give some answers or even some useful tips for using more features of this software.
I intend to have both FRV and PL always opened and active together.
Starting with FRV for:
Rejecting and deleting bad images- I understood that the âdeletedâ items are actually saved in sub folder named: Rejected.
Rating images to be edited with Stars.
Opening the images in PL, directly from FRV (if possible)
Than in PL:
Editing an image and rating it with color label. So in the next time I use FRV, I can identify those Raw images that are already were edited in PL.
My questions are:
Can I directly from FRV, open the image in PL to be edited ? (Like âEdit inâ)
Are star ratings on FRV carried on to PL? (reflected immediately in PL)
Vise versa to 2) - does any change in star ratings on PL carried on to FRV? (reflected immediately in FRV)
Are Color Labels on FRV carried on to PL? (reflected immediately in PL)
Vise versa to 4) - does any change in Color Labels on PL carried on to FRV? (reflected immediately in FRV)
Multi-image view and comparison- I understood I can compare 2 or 4 images. Could it be a mix of Raw and Jpg (exported) images?
Any better idea how to incorporate FRV into the workflow
I know I can download the trial version and check it by myself, but I believe this topic may help some other users which were not familiar with this option like me.
Thanks
Everyone will have their own way of doing this. What has worked well for me over several years is to use FRV and PL in the following way:
All RAW images are copied from the card into a folder called ROLL
Use FRV to scan and cull images. Discarded images get moved from ROLL into REJECTS folder, those I want to process are moved into a SELECTS folder. This is all easily achieved in FRV.
Process the images in the SELECTS folder in Photolab.
Once an image is finished move it into a FINISHED folder by using PL and export/print from there.
In time and you are confident images in the REJECTS folder are not required then they can be deleted.
Using this process, you know that all photos have been reviewed if the ROLL folder is empty, only the SELCTS folder has images that need to be processed and that will be empty once all processing is completed.
So, I donât use stars or colours in my selection/culling process. Nor do I edit images from within FRV because I load all my images to be edited in PL from the SELECTS folder.
pretty sure you can but only used it with RAW files.
I stopped using it but for no other reason than I was too invested in LRc and the process I had already formed but having heard good things about FRV.
my intention is to drop LRc in the future so I will probably begin to use FRV so will also be keeping an eye on this thread.
So tried again and it is like that. Working in PL5. Working in PL6, but!! When you have a Project selected, or a group folder, it only changes to PL6, without opening the selected photo in FRW. If I have selected any folder in the finder structure, it works. No idea, if this is a bug, or intended.
P.S.
Even more strange. Just saw it now. If a project is selected in PL6 and you tell FRW to open it with PL6, the selected photo is added to the project. What a mess.
PhotoLab 6 saved the star rating in a .dop sidecar;
It also looked like PL6 wouldnât update the star rating in the .dop sidecar (checked using a code editor) until I closed the software, which looks like one of the ramifications of all the PL6 for Mac bugs with file persistence and syncing that have been reported since PL6 came out.
After configuring PL6 to read and write ratings from XMP files, I got:
for files that I had rated in PL6 before changing those settings, no amount of changing the rating in FRV or in the XMP file directly was picked up (as if some phantom value from PhotoLabâs internal database always had priority);
for other files, ratings and color labels set in FRV showed up in PL6;
ratings and color labels set in PL6 didnât show up in FRV, or they did so erratically.
Itâs not a very positive test so far.
Note that some of the issues might be specific to only the macOS version of PL6, or just to my configuration.
I will try to answer specific queries when I have more time but in the meantime, notwithstanding any âbugsâ and operating system variants (intentional or unintentional) the following is what should (I believe) happen.
Please note DOPs are typically updated in a 20 second time period (a DOP update cycle) if not before and always on shutdown (if working correctly).
The first thing to point out is that PL6 can (typically) detect metadata changes automatically when an external editor makes a change but the reaction will be one of the following:-
With AS(ON) (Auto Synchronisationâ or âMetadata synchronisationâ selected):-
External changes will be detected automatically in PL6 and reflected in the database, DOP and display.
Changes via PL6 will automatically be reflected in the image metadata (embedded for JPG, TIFF, DNG and sidecar for RAW)
With first encounter, metadata will be taken from the image (embedded or sidecar xmp etc.) except if a PL4 or earlier DOP is encountered when the âRatingâ (âRankâ) and âRotationâ are taken from the DOP and all other metadata is taken from the image!
With AS(OFF):-
External changes will be detected automatically in PL6 but no automatic updates will be made to the database or DOP and the display for the image will be marked with an âSâ icon. The update to the metadata in PL6 will only be made after the user selects a âRead from imageâ or selects the âSâ icon which will give the option to âRead from imageâ (or âwrite to imageâ) and overwrite any metadata in PL6 (or the image)!
No external changes to the image will be made automatically, they will only occur after the execution of a âWrite to imageâ.
On first encounter the following will happen
1 For a PL5 DOP on a PL5 release earlier than PL5.3.0 all metadata will be taken from the image
2 For a PL5 DOP on the PL5.3.0 and later releases all metadata will be taken from the PL5 DOP
3 For a PL6 DOP all metadata will be taken from the PL6 DOP (DOPs are typically not backwards compatible)
4 For a PL4 (or earlier) DOP the âRatingâ (âRankâ) and âRotationâ are taken from the PL4 (or earlier) DOP and all other metadata is taken from the image!
FRV:-
All changes made to the metadata on offer in FRV i.e. âRatingâ, Rotationâ (âOrientationâ) and âLabelâ will be made to the image metadata immediately.
No external changes made to the metadata are automatically detected by FRV, they will be detected after
1 A âReloadâ file is executed (on right mouse click)
2 A âReload file(s)â is executed when more than one file is selected
3 A âFilesâ/âReloadâ/âMetadata for x Filesâ or âReloadâ/âMetadata for â or âReload current folderâ is executed
Or so my tests on DxPL on Win 10 have shown and are still showing on PL6!
Rob, thanks very much for posting your workflow. I have been using colors to show what needs to be done, but itâs very easy to overlook those that need work! Your system only requires that I periodically check those folders.
I just need to integrate your workflow into my Photo Supreme DAM which should not be a problem.
Also I donât understand how people can properly rate their images prior to editing. Things can change a lot in that process which would necessitate re-rating. I always rate after all processing is done.
Putting those pieces-of-info together, Rob (and guessing that you probably move images from your FINISHED folder into some sort of archive location) - suggests to me youâre not making use of any of PLâs DAM features ⌠This is pretty much how I work too.
In which case, provided you have PL set-up to use sidecar/.dop files (PLâs default config) - and you store these with your archived RAWs, then you donât need the database at all ⌠and I find that makes things much easier / less complicated ⌠eg. no spurious Virtual Copies, etc.
I use a âwrapperâ to delete the database (and the cache) before invoking PL.
John, I have been using your wrapper with PL5 and not using the PL database has worked very well for me. Do you have an updated version of it for PL6? If so, I would sure appreciate your sharing it.
I only make limited use of the PL DAM. The very last activity before exporting images in my workflow is to assign keywords to the finished RAW file in PL.
I only use virtual copies on the rare occasion that I want a different edit of an image, such as a different crop, where I donât want to compromise what I have already done.
Much of this has been covered by other posts albeit with problems but
Yes, up to 10 programs can be configured and it is possible to pass multiple selected images to DxPL in one operation (on Win 10 certainly) from the same directory. In Win 10 they come is as a form of 'Project" referred to as an âExternal Selectionâ
IF AS(OFF) then a âFileâ/âMetadataâ/âRead from Imageâ for one or more images will cause the Metadata for all selected images to be refreshed (at the expense of any metadata changes in the DxPLDb being lost, if there were any such âpendingâ changes)
But with AS(OFF) the âConflict Resolutionâ icon will have been set when the change was detected by DxPL
Yes but definitely NO. FRV never updates directly only when requested (please see updates to the post identified above).
Exactly the same applies to colour labels as to star ratings as stated in 2 above.
Same as 3 above.
Yes, please see my post in DeepPrime XD doing nothing - #10 by BHAYT where I was comparing RAW with DeepPRIME JPG and (same) RAW with DeepPRIME XD JPG using the sharpness overlay to highlight noise!
I will leave this item to others who have a more ârigorousâ workflow than I do. I use FRV primarily to weed out images that are less sharp when I have multiple copies. It is extremely customisable and can be configured to move/rename DOPs as well as xmp sidecars when an image is consigned to one âbinâ or another! The various commands can be re-assigned to create your own cluster of keys to allow quick despatch of a file(and itâs hangers on) to one directory or another or simply skip to the next file!
@KameraD On Win 10 I converted the items I used in my last post to a project and with the project selected in âPhotoLibraryâ I passed a new image from FRV and it came over as a new âExternal Selectionâ (we had discussions about âExternal selectionsâ on Win 10 versus what happens on Mac some time ago)!
Repeated starting with PL6 in âCustomizeâ with project selected
Single image launch failed again blank âCustomizeâ screen but there on the âPhotoLibraryâ screen @sgospodarenko.
So @KameraD not quite such a disaster on Win10 PPL6 but not perfect either with single images it appears and I need to do more tests to see if there is an absolutely repeatable pattern I usually pass from FastStone Image Viewer but it can pass only one at a time successfully but will also test with XnViewMP.
Good I just did it for testing and trying to help the original poster, Doron. I normally never send picture via FRW to PL. I only use FRW for culling, rating and moving bad pics to rejected folder. The workflows here are so different, that some people never drive into problems, which makes others nuts
Thanks John for pointing me to this post. I didnât follow it, because this is not my workflow.
Besides this, I also donât have this âLive Reviewâ function. Live RĂźckblick should be the german translation. No matter what I try, doesnât show up. Also donât really understand, what it should be good for