martinch

OK, I've uploaded another. If I find any more in the next few days, I'll upload, but I'm not sure if there are any more stored. I usually deleted them after it happened.

Also, have you seen this thread?: file-is-corrupted-and-closes-automatically-after-opening/ I believe this user is experiencing the exact same issue as I. The problem was with a Publisher file, but the user found that the issue was being caused by a broken image file within the Publisher document, and removing it solved the problem. I strongly suspect the problematic image file was corrupted in the same manner as mine.

I have found one of the other corrupt files, but that dropbox link has expired.

I have uploaded the file, thanks. I attempted to re-create the problem by setting up the same circumstances of multiple files open and saving a new .afphoto of this image, but there was no error this time. It really seems to happen randomly.

I am storing it locally on a 4TB SATA HDD. It hasn't otherwise ever given me trouble. I am using Win10 Education, OS build 19041.1165 Processor is an AMD Athlon II X3 455. I don't know how I could reproduce this problem, since it seems to happen randomly when saving. I can share the document. If I were to suggest any common factor when this happens, I can only say that to my recollection, I had multiple files open each time.

I just posted this elsewhere in a reply where I found someone had the exact same problem, but reposting here in the correct forum section: I have now experienced multiple times an error saying "file seems to be corrupted" after saving a file. It cannot be opened. I am using the current 1.10.0.1127 version, but I also experienced it with the previous 1.09 version (was really hoping 1.10 would have solved this!). I am using Windows 10, kept up-to-date. Attached is screenshot. This appeared immediately after saving the file. After the error box popped up it closed the image. Shows same error if I try to reopen. Same for files where this has happened previously.

I am having this same problem with Affinity Photo. This has happened to me multiple times now! I save an image and I get this error. I am never able to open it again subsequently. Also, sorry this is a wrong section of the forum, because I am using Photo, not Publisher, and I'm using Win10, not Mac. But here you see the same issue as OP using a different app/os.

You're satisfied with the noise reduction? I didn't care for it at all. I wouldn't be satisfied processing underexposed images with Affinity, though these days, I've more often been erring toward exposing slightly to the right for less noise generally. I'm seeing a weird lack of definition with Affinity when compared to Camera Raw, Raw Therapee or DxO. None of my lenses were recognized by Affinity, so lens correction isn't so good either. In comparison, DxO and Camera Raw recognize my lenses no problem. I've been playing with some other applications to make more comparison. So far, RawTherapee and DxO PhotoLab2 are the two that seem to give the best results and have a workflow I'm comfortable with. I didn't care for Capture One's workflow at all... it's the same issue I have with Lightroom's. I don't like having to create these large projects or collections or "reels" or whatever they're called and then "import" my images into them. I want to just be able to easily browse and then develop and export individuals as I see fit. RawTherapee and DxO behave more akin to if I were using Bridge+Camera Raw (though less clunky than Bridge, thank goodness). But none of these applications seem to have what I need with precise curves adjustments (I posted separately about this). As one of my cameras is a Nikon D800, I've tried Capture NX-D as well, and it does get some good quality, but I found it processes very slowly on my computer, much slower than any of the other applications. This makes it very tedious to use.

OK, I'm glad to be hearing this from another user, because I had been troubled by what I was seeing in the processed raw images but hadn't done a close comparison to the other apps yet. My experience is that the details look "smudgey" compared to what I see in Camera Raw or Raw Therapee. And the noise reduction is not attractive at all... makes the smudginess even worse, even at minimal settings. I'm running it on Windows.

Agreed. I don't like having to go through many different pages to do basic adjustments.

I agree. It would be a big time saver.

Also, lack of Gray Gamma 2.2 is annoying. I know that your Gray D50 claims to have a gamma of 2.2, but this still doesn't tell me whether it translates exactly to the same result as using Gray Gamma 2.2 profile.

Here's another thing that's keeping me stuck using PS for the near future, as I haven't found a suitable replacement in another application... I require precise adjustments of curves for when I create calibrated contrast correction for alt process photo printing. I regularly print using gum pigment (aka, gum bichromate), kallitype, gumoil and cyanotype techniques. The overwhelming majority of my fine art prints are done this way. To get the best results, it is necessary create compensation curves to correct for the deficiencies of the print process. They are all different, and ideally one would create individual curves for each kind of paper used, as well as for the different processes. I feel confident saying this is the common practice amongst alt process photo printers these days, so I'm certainly not the only one who would benefit. A full description of the process I use can be found here: https://www.freestylephoto.biz/alternative-process/making-digital-negatives Please take special note of Figures H and I in the article because these illustrate exactly what I'm needing to do with curves. What I need is the ability to precisely input the required I/O numbers into the curves dialog. Not only do I not see any way to do this in AP's curves, I don't even see any sort of scale that would clue me in to where I am on the curve. I am able to read gray values the way I need with the eyedropper, but without being able accurately translate those numbers to a curve, I'm stuck with only half the tools I need to do this.

Exactly. I was really hoping I wasn't the only one who considers this a basic function for raw processing. Without it, I can't consider AP for the serious photo work I do. The fact that it wasn't included from the very beginning makes me wonder who the intended user base is, because this is a big turn-off to professional photographers. In comparison, even freeware open-source applications like Raw Therapee have non-destructive raw processing. The non-destructive editing and ease of going back and tweaking is the main reason for using raw.

No one else has any interest in non-destructive develop persona? People like being stuck in a 20-years-in-the-past destructive workflow?