This brings my laptop into a complete halt towards the end of the upscaling process, I had to wait for a few minutes and only after the finishing touches of the process is finished that my laptop comes out of a hang state.
Like it has been reported earlier, there doesnât seem to be a way to turn off GPU processing (it immediately turns itself back on once you close the settings). Worth a hotfix right there. Also, I got lucky this time since I purchased Gigapixel in December last year (though lifetime updates were still being advertised when I bought it), but I sure hope this AI model that is meant to solve color shifting isnât going to be paywalled behind another âmajorâ release. This is an issue that existed since I bought the software.
If you read the thread the developer has already said
âThis is a graphical glitch, if the âAllowed graphics memory consumptionâ button is greyed out then youâre not using GPU mode.â
Except that it in deed used GPU, as I said, my upscaled started to have specific artifacts that are only done when GPU is on.
Anyway, 5.1.7 works fine with me, so I can wait until this part is definitively fixed. This part must be reliable for the user, especially when a single upscale is about 9mn to render. Batch processing saves time, I donât have time to spend hours to check every upscale after.
You guys try to fix problems as soon as possible, thanks but this kind of issues should not be here at every update.
Oh, and please make perpetual licenses please. I want to possess my software, thatâs why I donât have any Adobe software, if you see what I mean⊠I mean, Iâm OK to have to pay for a year maintenance, but if I stop I want to continue to use my version anyway. Is that the case ?
1 Like
Where can I find it here, to test it ? The available downloads seem to start at 4.5
Thanks !
You have a perpetual licence.
Cool, thanks.
Loving the new update to Gigapixel. one issue though. I can go straight from lightroom to edit and crop but when I go to photoshop, then try to go into gigapixel to edit and crop, the crop function doesnât work. I prefer to do it via photoshop because when I want to export a photo at a particular size, it gives me a preview of what it looks like. Is there anything that can be done to fix this? Thanks
Contact Topaz support at the main website and ask them to send you a download link to the installer. Thatâs how I got mine back. It wonât delete the newer version, so you can use both if you wish to compare.
For your second request, a simpler way might be to do a custom finder search inside your folder for all images 600px wide and then select all and drag them into the Gigapixel window.
It cannot be âfixedâ as the image is a fixed size that is passed from PS and the canvas cannot be adjusted in GigaPixel as it only sees a image whole.
Many thanks, Iâll do it.
For what Iâve tested so far the compressed model seems good on âout of focusâ background things but when it come to the main âin focusâ subject it seems very polished and details that the standard model produces are lost. Itâs disturbing to have models that produces unequal quality on the overall image. Like for having the best result you will have to render both then making a composite in your Photoshop/editing software and taking the best parts from each model. This can work if you absolutely want a specific image to look the best possible but you canât do this on hundreds /thousands images you will process.
Now if we could have what v4.4.5 produced on main focus objects and what v5.2.0 compressed produces on out of focus objects then we would have very good results.
1 Like
Iâve noticed the same about Compressed mode. I have actually done some tests, combining a Compressed render with a Standard render in Photoshop. Relatively a painstaking process, but the results were decent. As youâve stated, itâs not practical for processing many images, so I am hoping the Compressed model will become more refined in future updates.
1 Like
The best could be a kind of layer set.
You open a photo, then you had layers.
For each layer you have a different settings, and you can use brushes like any photoshop/gimp like, to choose what you want to keep or erase for the final result.
Plus, you can save the settings/layers/brushes/masks in a file in order to be able to come back later and change things.
More confusion. The new update(5.2.1). Itâs not clear to users that if the âCalibrateâ button is highlighted in preferences what will then happen upon loading an image is that Gigapixel will enable GPU mode without notifying the user. And will upscale with the GPU resulting in the output with graphical artifacts like red stripes and blurriness. And to be honest these artifacts have been there since day one. Canât believe they still havenât been fixed.
Personally im not interested in best performance, or what i call the âquick and dirtyâ GPU mode, im interested only in having the best quality output.
I think i would be better to have a quality slider from low to high which selects CPU mode for highest quality and GPU for lowest. Then the user would not need to mess around trying to decide which processor is best to use.
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.
5 Likes
Exactly, thatâs pretty much what I did, I put the Compressed render on one layer, the Standard render on another layer and then played with opacity, brushes, etc.
Thanks for the fixes.
One question, maybe itâs dumb : Many programs like RAW programs (Rawtherapee) or other (Gimp, Photoshop I guess) can or do work in 32 bits floating point. As itâs way more precise than working in 16 bits integer, could it be possible in a near future that AI could work in 32 bits, for better accuracy/quality ?
I didnât realise the search on Mac could do that, Iâll look into it, thanks.
