I came across a reference that renaming the files to CR3 causes them to be opened by libraw. Short term you could open DT with a secondary database only for these files and set DT in this case not to write xmp files and then DT will use Libraw and open themā¦
Its quirky but if you need something to get it to work asap you could try it and then just edit that database later if you need to rename them or just dont worryā¦people using DNG have files that are renamed after allā¦
Iāve looked at the images that were converted and checked them against the DNG files, and they appear to be unaltered.
If youāre enquiring about Exif data then at lot gets pulled across with the conversion. That said, when I commence the conversion process, there is a warning that some DNG info will be absent, and that a plug-in needs to be installed to include this in the conversion. Digikam is available as a downloadable file that, if you mark as executable in its properties, will run Digikam without the need to install, and you can see the warning message in one of the windows. I have tried - but admittedly not very hard - to install the plug-in but not been successful so far.
@Margaret_Wong There might be an issue with your configured repositories. I canāt guide you through fixing that, but you may start at checking where those liblcms2-dev versions are coming from
apt policy liblcms2-dev
and then perhaps adjusting repositories, if possible at all.
apt policy liblcms2-2, as you may have some āxiotaā source configured for some software package, which provides conflicting version of liblcms.
This really has nothing to do with OM System support. You may just want to make sure that standard darktable can be built on your system, then 4.2-om branch will compile as well.
Thanks very much for this information:) You are correct I do appear have some āxiotaā software installed which seems to be because I upgraded from ubuntu 20.04 to 22.04 rather than doing a totally fresh install.
@sugarbravo thanks for these directions, I initially had some build dependency issues, but I got your branch to build successfully and run (the version is 4.2om1 in the top left by the darktable logo). However, when try to open a raw OM-5 file in darkroom I get the following error:
$ /opt/darktable/bin/darktable
RawSpeed:Unable to find camera in database: 'OM Digital Solutions' 'OM-5' ''
Please consider providing samples on <https://raw.pixls.us/>, thanks!
[rawspeed] (P1070052.ORF) bool rawspeed::RawDecoder::checkCameraSupported(const rawspeed::CameraMetaData*, const string&, const string&, const string&), line 170: Camera 'OM Digital Solutions' 'OM-5', mode '' not supported, and not allowed to guess. Sorry.
[temperature] failed to read camera white balance information from `P1070052.ORF'!
[temperature] `OM Digital Solutions OM-5' color matrix not found for image
[temperature] failed to read camera white balance information from `P1070052.ORF'!
[temperature] failed to read camera white balance information from `P1070052.ORF'!
[lens correction] camera/lens not found
[colorin] could not find requested profile `standard color matrix'!
For context, this is on Ubuntu 22.04 and I also installed exiv2 from source from the 0.27-maintenance branch per @kmilosās comment above.
rename them *.cr3ā¦they will openā¦its a hack but it makes DT use Libraw and it should open your filesā¦ if you canāt get all your builds to work you could at least do this for a work aroundā¦
Check whether there is OM-5 present in src/external/rawspeed/data/cameras.xml.
Also, as mentioned, only base support for OM-5 was added, no WB presets or noise profiles. Since OM-5 seems to be essentially an E-M5III clone, at least sensor-wise, sensor noise characteristics could be the same. Probably WB presets too, if firmware wasnāt tweaked by OMDS for that. Thankfully, in darktable 4.2 both noise profiles and WB presets can be added as JSON data without the to recompile. So those data structures can just be copied from E-M5III for OM-5. Ideally however they should be derived from RAW files from OM-5.
An easier approach might be to let src/common/imageio_libraw.c to process not only .cr3, but any supported RAWs.
There was no OM-5 entry in src/external/rawspeed/data/cameras.xml. I tried adding the entry from this OM-5 PR to cameras.xml, but that didnāt fix the error. Iām guessing I might need to rebuild darktable for it to take effect?
Also, is there a way to copy the EM5-III or EM1-III noise profiles and WB presets to the OM-5? if I remember correctly, the EM5-III, EM1-III, and OM-5 all use the same sensor, but the OM-5 and EM1-III use a different (more powerful) image processor than the EM5-III. If thatās the case then using the EM1-III data might be the way to go.
EDIT: Not sure where to confirm the sensor, but from B&H specs I can confirm that the EM5-III uses the Truepic VIII image processor while EM1-III and OM-5 use Truepic IX.
@priort this new om-1 build is not letting me import any CR3 files. Not sure why. However, I did use this hack with my stock darktable 4.2 install and it let me open the the CR3 files. The results can be a bit all over the place, though (image previews donāt show up in lighttable until you open a file in darkroom, etc.).
I rebuilt darktable with the added OM-5 entry mentioned above and I can now open the raw .ORF files
Some of the images appear completely white when I open them and I have to reset the raw black/white point module to fix that. Iām guessing that has to do with the lack of WB presets.
The submodules get over my head. iād like get the two @sugarbravo 's PRs merged with the current master, as Iād like to test the multiple presets feature.
It might be easier to let Libraw to process ORFā¦ no need to wait for rawspeed updateā¦ Works with some test files. Just made om-libraw branch to play with this.
Would it not be a good idea to use libraw instead of rawspeed for all of the RAW file types? If I understand well from other threads, maintaining rawspeed depends on only one person. Libraw is used by more programs and is better maintained.
Iād like to get your patches into current master. Your repo is cloned from 4.2, and I cannot (donāt know how to) merge it with current master to get a version based on 4.3.