

jpg Lines 1 and 2: from PIL import Image Python Image Library - Image Processing import glob.

#How to convert cr2 to jpeg windows 8 code#
I haven't tested this theory (and not going to Affinity needs to do their own testing), but I suspect a batch process with more images than processors available, or some multiple of cores/processors) is the culprit in the code base. Convert the image file to a different format ( RGB) Finally save the file with the new extension.And actually converted as fast, if not faster than parallel processing when testing with small batches, re: small batches of 5 or so images did not crash the system. Once I disabled "parallel processing", the conversion process completed without error. The underlying issue is Affinity Photo is defaulting to "parallel processing" (small checkbox in the lower left of the batch convert UI) and the code is not correctly managing the parallel process. While monitoring the conversion process, I noticed the CPU spiked and maxed out, as well as RAM through the roof. Same issue with crashing while batch converting several CR2 files to JPEG (or really any exported format). Some tasks ask a lot of a computer, sometimes I think, more than what we think they're capable of. Might ask why do that? To get the job done, without having hanging and crashing,= fewer headaches. I learned this from a college, where the profile would have the bare minimum services running.

Just a side note I learned years ago, while I was a moderator and then Administrator for Corel (originally Ulead) help forums, to set up a profile to edit videos using their programs, Ulead MediaStudio Pro, and VideoStudio. *My video card Nvidia GTX 645 does not qualify for the OpenCL so it was not enabled. I also ran them with and without Parallel Processing enabled. I tried both saving the converted files to the same drive as the CR2 files, and to an USB external drive. Knowing this would be very heavy task for my old machine, I done the following before running the batches. I had task manager running during this, and noticed my Memory usage did climb to around 12,000+ MB, CPU of course at %100, GPU only around %4. FWIW, I have not had any hanging while batch converting CR2 files to jpg.
