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

Lareneg

Members
  • Posts

    19
  • Joined

  • Last visited

  1. Hey @Chris B - is there any new information concerning this matter? Thank you a lot :)
  2. Thank you for your answer and your further investigation. The app does not hang, it is still responsive in terms of the "working"-animation and other buttons such as minimize / maximize. It just cannot be closed because it says "processing is still running" and therefore the only way of closing it is by using the Task Manager and killing the process. Do you need a memory dump nevertheless? If i can contribute in finding the cause of this (e.g. by doing some tests / giving you remote Teamviewer-Access to the machine to test stuff / ...), just let me know.
  3. @Chris B To add one more information: If i take only e.g. 11 RAWs and put them trough a parallel processing batch, they will finish, but this already takes ages: All files switch to "saving JPEG" very fast (approx. 5 seconds), but it takes more than one minute until the files are really saved. The RAM usage is around 29 GB (without cap) then.
  4. @Chris B Thank you for your answer. I tried reducing the useable amount of RAM to 16GB without success. As you can see in the Screenshot attached, Affinity Photo (updated to the last recent version 1.10.x today) will occupy the memory, but no picture will be saved (output folder is visible in the explorer). The status of the single files is "saving JPEG" or sometimes "loading" (see arrows), but no output is written. The programm can only be closed by using the Task Manager, because it will always say "processing is still active" when trying to close it.
  5. @Chris B Did you successfully receive the pictures i uploaded? Thank you in advance for your time.
  6. @Chris B I am just uploading 261 Z6 RAWs (.NEF) to the dropbox you linked in you post above. Those are "real" pictures taken but sorted out during processing after the event. Uploading will be done in about an hour. Even tough those pictures were taken at on open event, please treat them with the respective privacy. I hope those help and thank you for your support!
  7. @Old Bruce This folder was created by me and is a normal folder (not e.g. a temp file created by the application). This should have been explained by me, thanks for asking. @Chris B Thank you very much for your effort. If the problem cannot be reproduced or you cannot get your hands onto some Z6-RAWs, I could shoot a series of RAW-files without content (e.g. set to unsharp using manual focus) to get us some testing material?
  8. Hello @Chris B thank you for your answer and your time. Since the photos were made at a private appointment and nearly all of them contain people and therefore privacy has to be taken into account, I am sorry but I cannot upload them to even a private dropbox. I can deliver the batch settings of course (attached).
  9. Hello support, I am encountering a problem in Affinity Photo 1.9.2.1035 in Windows 10 20H2 x64. I want to process a batch of 245 RAW-files made with my Nikon Z6 (.NEF with a file size of 28-32 MB per file) with the following options: - Save file to a different folder - convert to JPEG using standard settings (quality 100) As long as I do not activate the "parallel processing" option, everything runs fine, but somewhat slow since the pictures are processed one by one. As soon as I activate the option, 32 files will be processed simultaneously (32 CPU Threads), but no picture will be saved. Every file will have the "I am working" animation (see marker in example image attached), but it will run forever. The RAM usage is approx. 43GB then. My machine contains the following parts: - AMD Ryzen 9 5950X (16 Cores / 32 Threads) - 64GB DDR4-3600 CL16 - Gigabyte X570 Mainboard - AMD Radeon RX6900XT 16GB - source disc: Samsung 1TB 980 Pro SSD (NVME) - target disc: Corsair MP510 1TB SSD (NVME) - newest drivers and Windows updates Is the "parallel processing" not working a normal behaviour? Is this option designed for machines with far more CPU cores (e.g. workstations with 64C/128T) or is this a probably a buggy behaviour? Thank you very much for your answer and your investigation. Regards from Germany!
  10. I processed a couple of pictures this evening using the beta-version 1.7.0.284. Until now, everything seems to be fine, but it is too early to draw a conclusion. I will report back in a few days. Thank you very much for your effords anyway. Can you tell me what exactly got fixed?
  11. Hello, of course, i will Check if it is fixed. Where can i get the Beta? Thank you very much. Regards, Lareneg
  12. Hello Mark, thank you for your answer and your time. As this machine is also used for gaming, the graphics drivers are updated on a regular basis. As i suspected the driver to be a problem, i already did a clean uninstall by using DDU (Display Driver Uninstallier) and installiing the last recent driver on a clean basis. What I determined on occasion as i am on holiday at the moment: The problem does also occur on my notebook and there is also a Nvidia-graphics-card involved. The laptop is running Windows 10 Pro x64 1809 on an Intel Core i7 7700HQ, 16GB RAM, Samsung S-ATA SSD and a Nvidia GeForce GTX 1060 6GB. Interestingly, the frequency of the problem occuring is faw lower than on my desktop machine. I processed approx. 40 RAWs until now and there was only one time where the sliders became somewhat laggy / little freeze. If there is anything more i can do to help ruling things out, just let me know.
  13. Hello Gabriel, thank you for your answer. I did as you advised me. You find the LatencyMon-Report attached. I processed some raws in my normal workflow. The issue was present (some laggy sliders and stuff), not as bad as normal, but it was there. It seems as if the Nvidia-driver is making some trouble there? Driver-version is from 01/2019, there are machines with newer and older drivers running fine at my place... Any ideas? Thank you for your further assistance! LatencyMon.txt
×
×
  • 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.