We’re planning on overhauling the calibration option soon, so it’s easier to use / more verbose on quality vs. speed. Currently, calibration only picks the options for best possible performance, not quality. I agree that it’s non-obvious and a bit confusing.
If you’re only concerned about best possible quality, you can disregard calibration entirely, unless you use OpenVINO for processing and have a CPU capable of using it. Some people think OpenVINO quality is better than raw CPU processing, but your mileage may vary. Calibrating will enable the option if it’s disabled and you have an Intel CPU that can use it. You’re free to change the settings after calibration, nothing will stick around that you don’t intend (it didn’t in the previous version either, but it looked like it did).
The GPU artifacting issue will be fixed early next year when the new AI engine going in VEAI gets migrated into the image-editing applications. Currently, Gigapixel’s GPU processing is on a very old custom-built OpenGL engine and our ML engineers have looked into it and haven’t been able to fix it, without rewriting the entire engine. The new AI engine will throw that out entirely for a much better, faster (magnitudes faster) processing library. It will take some time though, and is currently being tested in VEAI.
