Topaz Video AI 5.2.0.2.rhea (New enhancement model: Rhea)

Hi everyone,

Today we’re releasing an updated alpha of our next Enhancement model, Rhea.

  • Updated training checkpoint for Rhea
  • Rhea now runs for all output resolutions (Rhea will internally scale to 4x and then re-scale up/down to match output resolution)
  • Recover Original Details disabled for Rhea
  • Slight ghosting of next frame fixed
  • First/Last frame desync fixed

5.2.0.2.rhea


Rhea represents a combination of Proteus and Iris. The model is intended to be more accurate in preserving fine details than Iris, while also handling text in a less destructive way.

There are a few key limitations for this alpha that testers should know about:

  • The current version of the model is not fully optimized and speeds of this alpha are not representative of speeds users can expect when Rhea is released.

We’re very excited to have testers working with Rhea. Thanks as always for your feedback and testing.


9 Likes

Preliminary tests - getting some nice looking results and skin looks like it is retaining more detail (auto settings). Did the model get changed to do that or am I just imagining it?

Screenshots:

Check out Troi’s comm badge - it looks amazing!

4 Likes

@david.123, the model is updated to provide more details.

2 Likes

Fantastic work sir.

2 Likes

The model seems to be quite large, isn’t it?
Have a 320p video upscale x4 running and dGPU-Memory consumption hovers around 14-14.5 GiB.

If you are upscaling 4x, and the model internally scales to 4x, then you are going up 16x memory-wise.

I could be wrong, though.

Ufff … hair looks really really bad in my first test and I have huge ghosting artifacts (kinda like 90s LCDs).
Definitely worse than Iris or Proteus in this case.

2 Likes

Does this model improve background text?

Original 320p video running in VLC:
Screenshot 2024-06-25 235338

Rhea1:
Screenshot 2024-06-25 235417

1 Like

Will this always be restricted to progressive sources, or will it eventually be available for interlaced sources as well? I deal primarily with interlaced sources.

I just completed rendering 2.5 hours of footage using Proteus after many hours of running tests between Proteus and Iris. I finally settled on Proteus because, while Iris produced detail recovery that I can only describe as magical, the results from Proteus were more natural. The Iris results had what I would call an “AI shimmer.”

When you made this Rhea model available, I was hoping it might be a “best of both worlds” solution, but since Rhea is currently only available when Progressive is selected as the source type, it’s not ideal.

1 Like

image

Guess I’ll wait the optimized version of Rhea in an upcoming release :sweat_smile:
(This is a mix between Gaia-CG and Rhea)

1 Like
  • The window should not get smaller than the smallest size where all controls fit

  • When I apply a crop all enhancement settings are gone. This has been reported before.

  • The input and output frame do not match. This has been reported dozens of times before.

  • Instant render: wront aspect ratio in the preview and suddenly stops working

  • the application crashed when the instant preview was turned on
    logsForSupport.zip (1.2 MB)

  • re-open the app after the crash made it open in full size window

  • tr-open after preferences, save and exit opens in full size window

  • when i hold the left mouse button in single view the original view is not shown. has been reported before

  • render times even on an rtx 4090 totally unacceptable

1 Like

Bruh.

1 Like

I love to see more development towards fighting the compression artifacts! Definitely going to test, even though I’m on 5.0.4 with stable VEAI. :slight_smile:

A teeny tiny question - could we expect Gaia HQ/CG v6 to make an appearance among legacy models? :slight_smile:

3 Likes

Is there any valid reason why new test versions appear unoptimized? Normally just enable the needed compiler options to get an optimized version should not be too hard. :eyes:

1 Like

@nipun.nath

More Rhea testing (all auto settings):

Black nebulous artifacts detected during testing.

Also, on further testing it looks like source details are still being destroyed. Check the below image comparisons for the black artifacts and also see how the fine details on the saucer section are being severely smoothed out/destroyed:

I think there is more work to be done on preserving detail.

Thanks!

4 Likes

Highlighting these 2 comparisons that clearly demonstrate the loss of fidelity:

Source:

Rhea:

3 Likes

And black artifacting:

Source:

Rhea:

Yes, I am assuming they don’t want to go through the time consuming process of converting the models to Tensor RT compatible ones until the models are finalized.

2 Likes

Wow, just “wow”… And if you can solve this one that I’m showing you…


2 Likes