That is what I am thinking also, Lars. So this really becomes important for folks to think about and choose, as trying to use both systems is a huge amount of work and extra storage space. This was one of the reasons I did not go with iView/EM back then....I saw what Aperture and Lightroom were doing, and could see that one needed to commit to one or the other (LR/Aperture v iView), unless they were prepared for more storage and management tasks. I still think EM is a much more powerful and useful catalog than LR/Aperture at this point, and may be more useful for folks that use ACR/PS, C1, RAW Developer, and other tools as their main processing tools, as it creates the DAM part those lack. However, if one's workflow preference is to just keep RAW files and instructions sets for handling things, EM is not going to work easily. It requires a completed file of some sort for cataloging. One can catalog just the RAW file, and maybe then launch some app to process it and go from there, but if you already have a library or libraries of processed images that have not been stored as final output tiff, PSD, JPEG, etc., files, like you would have inside LR or Aperture, EM is not going to be fun to work with.
LJ
P.S. The one way around things, maybe, is if EM could just access the created thumbnail or preview file from LR or Aperture, not having to "read" the entire processing instruction set. Then one could at least see what the version looked like, know where it was stored, and go from there. That is the power of the cross-platform/cross-app cataloging capabilities of EM. It cannot do that at this point, as far as I am aware. If it can get to that stage, as a minimum, it will become a lot more useful to folks using other DAM tools now.
LJ
P.S. The one way around things, maybe, is if EM could just access the created thumbnail or preview file from LR or Aperture, not having to "read" the entire processing instruction set. Then one could at least see what the version looked like, know where it was stored, and go from there. That is the power of the cross-platform/cross-app cataloging capabilities of EM. It cannot do that at this point, as far as I am aware. If it can get to that stage, as a minimum, it will become a lot more useful to folks using other DAM tools now.
Last edited: