Gigapixel v5.0.3

Download: Windows, Mac
Released July 22, 2020.

Major Features

  • Full Lightroom support for Windows and Mac
  • An in-app survey will be displayed periodically, to help us better get an idea of how users are liking the software. Your feedback is always appreciated!

Improvements

  • Zoom hotkeys in the view menu have been changed to Ctrl+(0 through 4), from Ctrl+(1 through 5), to better mirror the hotkeys in other Topaz photo-editing programs

Fixes

  • “Image Type” button will now be disabled, and default to “Natural” when “Use maximum quality AI models” is turned off in the Preferences
  • Cancelling while batch processing now actually cancels processing - previously, the UI would say it has been cancelled but it would continue processing in the background
  • Preview no longer auto-processes when auto-update preview is off after cancelling the preview processing
  • Preview does not show a small overlay of the original image when processing

If you have any issues using this version such as crashes, hangs, metadata issues or other errors, you can submit your logs and test images here . The images used when an error occurs are always helpful for us when pinning down what the issue is.

3 Likes

Giga Pixel Showing Incorrect Blur About in Status Bar.

Uploaded test photo .And Addional Test Photos.

Application & Version: Topaz Gigapixel AI Version 5.0.3.0

Operating System: macOS 10.15

Graphics Hardware: AMD Radeon Pro 580 OpenGL Engine

OpenGL Driver: 4.1 ATI-3.10.15

CPU RAM: 16384 MB

Video RAM: 2047 MB

Preview Limit: 4492 Pixels

Please bring back V 4.4.5 quality models. Here is a comparison view. Original at left, resized X2.5 using CPU with Open VINO enabled with auto settings. Middle=V 5.0.3 (natural) , right=V 4.4.5
The comparison image also has been resized X3 using bicubic method for a better view.
V 5.0 is not even close to v 4.4.5 quality. It is blurry with lot of chroma noise

original size of comparison view : compare

3 Likes

Yes I also noticed that the 4.4.5 version delivered better results.

1 Like

Openvino results are more blurry than CPU mode only. Try disabling Openvino.

Do not put in “in app surveys”. It is absolutely amazing to me that in the year of our Lord 2020 there are developers who still think that interupting the user experience is a good idea.

4 Likes

Is there a list of Lightroom versions that are supported?

I compared the options CPU, GPU and OpenVino and can not find a noticeable difference in the results.

I have tried to install on OS X Catalina (latest version) on a 2015 MacBook Pro. During the install permission error prompts appear. Only out is to cancel the update. Anyone else on a Mac having install issues?

Hi Patricia,

These are the currently supported versions of Lightroom on Windows and Mac, for all Topaz products that have Lightroom support:

  • Lightroom 4-6
  • Lightroom CC 2015-2016
  • Lightroom CC 2019

If your version’s not on this list let me know and I’ll see what I can do. Also, let me know if you run into any issues using it with Lightroom. Note that if you’re on Mac, you’ll have to run Gigapixel at least once as standalone to get it to install the Lightroom plugin (annoying I know, but only need to do once unless you completely reinstall the software. No need to do it every update).

Thanks!
Taylor B.

Hi Chase,

We’ve attempted to make this survey as unintrusive as possible. You can permanently disable it after the first time it pops up, and it shouldn’t interrupt workflow. If you notice it getting in the way, definitely let me know.

As Imo and sumsar mentioned, disabling OpenVINO should make it crisper. We’ve got plans in the works to fix this issue permanently, but it will take some time.

Hi JesusSheep,

This is an issue with your resolution setting - our GUI framework has issues rendering correctly at higher resolutions (you’ll notice you have to scroll the right panel at higher resolutions, but not lower resolutions, which is counter-intuitive).

We’ve got an upgrade to the framework on our roadmap that should fix this.

Hi risingleo,

Do you by chance have Topaz Studio 2 installed on your machine? We’ve seen this issue before with users (typically related to a corrupted TS2 install) and have a help article that should fix the issue.

If that doesn’t work, definitely let me know. The easiest route is deleting the Topaz Labs LLC folder entirely and re-installing. Apologies for the frustration!

Thank you! I have LR6, so I’m happy to see it on this list. I won’t have a need for testing it until next week, but will let you know if I have any additional questions or concerns with that.

Are you suggesting the example shown for version 4.4.5 is crisper because it had OpenVINO turned off? Or, that there is a bug with OpenVINO in version 5.0.3?

Prior to today I’ve not had a situation where I only wanted to process around half of the images dumped into the list. What I found was that the program pays no attention to whether an image is selected - it processes them all in order.

In this instance I dumped them into the list as an easy way to see which ones were small, so I could process them only. My preference would have been to select the ones I didn’t want and remove them, but I haven’t found a way to do that. You have to x each one out individually and answer the cursed “Changes to this image have not been saved” dialog. If you are going to make us do that, please add a “Don’t show this again” option!

So, two problems. Selection doesn’t matter, and no way to batch delete.

Batch delete:
Taylor, there is a check box on the left side of each image. If the box is not checked, why does it get processed anyway? Unchecking the box should skip this image in the save process. Perhaps you can add that to an update.
I have done a number of images scaling with people in them and the latest release does an excellent job on most of them.

I noticed something interesting:

  • Original image, zoomed 4x:

  • “Treated” with stable 5.0.3.0:

  • Processed with 5.0.3.1b:

options used:

options2 options1

Hmmm… OpenVINO seems to make image really sharp and introduces a bit of blue-ish artifacts in white parts in stable GP version, whereas turning it off in stable GP gets me results EXACT to the beta OpenVINO:

If turning OpenVINO off gives crisper result (mentioned above by @taylor.bishop), then either in beta the “boolean” of OpenVINO is “swapped”, or the libraries differ. :slight_smile:

Great observation, thanks.