That’s even weirder given Gigapixel having 0.5x, 2x, 4x, 6x in the UI - would make more sense to stick to AI model presets and I certainly use 1x more than 0.5x and why 6x is generally worthless.
Same happens in video enhance, the HD, 4k, etc resolution sizes don’t necessarily correspond to the AI model sizes.
There is at least some logic there, if you are mastering for a resolution standard. Although I’d argue still better off letting your production software do the final scale. I don’t see the logic in wasting space on plain upscaling before the final pass (or at all if you aren’t targeting a specific resolution for a good reason).
Even if I have chosen to use my GPU to upscale the images, Gigapixel insists on using my CPU cores which are very slow. I double checked it from the activity monitor - my GPU is idle. I didn’t have that problem when I had version 5.5.2, in fact the process used to be super fast. Now I have to wait ages for a single photo upscale.
Application & Version: Topaz Gigapixel AI Version 6.2.2
Operating System: macOS 12.6
Graphics Hardware: AMD Radeon VII OpenGL Engine
OpenGL Driver: 4.1 ATI-4.8.101
CPU RAM: 131072 MB
Video RAM: 2047 MB
Preview Limit: 4492 Pixels
1 Like
Gigapixel just doesn’t know how to use modern hardware. It’s like it was written in 2003.
2 Likes
Hello, I am using Gigapixel AI to scale up an hdr file of a sky. When exporting the image and then reading it in Nuke, i get a bounding box error. Do you have any ideas why this problem occurs?
They found the software in a time capsule from 2003, and thought they could get away with releasing it in 2022. 
1 Like
His 2 GB Vram is like 2007.
Not far off:
Radeon HD 5870, Sep 23, 2009 - Size 2048 MB
I tried out 6.2.2 and found no significant improvement compared to 5.7.1 I used to run before. But I found something I consider a weird bug: If JPG is chosen as output format, an image of, say, 9 Megapixel is saved as a JPG roundabout 1,5 MB in file size, with the respective compression artefacts clearly visible. Saving the same file as PNG will yield a result of 8 MB in file size.
Am I the only one experiencing this issue? If not, when can we expect this to be fixed?
I have a 2021 6700XT with 12GB and get the same result.
Is your driver up to date?
Have a Radeon too and it does work.
Oh its all up to date and runs fine with everything else just Topaz software (Gigapixel and VideoAI) just give worse and worse performance with every version. Been using the software around three years now. I refuse to pay any more subs until things appear to improve.
As I’ve mentioned I don’t want to run one video or picture list at 33% CPU/GPU resource. I (and others it seems) want to be able to throw all the computing power I have in one go. Why do one thing over an hour at 33% when I could do it in 20 mins at 100%?
I just downloaded Gigapixel 6.2.2. The big window comes up. I drag .jpg into it and boom.
| Model Name: | Mac mini |
|---|---|
| Model Identifier: | Macmini8,1 |
| Processor Name: | 6-Core Intel Core i7 |
| Processor Speed: | 3.2 GHz |
| Number of Processors: | 1 |
| Total Number of Cores: | 6 |
| L2 Cache (per Core): | 256 KB |
| L3 Cache: | 12 MB |
| Hyper-Threading Technology: | Enabled |
| Memory: | 32 GB |
I have the crash report.
You need to check with the Nuke support as to what they are looking for in the app, or try PNG as the export. Nuke is a video editing app.
I’m using it for Hdr images which I think Png doesn’t support though?
What is the image type you are exporting from GigaPixel?
Tried tiff and dng that I think support Hdr.
I would have thought TIFF would be ok because it has an Alpha channel.
Maybe you can check on the Nuke forum and maybe @alexander.zhang can help here.
Hello Support, I’m working with Gigapixel AI 6.2.2 on a Mac Intel running macOS 13.1. I’m having the problem since a few days that Gigapixel crashes when calculating a whole image or saving an image. Can you please fix the problem as soon as possible? Thanks a lot
A Merry Christmas wishes
Holger Schrader from Germany
Uploading: TopazGigapixelAI_Logs_2022-12-20-11-07-16.zip…
Here the log file
