New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OM System OM-1 #11258
Comments
Why post 4 issues? One issue per camera is enough. And which mark you post here? Please update this issue by adding all wanted things from your 3 other issues and update title with mark you post. Thanks |
If mark is necessary, then it would be I. However it is not part of the model name and we don't know if there ever will be next marks of this model. |
Seems that I made some confusion with E-M1 one. Sorry. didn't know that Olympus release this new model. Thanks for your update. I let people who update cameras for darktable to check your samples. |
I tested OM-1 support today in the latest git code and it does not work. The camera is not recognized. |
That's why this issue is opened @algreen05 |
Great. What is needed to close it? |
I have tested OM-1 Support in Darktable-Dev 716. Lens Correction has the OM-1 Camera model and can recognize the camera in JPG files. But Darktable is unable to read the OM-1 RAW .ORF files. |
So good to read that: https://www.darktable.org/2012/10/whats-involved-with-adding-support-for-new-cameras/ |
Time is the only luxury we all possess and it isn't free. |
These together add full support for OM-1. Tested on thousands of images in darktable.
|
Here is a branch with OM-1 support based on darktable release 4.0.0 tag.
|
Can someone guide me how I can use it in windows11. I am also not able to edit photos taken by OM-1 |
I am playing with your custom build, and it seems to me that the highlight reconstruction does not work properly when "clip highlights" is selected: the clipping zones are replaced with tint patches instead of white. Maybe the color calibration module should come before the highlight reconstruction in the pipeline? Thanks, |
I don't think this is related to -om1. Highlight recovery module behaves the same in 4.0.1, with no om1 support. |
Indeed, you are right. Darktable highlight recovery is not working properly even in the official 4.0.1 build. In fact, none of the 4 methods work properly. Compare the result with RawTherapee: |
I've been using your build with my OM-1 based on DT 4.0. Thanks!!!! |
Yes, I do, maybe in a couple of days. |
Is there any feedback somewhere from the Darktable maintainers about why this hasn't been merged yet? It's been tested by so many users by now... I've been using it for months, and thousands of photos. |
rawspeed submodule has only one maintainer. He couldn't yet devote time to it… :( |
I just made a branch starting with darktable 4.2 release tag. It should automatically pull the right rawspeed submodule with OM System and OM-1 support. (WB presets and noise profiles for OM-1 are added to JSON files within the main darktable tree.) To get the source code:
To compile on Ubuntu I do:
Running
In case your previous darktable version was earlier than 4.2, then running this will upgrade database and possibly config. One can run this newly compiled 4.2.om1 something like this to preserve the existing DB and config:
|
I just compiled and installed your new 4.2 version in Fedora 36 Šarūnas, and it seems to be working great. Nice 2023 and THANKS A LOT!!!!!!!!!!!!! L. |
Could some kind soul dumb it down for this lowly Windows user? I see someone here has support for the new OM-1 working on the Linux version of Darktable. Is there an expected date (or current way) to add support for that camera in the Windows version of Darktable? Github is a strange place to me; I previously created an account to get builds of software to run a closed-loop insulin pump for my son. (I had very detailed instructions on another site that only showed how to grab the build from Github.) All that to say, be kind. :-) Newb to Nth newbieness. |
There is a ready-build Windows package available, check the post in pixls.us https://discuss.pixls.us/t/om-1-support-in-darktable/30980/55 |
|
I close. Rawspeed support added. Remains noise profiles (another issue opened) and PR opened and to update for WB. |
Just a little note, this has been added in rawspeed but the sub-module has not yet been updated so at the moment it is still not supported on darktable. |
Would be great to merge this into rawspeed stable and backport for 4.2.1 😉 @LebedevRI @TurboGit |
Hmm, forget that step. This will be done quickly I think so we can let this one opened. Will try to remember that next time! |
I have build dt from the latest master, and I'm not having OM-1 support. I have rebuilt everything from scratch, without success. Have I done something wrong, or should I wait for the submodule to be updated? |
@lintujuh: you have the answer just 3 comments above. |
This will have OM-1. Not that I can explain it :) |
The path
So, i tried commenting out
Does the |
It should still build, those there is no need to use my branch of rawspeed anymore, as OM support has been merged into darktable-org/rawspeed. |
I didn't pull
|
You can just check out master now. This is not a support forum, but a tool for development. Please head over to discuss.pixls.us for community support. |
Full support for OM has been merged into darktable main. One can just follow build instructions there. |
Please add support for OM-1. Default 20Mpx and three hi-res mode (25, 50 and 80Mpx) RAW sampes uploaded to raw.pixl.us.
The text was updated successfully, but these errors were encountered: