Piro

Hi Gabe, I think this has been addressed elsewhere by Chris B (we think the issue is process-specific, i.e. jpeg+raw, and nothing to do with the individual file)

Is it possible to revert from the beta to the public release? I'm happy to give it a go, but terrified I might have other problems - so would be good have fallback option.

Yes! As posted on the Sony/.awr thread (the glitch must have something to do with the process for opening RAW+JPEG files, as it does not occur with RAW only): "OK so I've just tried two different processes: (1) took new photo on Sony RX100iii in RAW+JPEG format; (2) took new photo on same camera in RAW format. (2) Imported correctly into Affinity Photo, showing as RAW and opening in Develop Persona. (1) (JPEG+RAW) failed to import, showing the 'Failed to open file' dialogue box. So no help in opening files where photos are in JPEG+RAW, as is the case with most of my photos going back some years."

Actually I've just addressed this issue. I'm using iPad Pro 12.9 with 256gb, in conjunction with MacBook 500gb. Don't like Cloud storage for lots of reasons, so I also use external storage, including SSD and most recently WD Passport SSD Wireless which gives a 'personal Cloud' option which is useful when don't want to bother with wires. The originals are safe, though it's been a pain backing them up (as also discussed on here). In future I'll be shooting in RAW rather than JPEG+RAW which avoids some of the problems.

Sorry to be thick, but what is the '172 beta'? Does one need to subscribe to the beta programme to get this? Currently running 1.8.0.168. Thanks

OK so I've just tried two different processes: (1) took new photo on Sony RX100iii in RAW+JPEG format; (2) took new photo on same camera in RAW format. (2) Imported correctly into Affinity Photo, showing as RAW and opening in Develop Persona. (1) (JPEG+RAW) failed to import, showing the 'Failed to open file' dialogue box. So no help in opening files where photos are in JPEG+RAW, as is the case with most of my photos going back some years.

That's fine going forward, but not much use for the many RAW files already imported into Photos where originals of no longer exist on SD card.

p.s. Is there any way of checking in Affinity Photo the size and format of the file, as with the 'Information' facility in Darkroom, above? If not, how do you know whether it is RAW? If it is only RAW when the file opens in Developer, and says RAW (which is what used to happen when opening from Photos), then none of the work-arounds work - they all succeed in opening the file only because it is no longer RAW!

Just tried this, and it's true the file can be opened using 'Import from Cloud' whereas is can't be opened using 'Import from photos. BUT as far as I can see, the file imported from Cloud in this way is no longer in RAW format, which defeats the point of the work-around. So for example, this is the Sony JPEG/RAW (.awr) file opened in Darkroom, which shows size as 20.9mb. And here is a shot showing the same file exported from Photos into the Cloud, then imported into Affinity Photo using the 'Import from Cloud' function - now only 5.6mb. I suspect this may be happening with the other workaround suggested elsewhere on the forum.

Lots of discussion on this, see for example https://forum.affinity.serif.com/index.php?/topic/108121-dsrryl-saunders-sony-raw-files/

Thanks DM1. This really is the most bizarre coincidence, as this morning the thumbnails are back (as in your post above), for the first time in months! So thanks also AP for the fix, though I don't know quite how this has happened.

Thanks very much p_mac, that's incredibly helpful. This seems to work for me, though I'm not convinced that the file that opens is RAW, rather than JPEG: whereas under the previous 'import from photos' action the file would open in the Develop Persona with a RAW tag, your workaround (as you say) opens in the Photo Persona. Is there some way of knowing whether the file really is RAW? I should say that the JPEG/RAW (Sony .awr) files I am trying to open from Apple Photos are as they left the camera, and have not otherwise been processed in any way. Thanks in advance. Piro

Did anyone above resolve this, or find a work-around? I have this problem with Sony (ARW+JPEG) files since updating to 1.8.0 - very frustrating.

Hello again DWright, sorry to be a pain, but is there any movement on this? It is incredibly frustrating when a valuable software feature disappears from an updated version, and then to have no information on if/when the feature is likely to be restored.

Not sure how this works? Have iPad pro 12.9 inch.