Gigapixel 8 taking hours on a 1 meg file?

Topaz Gigapixel AI Bugs and Issues
1

I’m running recover on a 1 meg file (that’s right, 1 meg), output to 1.2 meg.
It took hours and didn’t finish so I decided to cancel.
When I did - tada! the process completed, so I went to export.
Processing the export has been choking at about 98% for the last two hours.
This can’t be right…
Can someone tell me what I might be doing wrong?
MacBook Pro, M1, 16g ram, 330g available on my internal ssd.
Using Gigapixel 8.0.0 stand alone.

2 Likes
2

…why do I hear crickets?

1 Like
3

I have the same issue on my iMac

1 Like
4

Yep… same here, mines basically unusable
MacBook Pro, 8 core, 16Gb ram, M1 Pro , 14 core GPU, Metal 3

5

Can anyone from Topaz offer a suggestion?
Or should we talk refunds?

            ...Beuhler?

                        ...Beuhler?
6

Hello.

IMO, 'cause it’s the same story, for many MAINSTREAM 3rd-party software (minus in-bed Apple’s SUPER CLOSE partners… e.g. Adobe, ect.) that many Apple’s devices underperforms very often.

7

Well the earlier version worked incredibly well, Topaz sharpen and Denoise work efficiently and produce great results as well as every other single program on my computer … so I doubt its that

8

Turns out, "recover’ is best used on under 1000 megapixels.
So very lo-res images.
yikes…

9

1000 pixels. Also on larger images it fails silently, the UI spinner keeps spinning and the process in activity monitor looks fine but in reality it will spin forever and the process will never complete.

1 Like