#IRIDIENT DEVELOPER VS ON1 MAC OS#
#IRIDIENT DEVELOPER VS ON1 SOFTWARE#

If I can get away with just cropping a JPG I may do that. I used to develop everything, now I try to be more pragmatic. Since I shoot Fuji the jpg are usually pretty good to begin with and I may share them with people to give them something to look at while I do the real interpretation. At this point I may choose to move some images back and forth between Captures/Selects This is where I do my critical thinking about the images in Selects I also find that my opinion changes as time goes by so I usually wait to use stars or colors I find there is no point in tagging images that do not make the cut Instead I just make 3 piles: Good(Selects), Undecided(Capture), Rejects (Trash)Ĥ) Further tagging is only done on the select using PM

#IRIDIENT DEVELOPER VS ON1 SOFTWARE#

The issue is how do you make all the different software happy since they are not interoperable.įor example if you use both Adobe and C1P you have to make a decision which to adopt. I am fully aware I could use stars or colors to do this in PM/FRV/C1P as they all support it to various degree. Once no further images are left at the folder root I know they all have been evaluated. Destination: /Trash/*.jpg, *.raf, *.xmp Here are further details of what I have come up with regards to integrating C1P with PM and FRV. I'm looking forward to learning what others do. What are you favourite folder structures and do you start with PM then C1P or the other way around. I'm curious how others use PM with C1P Sessions. I suspect this is unlikely to happen which is why I am looking into C1P right now. If PM was able to implement a plugin architecture allowing for Luminary's Flex to be added to the mix it would be a very interesting combination.Īffinity Photo could then be used for further refinement which I believe could make for a wining combination. These are not on par and do not entirely serve the same purpose but they are options. This is what got me looking into C1P, Luminar and Affinity Photo.

I am also concerned that the UI has not evolved over the years and wonder just how long will the software be supported. I am not knocking the work of Iridient Developer developers but as someone who writes software for a living it somewhat get's under my skin. I currently have licences for PM6, FRV and Iridient Developer.Īlthough Iridient Developer has excellent conversions is it particularly slow to operate with poor UX design. I use FRV to critically inspect raw files and typically do a first culling pass from my local library where images get moved into _Selected/_Rejected folders. I use PM to ingest, tag images with metadata and move/copy images around based on specific folder structure needs. The intent of this post is to allow me to compare workflow notes with fellow users of Photo Mechanic, FastRawViewer and consider various options: Ideally it should be possible to replace workflow elements without having to start over while in practice this may not be possible. Moving a library from one piece of software to another is fairly time consuming effort and typically involves loosing something along the way which is why I would prefer to keep concerns separate and use different software for different purposes, basically adopt more of a folder centric view of a library. In the past I used Adobe software while I am less inclined to do so lately.

#IRIDIENT DEVELOPER VS ON1 MAC OS#

My current platform is Mac OS based and over the years I have used various software to manage my library, develop raw files and edit developed images further.

Iridient developer vs on1