# Gigapixel v7.4.4

**URL:** <https://community.topazlabs.com/t/gigapixel-v7-4-4/78991>\
**Category:** Releases\
**Created:** [October 2, 2024, 7:20pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991 "2024-10-02T19:20:33Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![esther.huynh](https://community.topazlabs.com/user_avatar/community.topazlabs.com/esther.huynh/32/211052_2.png) [@esther.huynh](https://community.topazlabs.com/u/esther.huynh)\
**Post date:** [October 2, 2024, 7:20pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/1 "2024-10-02T19:20:33Z")

</div>

Hello!  
This is a fairly small update compared to our last release. We hope you’ll continue to report your results and share your feedback with us.

Thank you!

* * *

**v7.4.4**  
Released October 2, 2024  
Mac: [[Download](https://downloads.topazlabs.com/deploy/TopazGigapixelAI/7.4.4/TopazGigapixelAI-7.4.4.pkg)]  
Windows: [[Download](https://downloads.topazlabs.com/deploy/TopazGigapixelAI/7.4.4/TopazGigapixelAI-7.4.4.msi)]

* * *

Changelog:

- Fixed images with 90/270 degree orientations not working in Gigaprint
- Fixed a minor memory leak when using tablets for panning
- Fixed being unable to close print error dialog

---

<div class="post-metadata">

**Author:** ![david.123](https://community.topazlabs.com/user_avatar/community.topazlabs.com/david.123/32/163156_2.png) [@david.123](https://community.topazlabs.com/u/david.123)\
**Post date:** [October 2, 2024, 7:23pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/2 "2024-10-02T19:23:36Z")

</div>

Hi Esther,

Can you please comment on the ETA of the quick export button?

Thanks

---

<div class="post-metadata">

**Author:** ![mtjk619](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/m/3da27b/32.png) [@mtjk619](https://community.topazlabs.com/u/mtjk619)\
**Post date:** [October 2, 2024, 8:07pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/3 "2024-10-02T20:07:04Z")

</div>

Hi, when is the batch face recovery issue going to be fixed? I noticed it on 7.4.3 and even 7.4.4 doesn’t work. Thanks.

---

<div class="post-metadata">

**Author:** ![esther.huynh](https://community.topazlabs.com/user_avatar/community.topazlabs.com/esther.huynh/32/211052_2.png) [@esther.huynh](https://community.topazlabs.com/u/esther.huynh)\
**Post date:** [October 2, 2024, 8:13pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/4 "2024-10-02T20:13:38Z")

</div>

This one is on the docket to be fixed. Thank you for checking in!

---

<div class="post-metadata">

**Author:** ![alanhusband-677420](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/a/7ba0ec/32.png) [@alanhusband-677420](https://community.topazlabs.com/u/alanhusband-677420)\
**Post date:** [October 2, 2024, 9:16pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/5 "2024-10-02T21:16:14Z")

</div>

Have the same issue with this release, as reported for the previous release.

> [@Gigapixel v7.4.3](https://community.topazlabs.com/t/gigapixel-v7-4-3/78196/4):
>
> I noticed that most models are carrying out the upscale twice, which becomes a major pain with the recovery models. [2024-09-19-08-30-8.tzlog](https://community.topazlabs.com/uploads/short-url/9Tpn2j5xuFNxc215DcWSVf4JbiI.tzlog) (220.9 KB)

---

<div class="post-metadata">

**Author:** ![samb15](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/s/b38774/32.png) [@samb15](https://community.topazlabs.com/u/samb15)\
**Post date:** [October 2, 2024, 9:45pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/6 "2024-10-02T21:45:01Z")

</div>

PLEASE NOTE:

This is the first GP that has the new EULA with terms that are not agreeable to many of us here. If you load this you are changing the legal relationship between yourself and Topaz. Check with your lawyer if you are not sure.

Oddly, this was not noted in the Changelog.

…Sam

---

<div class="post-metadata">

**Author:** ![david.123](https://community.topazlabs.com/user_avatar/community.topazlabs.com/david.123/32/163156_2.png) [@david.123](https://community.topazlabs.com/u/david.123)\
**Post date:** [October 2, 2024, 10:07pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/8 "2024-10-02T22:07:38Z")

</div>

Alright, since my question was ignored, it’s time to break out the meme of shame:

![82f0d6b1f017f6331825e54a674bb39b714f43bd](https://community-cdn.topazlabs.com/original/3X/5/b/5b53950481ed2bac2bfa154f2ac05bb5ea66142e.jpeg)

---

<div class="post-metadata">

**Author:** ![esther.huynh](https://community.topazlabs.com/user_avatar/community.topazlabs.com/esther.huynh/32/211052_2.png) [@esther.huynh](https://community.topazlabs.com/u/esther.huynh)\
**Post date:** [October 3, 2024, 7:24am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/9 "2024-10-03T07:24:45Z")

</div>

Hi David,  
Apologies on missing your first comment. Meme of shame warranted.

I spoke with our product team and the quick export button will not be coming back for the time being - only because we are discussing on how to improve the overall export process for future iterations and how we can really improve on it.

So although it won’t return, please know we are working on bringing something better.

Feel free to continue sharing your thoughts in the Ideas section about it though!

---

<div class="post-metadata">

**Author:** ![esther.huynh](https://community.topazlabs.com/user_avatar/community.topazlabs.com/esther.huynh/32/211052_2.png) [@esther.huynh](https://community.topazlabs.com/u/esther.huynh)\
**Post date:** [October 3, 2024, 7:25am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/10 "2024-10-03T07:25:14Z")

</div>

@amy.mae could you take a look at this log?

---

<div class="post-metadata">

**Author:** ![esther.huynh](https://community.topazlabs.com/user_avatar/community.topazlabs.com/esther.huynh/32/211052_2.png) [@esther.huynh](https://community.topazlabs.com/u/esther.huynh)\
**Post date:** [October 3, 2024, 7:26am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/11 "2024-10-03T07:26:34Z")

</div>

Hi samb15,

The new EULA changes were first mentioned in our release post for 7.4.3 in the Changelog.

---

<div class="post-metadata">

**Author:** ![samb15](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/s/b38774/32.png) [@samb15](https://community.topazlabs.com/u/samb15)\
**Post date:** [October 3, 2024, 7:57am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/12 "2024-10-03T07:57:50Z")

</div>

I did see that, but the installer for 7.4.3 (and at the time, the Topaz website) still had clean and reasonable terms for the EULA on that release. The troublesome language did not appear until this installer, so I was careful to back out before agreeing or installing, and to delete the 7.4.4 file from my computer.

…Sam

---

<div class="post-metadata">

**Author:** ![Paul\_Coddington](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/p/b782af/32.png) [@Paul\_Coddington](https://community.topazlabs.com/u/Paul_Coddington)\
**Post date:** [October 3, 2024, 8:58am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/13 "2024-10-03T08:58:38Z")

</div>

For me, it would speed up export a lot if we could have dimensions that are not aspect ratio locked in which we can specify exact pixel counts.

Currently, images which should be, say, 2160x1440 cannot always be specified (they will be out by one or more pixels in one dimension) and even when we can specify them, the export itself can also be out by one or more pixels from what was specified.

It is difficult second-guessing entering, say 2163x1442 in the hope we can accidentally hit 2160x1440 on export, or at least crop it back to 2160x1440 after export.

I think the root of the problem is that smaller images are rounded to the nearest pixel which can cause errors when scaling up.

---

<div class="post-metadata">

**Author:** ![jamie\_wood](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/j/a88e57/32.png) [@jamie\_wood](https://community.topazlabs.com/u/jamie_wood)\
**Post date:** [October 3, 2024, 9:07am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/14 "2024-10-03T09:07:55Z")

</div>

It doesn’t look like this is going to happen. It was there in an earlier release of V7, so I would have thought it would be easy enough to reinstate. Best get used to many, many clicks…

---

<div class="post-metadata">

**Author:** ![jamie\_wood](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/j/a88e57/32.png) [@jamie\_wood](https://community.topazlabs.com/u/jamie_wood)\
**Post date:** [October 3, 2024, 9:12am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/15 "2024-10-03T09:12:07Z")

</div>

I can’t see what could be more simple, than one click to export, and done, rather than the three clicks currently used. Every single time.

---

<div class="post-metadata">

**Author:** ![david.123](https://community.topazlabs.com/user_avatar/community.topazlabs.com/david.123/32/163156_2.png) [@david.123](https://community.topazlabs.com/u/david.123)\
**Post date:** [October 3, 2024, 4:51pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/17 "2024-10-03T16:51:43Z")

</div>

> [@esther.huynh](#):
>
> I spoke with our product team and the quick export button will not be coming back for the time being - only because we are discussing on how to improve the overall export process for future iterations and how we can really improve on it.
> 
> So although it won’t return, please know we are working on bringing something better.

It’s not a case of ‘better’ - we just need to reduce the unnecessary clicking!

Current click count to export a single image:

1. If using recovery model - once to clear the ‘large image recovery warning’
2. Once to invoke the export dialog
3. Once to start the export
4. Once more to close the dialog

Don’t you see how insanely arduous this is on the users?

If you actually care about your customers concerns, PLEASE:

- Put a check box on the ‘large images warning’ for recovery exports that allows us to ‘don’t show this dialog again’.

- Give us a quick export option! I want to export via a single click, just like in Photo AI, where the product team actually realizes the benefit of it!

I will likely be cancelling my subscription if these items are not actioned before it’s time to renew.

---

<div class="post-metadata">

**Author:** ![plugsnpixels](https://community.topazlabs.com/user_avatar/community.topazlabs.com/plugsnpixels/32/193237_2.png) [@plugsnpixels](https://community.topazlabs.com/u/plugsnpixels)\
**Post date:** [October 3, 2024, 9:23pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/20 "2024-10-03T21:23:32Z")

</div>

Today’s quick use of Face Recovery with the new 7.4.4 build on 1990s 35mm film scans.

Without **[Gigapixel](https://www.topazlabs.com/gigapixel/ref/5/)**, my old photos are pretty worthless… Film scans of negatives going back decades, 20-year-old lo-res digital images, etc.

All I might ask for in GP is a Levels dialog rather than the less useful Gamma correction option.

 ![gpgroup](https://community-cdn.topazlabs.com/original/3X/3/1/3196d27dec7ba148c226d8e2b33489871b9ddedd.jpeg)

 ![gpman](https://community-cdn.topazlabs.com/original/3X/9/e/9e414665e64a3ec34d7b562e84fff77becc9c263.jpeg)

 ![gpclinton](https://community-cdn.topazlabs.com/original/3X/3/a/3a5c62574b22ba6bf6a4c5aa084263a1e5e7ca75.jpeg)

 ![gpduch](https://community-cdn.topazlabs.com/original/3X/0/3/0315d61ee0692540c05e1ef1725f30f5e918f1ac.jpeg)

---

<div class="post-metadata">

**Author:** ![vincentabel42](https://community.topazlabs.com/letter_avatar_proxy/v4/letter/v/f1d935/32.png) [@vincentabel42](https://community.topazlabs.com/u/vincentabel42)\
**Post date:** [October 3, 2024, 9:38pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/21 "2024-10-03T21:38:03Z")

</div>

Hello.

Just curious, Bill looks a bit cooler (blue, yellow or green saturation added) than the warmer side (tropical orange ha-ha) still.

Did you apply any color correction, ect. to these stills or are these results from the Giga native processing?

---

<div class="post-metadata">

**Author:** ![plugsnpixels](https://community.topazlabs.com/user_avatar/community.topazlabs.com/plugsnpixels/32/193237_2.png) [@plugsnpixels](https://community.topazlabs.com/u/plugsnpixels)\
**Post date:** [October 3, 2024, 9:53pm UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/22 "2024-10-03T21:53:37Z")

</div>

GP did not affect these\*; for some I did quick auto-color in PS before treatment but I didn’t work it too hard.

Another pic of the old-timey group looked like this in the original scan:

 ![Screenshot 2024-10-03 at 2.47.10 PM](https://community-cdn.topazlabs.com/original/3X/7/0/70d4554572ee966e4f955195eb404f8ce52479ae.jpeg)

In GP we need something reliable to quickly adjust color, same with PAI. Neither of the current included options really do much. I think a generic Levels dialog would go a long way.

I used to use a PS plug-in with 1-click color correction called PictoColor iCorrect EditLab Pro, but it went obsolete along the way (users would click on different neutral areas to adjust color, very effective). If Topaz added that type of thing it would be really helpful to whip an image into shape before exporting and avoid embarrassing discussions such as this 😉 .

![picto](https://community-cdn.topazlabs.com/original/3X/b/5/b5d6f70c2597aaca377acf9e1a6fd65db10f1e2b.jpeg)

\*I do see what you mean about Bill; this was the least amount of face recovery in the bunch and that level of blending may have had an effect.

---

<div class="post-metadata">

**Author:** ![zelenooki](https://community.topazlabs.com/user_avatar/community.topazlabs.com/zelenooki/32/208727_2.png) [@zelenooki](https://community.topazlabs.com/u/zelenooki)\
**Post date:** [October 8, 2024, 7:58am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/23 "2024-10-08T07:58:59Z")

</div>

For color correction, especially for scanned photos, I use an older 32-bit (x86) version of Photoshop with the KODAK PROFESSIONAL ROC PLUG-IN. I’ve modified the default Kodak batch action to work with the ACES AP0 color space and 16-bit color depth, which significantly improved accuracy, particularly with older scans. I get the ACES AP0 profile from Raw Therapee and copy it to C:\Windows\System32\spool\drivers\color on my Windows system to make it available in Photoshop. The action is excellent for batch processing, not just for scanned photos, but also for regular photos.

Unfortunately, Kodak has discontinued this plugin (luckily, I got it in time). If you’re interested and use Kodak Roc Digital Pro, I’m happy to share the modified action and color profile.

Regarding Gigapixel AI batch processing, I’ve noticed an issue with the “Face Recovery” (Gen 2) option. When enabled during batch upscaling, it seems to only apply face restoration to the first image in the selection, while the rest are only upscaled. Are any of you experiencing the same behavior? This makes it very cumbersome when processing a large number of photos, as it requires manual processing of each image individually.

---

<div class="post-metadata">

**Author:** ![zelenooki](https://community.topazlabs.com/user_avatar/community.topazlabs.com/zelenooki/32/208727_2.png) [@zelenooki](https://community.topazlabs.com/u/zelenooki)\
**Post date:** [October 9, 2024, 11:02am UTC](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991/24 "2024-10-09T11:02:07Z")

</div>

In the latest version of Gigapixel AI, I’ve encountered an issue with the “Face Recovery” feature when processing a batch of selected images. While the GUI indicates that the option is enabled for all images (icon displayed next to each filename), “Face Recovery” is only applied to the first image in the selection. This is also visible in the attached screenshot. Has anyone else experienced this problem? Does anyone know why this is happening?

[![](https://i.postimg.cc/pmKBzBMQ/Screenshot-00075.png)](https://postimg.cc/pmKBzBMQ)

[![](https://i.postimg.cc/SJBrnv3N/Screenshot-00076.png)](https://postimg.cc/SJBrnv3N)

[Next page](https://community.topazlabs.com/t/gigapixel-v7-4-4/78991.md?page=2)
