rawspeed
rawspeed copied to clipboard
OM System brand and OM-1 camera support
Based on kmilos:om-1 branch. using "OM System" instead of just "OM".
New "make", as in "manucfacturer" is OM Digital Solutions (like Olympus Imaging Corp., Olympus Corporation).
New "make", as in "brand" is "OM System", used instead of just "Olympus". Name "OM System" is used on the title page of OM-1 user manual, Exif MakerNote, SD card default directory, in OM Workspace software, by vendors alongside "Olympus", etc.
I tested this branch in darktable (with noise profile and white balance presets) by working on ~2000 .ORF images from OM-1.
@LebedevRI Why can't this be merged?
Hello, maintainers and developers, please let me know what can be done to get this merged. Thank you.
If I saw this PR earlier, I'd order my OM-1 1-2 months ago :laughing: I'm getting mine next week and can help testing, in case that's part of the blocker, or give a hand at anything else needed to get this merged.
I don't know what's impeding review and merge, but here is a darktable branch based on release 4.0.0: https://github.com/darktable-org/darktable/issues/11258#issuecomment-1179588323
I just built Darktable from this branch and I confirm it is working very well with my first OM-1 images!
Indeed, it looks like the branding has been somehow "officialised", so this PR should probably obsolete mine.
In addition, it looks like you can add OM System OM-5 support by simply copying Olympus E-M5 Mark III. @sarunasb
Having this included in time for darktable 4.2 would be highly appreciated. Thank you!
Indeed, as far as rawspeed
decoding, the newly released OM-5 is identical to Olympus E-M5 MkIII. Verified with sample RAW and DNG files from both cameras. OM-5 added to data/cameras.xml
.
Wrong issue, that was meant for OM-5, moved to https://github.com/darktable-org/rawspeed/pull/399
@sarunasb i am sorry. this should not have taken so long. the PR arrived at an unfortunate time.
I've merged it in 51d9192ef11ff72667e55a72ecfb3596fc8748ab, but looks like PR does not recognize the squash-merge as a successful merge of this pr, so looks like the PR will need to be just closed.
@sarunasb thank you for the contribution!
@sarunasb thank you for the contribution!
@sarunasb i am sorry. this should not have taken so long. the PR arrived at an unfortunate time.
I've merged it in 51d9192, ...
@LebedevRI Better later than never :) Thank you for your time!