@alexandre.topazlabs the sizing issue, is still persistent in this release, look at my file details of an image. 4061x2613 original size upscaled to 10000x5226, but then it outputs 8122x5226px, I think it’s still remembering the last size output by default. Something still isn’t right with this. Ask your dev team to test with 2x different image dims, and output to replicate the issues
1 Like
Cloud rendering is not working after updating to v1.0.7…. Dont know if its just me or others as well??
1 Like
Same here
You are right, this issue is still open on our side and we will reach out when it’s fixed 
- It should technically be in the next version if all goes right.
Are you using Redefine + grain? We are tracking an issue with that at the moment, and we have already released a first fix. Can you try again today? It worked for me.
I thought Gigapixel was a professional tool for professionals. When I need to work, it’s unfortunately 50/50 whether the cloud will work or not. Right now I’ve been waiting for a few hours for the render and the wheels are still spinning. Yesterday it was only possible to send individual files to the cloud, two or more did not activate the Cloud rendering button. I have version 1.0.5 and I don’t have the courage to update when I read about other problems here. Do you release semi-finished products into the update and then iron out the mess on the fly? I thought as a paying client that I could rely on your services!
The issues from the past few days are now resolved. If you are still experiencing issues with cloud rendering, please contact us at help@topazlabs.com so we can investigate.
2 posts were split to a new topic: Feedback | Cloud rendering process
When will the model “Sharpen Wildlife / Portrait”, rolled out in Topaz Photo, be available in Gigapixel… will it be there at all?
Hi.
Sorry strictly for Topaz Photo only because, their part of Photo’s Sharpening capabilities which Gigapixel doesn’t have
Hope this helps
1 Like
A model that yields better results with animal pictures than the existing ones was announced weeks ago in the GP Beta thread, no new Beta since. My subscription runs for another 11 months, and if there is no substantial improvement in rendering animal fur (Redefine is a joke in that respect, and Wonder brings no improvement in comparison to the non-AI models), this first subscription period will be my last one. None of the newer GP models performs better than those in GPAI 8 when it comes to fur texture. And those who already use stand-alone AI generation such as Flux or Stable Diffusion should have a look at SeedVR2, an upscaler for ComfyUI which is powerful, fast and free. If the devs go on treating GP as a project that comes last behind VideoAI and PhotoAI, it is probably going down the drain due to a decreasing base of subscribers.
Interesting, I’m not a Beta Tester hence, I wouldn’t be privy to the information within the Beta Thread so, could only go on the information I have and from what I knew therefore, both the new Portrait and Animal Sharpen Models were placed in the Sharpening Section within Topaz Photo which Gigapixel doesn’t have so, from my point of view I was correct.
Also, you mentioned something about Topaz failing to Upgrade Gigapixel in a long time admittedly, there hasn’t been any Upgrades since the transition from Gigapixel AI to Gigapixel Studio when Standard MAX and Wonder were added not forgetting Unlimited Cloud Image Rendering plus, half a dozen patches since then.
Just remind me when was that again the transition was in September and it’s now December a mere few months ago so, a life time ago then.
Please bear in mind, also, that both Topaz Photo and Video have had major Releases recently to versions 1.1.0 so, one can assume a 1.1.0 Release for Gigapixel is pretty much imminent and who knows they may add Portrait and Animal Sharpening to it.
You also, mentioned Gigapixel as being the poor relation of both Topaz Photo and Video as though it had been abandoned by Topaz not your words exactly but that’s what you were referring.
Topaz Photo had two patch releases
Topaz Video had four patch releases
Topaz Gigapixel had several patch releases so, Topaz Gigapixel has been worked on the most then and therefore, far from being abandoned.
Lastly, you referred that lots of Topaz customers have left since the transition, how do you know this because, you’re read it within the Transition Topic many people were dissatisfied and were going to leave Topaz.
I beg to differ, it would be interesting if Topaz released the information on how exactly how many customers actually left, how many stayed and how many just saw a dam good deal and just got on with it.
But, I know Topaz, won’t release that Data because, one why should they and two what would be the point they have nothing to prove to you, me, or anyone else for that matter.
At the end of the day if you want to leave because you’re not happy that your decision to make
Hi,
I’ve noticed a very annoying bug in version 1.0.4, and it persists in 1.0.7. This bug occurs with Recover V2 on 12 or 12.5 megapixel photos. If I double the resolution using the “none” setting, I get a really bad result, as if I were using the low, medium, or even high resolution settings for certain types of images. This is the kind of bug I’ve never seen in older versions of Gigapixel, and even less so in the latest version 8.4.4 of GAI. To fix this problem, I have to quadruple the resolution. This results in a really huge image when I only want 50 megapixels from a 12-megapixel photo.
Here is an example for the demonstration
So here’s what happens when I multiply a portion by 2, knowing that I get this result if I multiply the entire image.
And now, look how much better it is with the x4
But look at the resolution of the output image I have to deal with for this. I’ve never seen anything like it before.
Also, to better observe the problem, here is a test between the result of the preview in small mode and the preview in large mode.
Look how well the details are on the pattern or on the writing or even on the chrome decoration on the right of the photo with the small preview.
And now look how awful it is with the full preview. (By the way, when I preview the entire image, it’s the same quality as the full preview.)
It looks like I used the medium or high settings in Recover v2. The modification on the sleeve of the black coat is just awful. I’ll try again with version 8.4.4. But I’m sure the result will be better with the same settings.
Edit,
I retested with version 8.4.4 and found the same problems. It’s crazy. The small details are ruined. I had to scale the image down by 4x to fix it. But then it takes me twice as long to render. My source files are JPGs. I don’t think the file format is the cause. That would be really strange.
Edit 2,
I tested it out of curiosity with the CPU. The details are even more destroyed with x2.
Before
After
Recover v1 appears to be broken
I’ll see if it still works on version 8.4.4
Edit:
Version 8.4.4 worked very well.
If the results are the same in Gigapixel v8.4.4, this means that either you are not using the right model, or the image in question is lacking details, and this is why you get artifacts. If you want, you can contact us at help@topazlabs.com, and we can help you test this image
Ok, I’m going to send you one of the same photos. Because in the one I showed with zoomed-in sections, there’s a person I don’t want to share. So the one I’m going to share has the same problem, but at least there’s no one in it.
But look here with the small preview. It seems to work. And yet, as soon as I show it with the large preview (which will be the same as the full image), the quality is noticeably worse.
Look here at the large preview; it’s clearly much worse. Very noticeable in the text and small details.
To get something decent, you have to do at least x4. But look at the resolution I have to tackle. It’s just enormous.
A post was split to a new topic: Feature request | abreviations for models in output file name instead of the full name
Is it just an issue with the preview, or the photo has also issues after processing and exporting?
It’s the same for both the preview and the export. I had to increase the scale by a factor of 4 to get the result I obtained when using the small preview mode.
I’d never noticed this problem before because I usually always used the native camera app on my Galaxy S25 Ultra, which delivers a 50-megapixel image but actually captures a 12-megapixel image upscaled to 50x at the time of capture. For the example above, I used another app that provides a true 12-megapixel image of better quality. And that’s when I noticed the degraded quality issue when I applied a 2x upscaling factor. Also, if you want to test it, I use the external photo application which is “Camera FV-5 Pro”
A post was merged into an existing topic: Model Downloads | 403 Error Appears
