Some suggestions for more efficient use of OM Workspace

[peterwgallagher]

The raw files produced by Olympus and OM-Systems cameras and lenses ask a lot of an image processor. OM Workspace [OMW] is (mostly) equal to these demands, but it's still rather limited in scope and slow compared to other processors. I've got some suggestions that might help other users to take advantage of OMW's strengths while working-around its limitations. TL;DR: you can find my suggestions in an illustrated PDF here::

https://petergallagher.net.au/om-workspace-workflow

It's not obvious that Olympus/OM raws should be difficult to process. But they're small (20.x MB typically) and don't leave a lot of room for cropping-out errors or irrelevant bits. Then the sharp native lenses and the very fast sensors ('quad' sensor in the OM cameras) pack a lot of detail into each proprietary-format raw file that several raw-processors just fail to find or use. Also, sometimes, they're Hi-Res files (50-80 MB) with more detailed luminance, colour and contrast information that, again, most raw processors seem unable to access (Luminar Neo, not at all). The lens distortion-correction data is built-in to the raw file, so almost any processor should be able to use it, although not all seem to use it well.

Finally, these are raw files from a brand that is not in the top-three-or-four by sales in most markets. That must affect the degree to which Adobe, or DXO, much less Capture One or the smaller competitors like Skylum and ON-1, would consider it important to accomodate Olympus/OM users with specific algorithms or facilities.

You would think that should give a big lead to the raw-processor made specifically to integrate with the Olympus/OM cameras. After all, OMW uses the routines devised by the same engineers that designed the camera's internal software. You would guess it should be the processor-of-choice for Olympus/OM shooters.

I have no data on whether that's a safe guess or not. But I suspect from knocking around M43 photo forums for many years that only a small minority of Olympus/OM raw shooters use OM Workspace for anything other than for updating their camera firmware.

