Can you remove an Olympus Pen-F color profile from RAW files in OM Workspace 2.4?

Asked 5/30/2026

4 views

2 answers

0

I’m editing ORF RAW files from an Olympus Pen-F in OM Workspace 2.4. The images were shot with one of Olympus’s in-camera color/film simulation modes enabled. In OM Workspace, changing Picture Control seems to add another look on top of that mode rather than fully disabling it. Finder previews appear to ignore the in-camera mode, which makes me think it may just be metadata. Is the color profile actually baked into the RAW file, and can it be disabled or ignored in OM Workspace?

Originally by Levon. Source · Licensed CC BY-SA 4.0

Levon

12d ago

2 Answers

0

AI Answer

Generated from our catalog & community — verify before relying on it.

The in-camera color/film simulation is not baked into the RAW sensor data. In a RAW file, those settings are stored as processing metadata or a suggested rendering recipe, not as changes to the underlying captured data.

So if exposure and scene are the same, RAW files shot with different Olympus color modes still contain the same basic RAW image data. What changes is how software chooses to interpret and render that data.

That also explains why Finder may ignore the Olympus setting while OM Workspace honors it: different software uses different metadata when generating the preview.

In practical terms, you are not trying to “remove” something from the RAW itself. You need OM Workspace to use a neutral/default rendering instead of the camera’s recorded style. If selecting Picture Control appears to stack another look on top, that means OM Workspace is applying its own processing choices while still referencing the embedded camera settings.

So the key point is: the RAW data is intact, and the color mode is only metadata-based rendering information, not permanent image data.

UniqueBot

AI

12d ago

0

Here's the thing you must remember about any color profiles: They're never applied to the raw image data that is recorded in the raw file. They never affect the contents of the raw image data. They're applied as a sort of "recipe" for processing the raw image data and that "recipe" is listed in the EXIF info appended to the raw file as the in-camera setting at the time the image was taken. But the actual raw image data is still only monochromatic luminance values recorded by each sensel for the light that strikes each sensel. Nothing more.

Assuming the scene is static and remains the same, and exposure time, aperture, and ISO setting remain the same then different images taken with different "film simulations" selected will still have identical raw file content (other than the random noise caused by Poisson distribution of light and the random read noise generated by the camera). The difference in what you see on the screen on the back of the camera is the difference in how that raw image data was processed to display it on your camera's LCD screen (most likely by generating a JPEG preview image, which is also appended to the raw image file along with the EXIF Info). It's not a difference of the actual contents of what the sensor detected.

If you tell any raw conversion application to disable the color profile or other processing instructions recorded in the EXIF Info, then the app should ignore the in-camera setting selected at the time of image capture and use its own default "recipe" to develop the sensor capture data contained in the raw file and display it on your screen.

It is unclear from your question if the above is what is happening which you do not want to happen, or if the above is what is not happening and you want it to happen?

Originally by Michael C. Source · Licensed CC BY-SA 4.0

Michael C

8d ago

Your Answer