I made a free OM SYSTEM OM-3 Recipe Studio tool for Windows
Hi everyone,
I have been working on a small independent Windows tool for the OM SYSTEM OM-3, and I’m finally sharing the first public beta.
It is called OM-3 Recipe Studio.
Disclosure: This Windows executable was built with AI-assisted coding. It is unsigned and has not been independently security-audited, so please only run it if you are comfortable with that and verify the SHA256 first.
GitHub Release:
https://github.com/roxsoulee/OM3-Recipe-Studio/releases/tag/v0.9-public-beta
Please download this file from Release Assets:
OM3_Recipe_Studio_v0_9_Public_Beta_Windows.zip
Do not download GitHub’s automatically generated “Source code” zip/tar files.
Current build:
v0.9 Public Beta / Internal build: v1.11.3l_ExportOESDialogEncodingFix
SHA256:
B2312BE63651A46E938B9311886E3329FAF0B9B8D52AA6B301B56980609D8A43
What it does
OM-3 Recipe Studio is a tool for creating and editing OM-3 color / monochrome recipe files.
It currently supports:
- Color recipe editing
- Mono recipe editing
- Loading an OM-3 Recipe JPG and backfilling the recipe parameters
- Exporting Recipe JPG files
- Importing / exporting OM Workspace
.oesrecipe files - Loading a preview image
- Before / After / Compare preview
- Saving and deleting local presets
- Custom output folder
- Rename / timestamp export workflow for both Recipe JPG and OES files
- Displaying WB information from loaded JPG / OES files
The exported files are meant to be used with OM Workspace and the OM-3 recipe / color profile workflow.
Important notes
This is an independent research tool.
It is not affiliated with, endorsed by, or supported by OM Digital Solutions, OM SYSTEM, Olympus, or OM Workspace.
It has only been tested against the OM SYSTEM OM-3.
Other OM SYSTEM / Olympus cameras are not guaranteed.
The preview is only an approximation. The final result may still differ from the camera output or OM Workspace rendering.
White balance information can be displayed when it exists in the loaded JPG / OES file, but WB is not applied through the recipe workflow. If you want the same WB result, you still need to set WB manually on the camera.
The Windows EXE is currently unsigned, so SmartScreen may warn you on first launch. Please verify the source and SHA256 before running it.
Basic workflow
- Download the Windows zip from the GitHub Release page.
- Extract it.
- Run
OM3ManualRecipeBuilder.exe. - Use File / Open Image for Preview to load a reference image.
- Edit Color or Mono recipe parameters.
- Or load an existing Recipe JPG / OES file to backfill parameters.
- Export either:
- Recipe JPG
- OM Workspace
.oes
- Import the result through OM Workspace / OM-3 workflow.
The exported Recipe JPG and OES files both support rename / timestamp naming, and overwrite-safe _02, _03 suffixes.
Color recipe controls
The Color tab lets you adjust:
- 12 color wheel nodes
- Contrast
- Clarity
- Highlight
- Midtone
- Shadow
You can adjust the values using sliders, numeric fields, or the color wheel preview.
Mono recipe controls
The Mono tab supports:
- Mono filter color
- Filter level
- Mono color
- Film grain
- Contrast
- Sharpness
- Highlight
- Midtone
- Shadow
- Shading
Loading Recipe JPG / OES files
If you load an OM-3 Recipe JPG, the tool reads the recipe payload and fills in the editable parameters. For this example, I used one of the OM-3 Recipe JPG files shared by OMTC here:
https://omtc.substack.com/p/5-jpeg-recipes-for-the-om-system
If WB information exists, it will be shown, but you still need to set WB manually on the camera.
If you load an OM Workspace .oes file, the tool imports the supported recipe parameters. If the file contains fields that OM-3 Recipe Studio does not apply, they are listed in a short “Not applied” section instead of being silently ignored.
Feedback welcome
This is still a public beta.
If you try it, I would appreciate feedback, especially from OM-3 users.
Useful bug reports would include:
- Windows version
- What you were trying to do
- The JPG / OES file type involved
- A screenshot of the problem
- Whether the issue happens in OM Workspace or only in this tool
Note: English is not my native language, and this post was translated and edited with the help of AI. This tool was also built with AI-assisted coding, and the EXE is unsigned. Please verify the SHA256 before running it.
Thanks!