Jump to content
You must now use your email address to sign in [click for more info] ×

Apple Engine opens supported camera's RAW as black


Recommended Posts

I use a Canon D6 Mark II which produces a .CR2 RAW file format.  When importing using the Serif engine I was getting a purple haze, so using the Assistant Manager I changed the engine to Apple.  I closed Affinity Photo and tried the same file again.  Now CR2 files open as completely black.  My camera is listed as a supported format on the Apple web site:  https://support.apple.com/en-us/HT207972.  I will attach an example file here.  I am able to view this file in Photos on my iMac.   

IMG_0127_RAW.CR2

Link to comment
Share on other sites

  • Staff

Hi WoodWorkerPaul,

Welcome to Affinity Forums :)

That camera is only supported if you are running macOS High Sierra. Are you sure you are not looking just at the thumbnail on Apple Photos? Double-click the thumbnail to see it in full screen - are you able to see it or just a grey exclamation point sign/icon?

 

Link to comment
Share on other sites

Just as a point of reference, I am running macOS Sierra (not High Sierra). If I set Affinity Photo to use the Apple engine, when I click the Develop button after opening this file, Affinity Photo crashes.

All 3 1.10.8, & all 3 V2.4.1 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7
Affinity Photo 
1.10.8; Affinity Designer 1.108; & all 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7

Link to comment
Share on other sites

Hi MEB!  Thank you for the quick response!  

 

I am running macOS High Sierra (version 10.13.1), so that shouldn't be the issue.  I am running Affinity Photo 1.6.6. 

 

I am unsure I understand the thumbnail question.  Here are the steps I follow:

1.  I start with Affinity Photo closed.  I open it with no document loaded. 

2.  On the Affinity menu bar, I navigate to File>Open and select the desired *.CR2 file.  

3.  Message appears along the top for a moment, "Affinity Photo - loading 1 document".  Once that finishes, I get a giant black screen.  The histogram also reflects all data along the left edge.  

4.  I checked Assistant Manager to confirm engine being used is the Apple engine.  I will attach a couple of screen shots.  

 

I hope I am doing something wrong!  

Affinity after it opens CR2 file.png

Affinity Developer Assistant.png

Link to comment
Share on other sites

MEB - 

 

I’m curious if it has been determined whether there is something I need to be doing differently?  I would very much like to be Affinity centric (it keeps things affordable and simple for me) even during my CR2 processing.  So if I’m erring, that would be excellent!  Alternatively, if this is an issue that is known to be in the pipeline for further development that would give me some hope that eventually I can stay in Affinity for my entire process!  

 

If nothing further is known at this time, that would also be helpful to understand.  After all, my camera (EOS D6 mk II hasn’t been around long).  But if it will be a while, I can begin looking for alternative solutions for my CR2 processing (which I’d prefer not to do).  

 

Thank you! 

 

 

Link to comment
Share on other sites

Quote

I am unsure I understand the thumbnail question.

The Canon RAW file has also a smaller jpg thumbnail embedded which might be shown instead inside the Photo's image browser, so MEB's question was if you can enlarge that one as a full shown up image preview (...are you able to see it or just a grey exclamation point sign/icon) here, which in turn would mean that Apple Photo then indeed can handle your RAW file.

If that doesn't work you have to use Canon's own supplied DPP or some other third party RAW processor (DxO, Rawtherapee etc.) in order to develop your D6 Mark II raws, until Apple and/or APh do really support your cams raw format!

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

v_kyr - thanks for the clarification!  

 

To make sure I'm tracking with you . . . I shoot JPEG + RAW, so my camera spits out one of each type of file.  Before importing my photos into any photo management software I rename all RAW files to append the word "RAW" at the end of their name (but before the .CR2 extension).  This way I am always dealing with the raw file when I mean to, as opposed to accidentally grabbing the similarly named JPEG.  So this separate JPEG file is not the cause of my issue.  

 

To start, I navigated to my CR2 file using OS X's Preview App.  I was able to preview the CR2 file.  (See third screen shot, below).  I then proceeded to check out the same file in Affinity.  This time, I decided to use the Affinity Media Browser to navigate to my pre-processing folder.  I was able to see thumbnails of all files - whether JPEG or CR2.  If I drag JPEG into the Affinity window it opens fine.  If I drag the corresponding CR2 file into Affinity I get the black screen.  I'll attach a couple of screen shots to show what I mean.

 

I also tried to develop the black CR2 file, but it was all black in the Photo Persona as well.  There was no change when I switched back to the Develop Persona.  

 

I am open to additional ideas to try!  

 

The D6 mk II seems to be a reasonably popular camera, so maybe this is something that will be fixed relatively quickly.  I may just have to go with DPP for now.  Not ideal, but I can make it work!  Maybe I'll give Lightroom a run.  I just really hate the idea of a subscription. . . 

 

Cheers! 

Screen Shot 2017-12-10 at 3.40.45 PM.png

Screen Shot 2017-12-10 at 3.51.53 PM.png

Screen Shot 2017-12-10 at 4.02.09 PM.png

Link to comment
Share on other sites

**Update**

 

I took some shots in format M-RAW, which is still a CR2 raw file but is a smaller file size.  These files all behave exactly as they should!  On this basis, I think my hardware may be the limiting factor.  Affinity handles the smaller raw files just fine when the Apple engine is selected in Assistant Manager.  

 

I will upgrade my RAM (I am currently running with 8GB) and see if that makes a difference.  

Link to comment
Share on other sites

Well mRAWs (medium) and sRAW (small) have less resolution than the common RAWs thus the smaller file sizes. Usually running with 8GB RAM should be Ok since that is what most Macs do nowadays come with as default equiped. - Can Apple Photo open those Canon full size RAWs on your system?

☛ Affinity Designer 1.10.8 ◆ Affinity Photo 1.10.8 ◆ Affinity Publisher 1.10.8 ◆ OSX El Capitan
☛ Affinity V2.3 apps ◆ MacOS Sonoma 14.2 ◆ iPad OS 17.2

Link to comment
Share on other sites

MEB: thank you for the update!  No worries about the delay.  I am impressed that there is a human being paying attention to this forum.  Your attentiveness makes me all the more desirous of staying Loyal to Affinity!  (I have talk about it with anybody who cares and even gifted the iPad app to my friends for Christmas!)

Link to comment
Share on other sites

  • 2 weeks later...

This underlying issue persists, but I have found a workaround for now.  I have downloaded the Adobe DNG Converter for free.  I convert my CR2 files into DNG files which appear to work seamlessly with the Serif Labs RAW engine.  Contrary to my prior thoughts, I have concluded that this is not a hardware issue, so I did not upgrade my computer.  It will be nice to do away with this intermediate conversion sometime in the future.  But this solution works for now. 

 

Thanks all! 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.