The reasons seem to include the slowness of the software on all but the best-equipped computers (not just for processing but also/especially for screen-updating) and the limited functionality it offers. It makes only global adjustments (apart from a clunky 'spot' cloning stamp); it is not good at recovering detail in extreme highlights; it will focus-stack but offers raw-shooters almost none of the other facilities available from modern raw-processors such as HDR imposition or panoramas (they're available only for Olympus consumer-JPEG cameras). It has a serviceable viewer, some limited 'filter' options and doesn't offer keywords, only a text field for saving comments on an image.

The outstanding strength of OMW, however, is it's basic rendering. It does a much better job with luminance, contrast and detail reproduction from OM raw files than any other processor, in my view. Also, it has an excellent "apical" luminance/contrast adjustment tool; good colour controls; a very good "AI" noise reduction action; the best 'dehaze' of any processor I've used, and; good-enough distortion/key-stoning controls.

So my goal for the past few months has been to find ways to take advantage of these strengths and work-around the weaknesses. This includes

* deciding whether to process on my computer or to use OMW's unique 'tethered' processing using the camera's internal 'TruPic' processor

* finding ways to quickly and efficiently import, rename, cull, rate and globally-process my raw files

* creating routines to better integrate a bit editor (Photoshop, Affinity Photo etc) into my post-processing to allow precise local-adjustments to images developed by OMW and to move those adjusted images back into the OMW catalog.

I've made an illustrated list of six practical suggestions for taking advantage of OMW's strengths that you'll find on my website at:: https://petergallagher.net.au/om-workspace-workflow

 

[grsnovi]

I don't use OMW to process my raws however I do use it to cull shots from a burst.

I shoot both raw and jpg so what I'll do is pull the jpg's to my computer and use OMW to determine which images to keep (deleting the jpgs along the way).

I'll then delete the raw's that don't have a kept jpg.

Then I'll process the remaining raw's (I use Affinity which works great for me).

Then I'll delete the camera jpgs and raw's leaving only the jpg's that I've exported from AP.

 

[luxborealis]

Thanks, Peter, for the PDF. OMW deserves more of my attention, it seems.


Terry
______________________________________
Capturing the Art inherent in Nature
www.luxBorealis.com

 

[peterwgallagher]

You're welcome, Terry. Hope these ideas are useful.

Great images on your website, by the way!

Peter

 

[jc11]

The raw files produced by Olympus and OM-Systems cameras and lenses ask a lot of an image processor. OM Workspace [OMW] is (mostly) equal to these demands, but it's still rather limited in scope and slow compared to other processors. I've got some suggestions that might help other users to take advantage of OMW's strengths while working-around its limitations. TL;DR: you can find my suggestions in an illustrated PDF here::

https://petergallagher.net.au/om-workspace-workflow

It's not obvious that Olympus/OM raws should be difficult to process. But they're small (20.x MB typically) and don't leave a lot of room for cropping-out errors or irrelevant bits. Then the sharp native lenses and the very fast sensors ('quad' sensor in the OM cameras) pack a lot of detail into each proprietary-format raw file that several raw-processors just fail to find or use. Also, sometimes, they're Hi-Res files (50-80 MB) with more detailed luminance, colour and contrast information that, again, most raw processors seem unable to access (Luminar Neo, not at all). The lens distortion-correction data is built-in to the raw file, so almost any processor should be able to use it, although not all seem to use it well.

Finally, these are raw files from a brand that is not in the top-three-or-four by sales in most markets. That must affect the degree to which Adobe, or DXO, much less Capture One or the smaller competitors like Skylum and ON-1, would consider it important to accomodate Olympus/OM users with specific algorithms or facilities.

You would think that should give a big lead to the raw-processor made specifically to integrate with the Olympus/OM cameras. After all, OMW uses the routines devised by the same engineers that designed the camera's internal software. You would guess it should be the processor-of-choice for Olympus/OM shooters.

I have no data on whether that's a safe guess or not. But I suspect from knocking around M43 photo forums for many years that only a small minority of Olympus/OM raw shooters use OM Workspace for anything other than for updating their camera firmware.

The reasons seem to include the slowness of the software on all but the best-equipped computers (not just for processing but also/especially for screen-updating) and the limited functionality it offers. It makes only global adjustments (apart from a clunky 'spot' cloning stamp); it is not good at recovering detail in extreme highlights; it will focus-stack but offers raw-shooters almost none of the other facilities available from modern raw-processors such as HDR imposition or panoramas (they're available only for Olympus consumer-JPEG cameras). It has a serviceable viewer, some limited 'filter' options and doesn't offer keywords, only a text field for saving comments on an image.

The outstanding strength of OMW, however, is it's basic rendering. It does a much better job with luminance, contrast and detail reproduction from OM raw files than any other processor, in my view. Also, it has an excellent "apical" luminance/contrast adjustment tool; good colour controls; a very good "AI" noise reduction action; the best 'dehaze' of any processor I've used, and; good-enough distortion/key-stoning controls.

So my goal for the past few months has been to find ways to take advantage of these strengths and work-around the weaknesses. This includes

* deciding whether to process on my computer or to use OMW's unique 'tethered' processing using the camera's internal 'TruPic' processor

* finding ways to quickly and efficiently import, rename, cull, rate and globally-process my raw files

* creating routines to better integrate a bit editor (Photoshop, Affinity Photo etc) into my post-processing to allow precise local-adjustments to images developed by OMW and to move those adjusted images back into the OMW catalog.

I've made an illustrated list of six practical suggestions for taking advantage of OMW's strengths that you'll find on my website at:: https://petergallagher.net.au/om-workspace-workflow

So I wanted to look at your document, But it says it is not availible..

 

[peterwgallagher]

Hi JC,

Try this (https://drive.google.com/file/d/1K8xsxKsPKMdBD_1nwBWMBAlRKxpNDWal/view?usp=sharing ) direct link

best,

Peter

 

[tomrandall86]

I generally these days always open up OM Workspace alongside my photo imported into Adobe Lightroom Classic.

The main reason is how Workspace renders the colour of the photos - I find it incredible. Not only accurate but it naturally softens blacks a little, so the same as how the camera would render a jpeg.

I tend not to export TIFF files or anything from it though because of the huge file sizes, and because I generally like using just one application to develop photos.

I keep Workspace open side by side because if I decide I actually prefer how Workspace renders the colour, then I try and mimic that within Lightroom and create some presets.

The colour calibration panel in Lightroom is fantastic, but I also use the colour mixer to try and match the hues Workspace brings out. Where Workspace shines is hue changes across a colour, for example autumn trees where there are mixes of reds, oranges and yellows. Lightroom by default warms everything up, probably maybe 200 to 400 Kelvin warmer than OM Workspace, and Lightroom does not understand yellows within ORF files very well, so modifiying HSL within Lightroom is a must for trying to get that "Olympus" colour.

At least, that's what I use it for!

 

[jc11]

Hi JC,

Try this (https://drive.google.com/file/d/1K8xsxKsPKMdBD_1nwBWMBAlRKxpNDWal/view?usp=sharing ) direct link

best,

Peter

that worked, Thank you!!!