6/10/2023 0 Comments Photo mechanic vs fastrawviewer![]() to see if I can see a player's jersey number that may be hidden in the selected one). Sometimes during review in LR I may have second thoughts, and want to go find a different selection from a burst, or just to review other images before and after (e.g. I keep the PM ingested images there for a while (in an area I don't back up) in case I need them. plus I'm importing only 5-10% of the original images. I ingest in PM to the same disk as my LR images will reside, then during the LR Import I do a Move, so it's VERY fast, as no actual additional file copy occurs. There are also zoom side by side comparison tools you can use to choose the best image. ![]() ![]() It's one keystroke per image, or for crops you draw one rectangle and move one corner per image (you can also lock aspect and choose aspect size from a dropdown if you want specific aspects only). ĥ) View only tagged, then select all taggedĦ) Drag and drop from PM onto Lightroom, which triggers an importĪll the above works great on a dual monitor setup, I keep the thumbnails on one screen, and a full screen view on a second. one keystroke per image to cull).Ĥ) Make another pass through each and crop/straighten tagged (occasionally reject some more). They have quite a following of lightroom users, so have preference settings that also align things like ratings and color metadata so they match how Lightroom does it.ġ) Ingest in PM (it can do multiple ingestions at once if you have multiple cards and readers)Ģ) Use the "T" key to tag keepers, and the arrow to go to the next image (i.e. enter TW12 and it will replace it with "Minnesota Twins player #12 Left Fielder Tom Jones" or some such, including ties to subscription services to keep those updated).Ĭlick to expand.Correct, it uses XMP files if your input is raw (I'm not sure about JPG only). It's widely used by press and media of all sorts, and includes lots of tools for JPG only shooters to finalize and upload fully coded images to services, including templates, auto-expanded code tables (e.g. For those not familiar, PM is not an editor really, it uses the embedded preview for raw images (or the JPG if you shoot JPG also). But for someone who comes back from a soccer game with 1500 shots and needs to cull and post 70 of them and still get to bed at a decent hour - there's nothing like it. I find LR's tools perfectly adequate, and more to the point the metadata aspect of LR is not slow - it's injest, cull and develop that is slow.įor someone shooting a few shots as opposed to hundreds or thousands per shoot, it's overkill. I know how to do metadata coding in PM, it has far better tools than LR for that, but I do not do so. A typical 3-4 hour session would now be 1-2 max. ![]() For day events more than in half, maybe to a third (as less images needed further editing). While LR's performance improvements may change this somewhat, when I first went from doing sports with LR only to PM + LR, I cut my post processing time easily in half. Going image to image in LR to crop is incredibly tedious - 2-8 seconds or so will pass between images, which doesn't sound like much, but let's say I am doing 100 images of crop at 4 seconds average that's about 6-7 minutes of staring at the screen. I find that for most events, about 50-80% of the shots need only a crop/straighten, no other edits. I also crop and straighten entirely in PM. Lightroom has improved ingestion substantially but there's still a HUGE difference in speed. Ingestion is faster, I can review images at full resolution (of the embedded preview) almost instantly. Almost even load from my camera goes through Photomechanic (PM), and for me it's all about speed. ![]()
0 Comments
Leave a Reply. |