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

AiDon

Members
  • Posts

    533
  • Joined

  • Last visited

Everything posted by AiDon

  1. Another option is if you have a integrated GPU, e.g. say a onboard Intel one, switch to that for the rendering.
  2. This is a known issue, in this thread there is a suggestion to downgrade the drivers ... and it works:
  3. Where are you saving it to? If it is on a NAS drive try saving to your hard disk then move it to the NAS
  4. Hi Chris, Thanks yes that driver works perfectly well ... but, there must be an issue in Affinity also because it only affects Sony RAW with the later drivers. Canon RAW and Fuji RAW are not affected along with TIF also. Regards, Don
  5. Hi, As detailed in this thread the crash is now happening in the latest PRD version.
  6. Hi, Note that it is still crashing in the latest Beta [1.8.4.693(RC)] also repeatable using ARW images for HDR. Regards, Don Crash Report Attached ... Unhandled exception at 0x000001DD06743CF8 (nvwgf2umx.dll) in f7d1f3df-b787-42cb-8396-c2919b64d31a.dmp: 0xC00000FD: Stack overflow (parameters: 0x0000000000000001, 0x0000003DE0CA9000). f7d1f3df-b787-42cb-8396-c2919b64d31a.dmp
  7. If you want some more I can also attach as it only seems to work for CR2/CR3 images. Sony & Fujifilm images have the Show AF Focus greyed out.
  8. Hi Chris, I have attached crash reports both from the PRD and Beta versions; - AiDon Crash Reports from 0627 Beta.zip - AiDon Crash Reports from 0627 Prd.zip You right insofar as it is unusual but I am sure it isn't the uncompressed RAW from Sony as it will happen with CR3, CR3 and Sony compressed. I have seen some inconsistencies when 3 images are selected from the File-> Open dialog at the same time, where the application sometimes reports opening 1 document or 2 documents using the GTX1050 but when using the iGPU (HD630) it always reports opening 3 documents. Regards, Don
  9. So, in summary, if I use the internal GPU as a renderer on either monitor the crash doesn't happen ... if I use the high-performance GPU as the renderer then the crash occurs. Driver is:
  10. AS UPDATED on the other thread ... Yes, this is still happening but it seems to be an issue with the monitor in use or the ICC Profile used by that monitor as I have a internal monitor using the IGPU (Intel HD630) set to sRGB IEC61966-2.1and a external monitor where the ICC profile being used is S24R35x.icm (Samsung). If I change that external monitor to sRGB IEC61966-2.1 the crash still happens. Windows setting is Extend. If I reset the settings and change the renderer to the iGPU and open on either monitor there is NO crash, the performance settings are: So the question is is the issue because of the renderer or the monitor or the compressed RAW? Also I noticed that when using the GTX1050 as the renderer the application interface colors are a little off.
  11. Hi Chris, no there are no crashes today, maybe next time I need to restart after an update. Here is the Develop Assistant settings: The other 2 issues reported are still happening: And, this is still happening on Develo, HDR Merge or Panorama Merge when 3 images are opened at the same time (ARW Only) ; Yes, this is still happening but it seems to be an issue with the monitor in use or the ICC Profile used by that monitor as I have a internal monitor using the IGPU (Intel HD630) set to sRGB IEC61966-2.1and a external monitor where the ICC profile being used is S24R35x.icm (Samsung). If I change that external monitor to sRGB IEC61966-2.1 the crash still happens. Windows setting is Extend. If I reset the settings and change the renderer to the iGPU and open on either monitor there is NO crash, the performance settings are: So the question is is the issue because of the renderer or the monitor or the compressed RAW? Also I noticed that when using the GTX1050 as the renderer the application interface colors are a little off. I have also updated the thread. Regards, Don
  12. Hi, t The following image can be downloaded from Dropbox at the link provided. The image is an ARW RAW from Sony A7 Mk III using a Sigma Lens (EF Mount) via a metabones Canon EF to E mount adaptor that causes an immediate crash with no recovery, note the Production version opens but shows EXIF as this: . DropBox: https://www.dropbox.com/s/e6fgso2jsw3ko7b/A7301307.ARW?dl=0 Note it seems like it crashes with most images using the metabones adaptor. Regards, Don
  13. Hi Chris, the crash hasn't happened again but the lens adjustment should adjust the Vignette to 0 rather than 100 for APS-C lenses attached to the FF Sony cameras. Regards, Don
  14. Hi, Opening a ARW taken on a A7M3 in crop mode with a APS-C lens crashed the Beta version with an sudden exit, I cannot replicate and there was no crash dump but I have added the image file that caused the crash as an attachment. Whereas on the PRD/BETA version the Lens Vignette is not correct as you can see here, setting the Intensity to 0 in the Remove Lens Vignette panel presents the correct image: Regards, Don A7301261.ARW
  15. Hi, Crashing reported in the PRD version is happening with the latest Beta (v1.8.4.665), the Beta created a Crash Dump which is attached. e5c83c16-44bc-4115-908f-3087231a2dc3.dmp
  16. Note that this also happens in the Beta version so I have reported there. I also see it happening if I have any 3 images open at the same time in develop, the following I can reproduce: uncompressed RAW from the A7M3 causes a crash compressed RAW from a A6400 doesn't crash CR2 from both 5DsR and 5D Mark III cause the crash CR3 from a M50 doesn't crash There is a dump from the Beta version that I have uploaded there.
  17. Hi, Idon't seem to be having these issues with EOS M50 images. I also set the Tone Curve to Apply tone curve but with no Exposure bias in the Assistant.
  18. Hi Chris, Uploaded to the link. Just the following sequence: 1. File-Open, select all 3 images 2. Select A7301234.ARW (last opened) select Basic, Profile and select ProPhotoRGB, click Develop 3. Select A7301232.ARW (first opened), Click Develop 4. Click on A7301233.ARW (second opened), Click Develop and it just exits. Nothing special with the OS and peripherals, these are the specs: Operating System: Windows 10 Version 1909 (OS Build 18363.900) Graphics Hardware: GeForce GTX 1050/PCIe/SSE2 OpenGL Driver: 3.3.0 NVIDIA 446.14 CPU RAM: 16269 MB Video RAM: 4096 MB Preview Limit: 6449 Pixels Have also reset by clearing the user data multiple times, no difference. Note I haven't downloaded and tested the latest Beta. Regards, Don
  19. Hi, I have 3 Sony A7M3 images (any) that I open at the same time (ARW) in Develop but the application will always crash on either the second or third image. Usually if I add an Adjustment, say add a profile for the developed image, it will crash when clicking on the window for the next image, if I don't add an adjustment it will crash on the 3rd image. There is no crash report or crash dumps available the application simply exits. I can supply the 3 images if you like, there are uncompressed RAW, or another 3 that are compressed RAW. I do believed it may be concerning the Sony RAW images only, compressed or uncompressed, as it doesn't happen with other types of images I have such as CR2, CR3 and RAF RAW images. Note that I can reproduce this 100% of the time by opening any 3 ARW images, Regards, Don
  20. Try changing the RAW output format to RGB (8 bit) in the Develop Assistant and see if that gives a better output or try AdobeRGB (1998).
  21. Hi, try this. Make sure that the RAW output format is set to RGB (16 bit) in the Develop Assistant. From the Second pic above, where you have applied the Tone Curve, and just before clicking on Develop change the Profiles on the Basic Tab to ProPhotoRGB then press Develop.
  22. Make sure you have "Apply tone curve" selected on the Develop Assistant:
  23. Just a request to include corrections for the Sony FE 200-600 mm F5.6-6.3 G OSS (SEL200600G) to the lens corrections database.
×
×
  • 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.