Search the Community

When using "Photo - Launch registered application" function in Olympus Workspace on an E-P5 camera ORF raw file, Affinity Photo does not open it as a raw file, but immediately show it as a jpg format. This happens when no jpg format of the photo is available on the drive. Attached is a sample ORF raw file that opens in JPG format. There is no problem opening the ORF raw file any other way. (Windows 10 operating system) P3260053.ORF

Í’ve reported this bug last year for both Olympus ORF and Nikon NEF files (3500 model). It was resolved for NEF files, but it remains an issue for Olympus ORF (camera models e-m10, e-m5ii and e-m1ii). Trying to help another person, I see this also happens now with CR3 files from a Canon 90d. My post from last year Trying to place a RAW files does absolutely nothing but moves the background pic around.

I tried out the Affinity working with raw images, in my case .orf files. I liked the control over sharpness exposure etc. The problem was when I developed the image to continue work in the regular Affinity workspace, none of the adjustments I made were saved and I had to try to recreate my work. It is annoying as I would like to move to one program work flow, but there must be something I'm doing wrong. Mac desktop, Mojave.

I have updated to 1.6.7 on my IOS device (IPad pro, iOS 11.2.6) When I am trying to import ORF raw files (TG 5) no image is displayed in the raw development window, when I tap “develop” Affinity crashes, I am able tough to import ORF RAW files from an EM5 mk 2 Camera, is the Olympus TG 5 not supported by Affinity in spite of the IOS support for this camera? If not, when can I expect support for this camera?

When I run a batch job on some raw files using a macro I have created, the saved jpegs come out differently to when I run the same macro on files individually. Is there something I am missing? See attached photo: Left is individual output, and right is batch output. This only happens with raw files (olympus .orf) and not if run it on a jpeg. I can change the output of batch jobs to a degree by changing the develop assistant options, but I cannot get the result I wanted. I assume the problem is something to do with the develop persona, which I cannot record a macro for, but automatically runs when I open a raw file. Thanks for any help.

I'm evaluating the trial version of AP to see if it will free me from PS Elements. One problem that's really bothering me is the poor quality of the ORF RAW files imported from my Olympus E-M1. They're dark and muddy looking -- they look nothing like what I see in Oly's Viewer 3. Is this because I'm still using the trial version 1.4. (If so, it's not a feature that encourages someone to buy the program.) Will it be different if I buy the program and get the latest updated Beta version? If not, has anyone found a solution to this problem? I read a previous thread that said the problem was fixed but it's not fixed for me. I also just discovered that the ORF files appear to be imported at 96 DPI, despite the fact that a resolution of 300 is set in the camera. I saved some processed files before I realized this and now I have to do them over again. Why does this happen and how can I make sure imported RAW files are the correct resolution? Also, why is it not possible to see the image resolution anywhere in the UI? I had to use the Resize Document menu to see that the resolution is 96 DPI and change it to 300 DPI.

I open the topic regarding RAW. It means the cameras which RAW is reading properly by AP. At the moment I can't find information about these. I'm using Leica M (DNG) and Olympus OMD-EM1 (ORF)... Thanks in advance. Best, CYBURek