Macbook M4 pro max. Crashes on batch jobs after between 5 and 20 images processed. Usually resumes correctly when Photo AI is restarted but sometimes gets stuck on a picture which then is processed normally after restarting Photo AI. The pictures are 20 MP NEF images from Nikon D500 camera.
I added you to the thread where we discuss the issue you have. For now you need to revert to the previous version of Photo AI until we release a fix for this (See solution above)
Just for clarification. I do not have a batch editing issue. I edit photos one at a time out of LRC. I will edit my photo in LRC and right click and select Edit in Topaz. When finished with my edit in Topaz I will export back to LRC. I do this one photo at a time. Approximately every 5th photo while waiting on Topaz to open the photo I have selected to edit Topaz will simply send the JPG back to LRC without me even seeing the photo to edit in Topaz. I will delete the unedited JPG from LRC and attempt to edit the same photo and this time Topaz will open the photo I had selected to edit but it will hang on Analyzing and I will be forced to Quit Topaz. Then on the third try I will have no issue editing that same photo. I hope that clarifies. But I will revert to 4.0.1 as suggested, thank you
Hello Topaz Ai
Lately I’ve been getting crashes almost every time i used Topaz Ai on my M3 macbook, I have tied changing the preferneces to CPU and back with no relief. It is frustrating as it happened more and more. I am only processing afew files < 30 JPEGS only. This has never been an issue until recently
Is there a fix, please advise, thank you.
When processing files using autopilot, the program always crashes after a few files. Since I am trying to process 300-600 files at a time, this has rendered the program non functional.
Having the same issue on 4.0.2 on M1 Ultra 64GB/Sequoia 15.5. Won’t do more than 20 .jpg before hanging then crashing. Per instructions above I downgraded to 4.0.1 and so far it’s 450 images into the 4800 I was trying to batch. Yay.
BTW, thanks for your transparency on this issue. The thread took a little while to find, but I appreciate you acknowledging it and offering a reasonable and functional workaround. Most ISVs pretend their software is perfect, which leaves you in quite a quandary when it fails.