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

JDEV

Members
  • Posts

    7
  • Joined

  • Last visited

Everything posted by JDEV

  1. I solved this problem in the short term by going back to version 1.65 JDEV 0n 7/12/2019
  2. I solved this problem in the short term by going back to version 1.65 JDEV 0n 7/12/2019
  3. Shortly before I updated to version 1.7 I had gone on an Osprey shoot. I meant to set the camera to shutter priority and ISO auto with max ISO set to 8000. Confused with the settings I mistakenly set the ISO to 8000. I took a number of shots with ISO 8000 and shutter speed to 1/8000. These were developed around the time I upgraded to version 1.7. Could these extreme settings have caused the program to get out of kelter?
  4. Thanks for your interest: I checked the 32-bit preview panel and nothing appears enabled. The exposure is set to 0 and Gamma is set to 1. The Display Transform is set to ICC Display Transform.
  5. This is the third iteration of this problem. I now include screen shots that should define the problem better. I am shooting a Sony A7iii for both jpeg and raw. For this problem I just shot two photos in the garden using "Auto" mode. I loaded the raw version of photo _9803 into Affinity (Windows 10) and the image Screenshot(2) came up in Develop window. Without making any adjustments I pressed "Develop" and the photo was transformed to Screenshot(3) which was in the range of what I wanted but I did not make any fine adjustments. Next I loaded the raw version of photo_9802 and Screenshot(4) came up. I made a number of changes trying to get the image to look as I wanted. The exposure was increased to + 0.7. The brightness was increased + 10%. The vibrance was increased + 5%. Using Shadows and Highlights, the shadows were increased 25%. These were the only adjustments that seemed to have a positive effect, but certainly was not an acceptable image. See Screenshot(5). I then developed this image and got Screenshot(6) which was awful. The net result is that I cannot use the Develop module to get a satisfactory photo since I upgraded to version 1.7. My only recourse seems to be to try to re-install the previous version or switch to a different program. I would appreciate any help I can get. For now I am using overlays, etc. to handle critical photos. This is using a great deal of extra time I don't have. _DFA9802.ARW _DFA9803.ARW
  6. I am shooting a Sony 7iii capturing raw & jpeg. When I upgraded to 1.7 the problem started. I initially thought that something went wrong with the camera but extensive testing proves the problem is in the program. When I load a raw file into the program the initial screen comes up so dark as to be unusable. The picture can be manipulated to look like the camera produced jpeg by lowering the exposure to -0.7 or -1.0, lowering the black point to -10%, and lowering the Briteness to -25%. Upon doing this and then developing the image, the result is grossly affected by the black point and Briteness settings. If on the other hand, I only adjust the the exposure down, the file develops to a reasonable facsimile of the camera produced jpeg. If I make no adjustments and develop the photo as is, I get a result that is usable (with subsequent manipulations). In effect, the develop module is useless in its present state. Since most of my working adjustments are usually in the develop module, the program has become almost useless to me. Files that worked well before the update as well as new photos all react the same way. The submitted file was an under exposed file I shot as a test when I first got the Sony A7iii. It developed up nicely on the older version of Affinity Photo. Now I cannot acceptably develop anything. HELP!!!! _DFA6103.ARW
  7. I am shooting a Sony 7iii capturing raw & jpeg. When I upgraded to 1.7 the problem started. I initially thought that something went wrong with the camera but extensive testing proves the problem is in the program. When I load a raw file into the program the initial screen comes up so dark as to be unusable. The picture can be manipulated to look like the camera produced jpeg by lowering the exposure to -0.7 or -1.0, lowering the black point to -10%, and lowering the Briteness to -25%. Upon doing this and then developing the image, the result is grossly affected by the black point and Briteness settings. If on the other hand, I only adjust the the exposure down, the file develops to a reasonable facsimile of the camera produced jpeg. If I make no adjustments and develop the photo as is, I get a result that is usable (with subsequent manipulations). In effect, the develop module is useless in its present state. Since most of my working adjustments are usually in the develop module, the program has become almost useless to me. Files that worked well before the update as well as new photos all react the same way. HELP!!!! _DFA6103.ARW
×
×
  • 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.