You are not wrong. 
While the model itself is still the same the quality of the output is much improved when GaiaHQ is used in combination with the “add noise” feature.
In 2.6.4 GaiaHQ tends to have issues with noisy/grainy material; it transforms the noise/grain into stretching lines or bumpy “details” on faces and such.
In the current version that issue is still there but can be overcome by using “add noise”.
For some reason, I’m not able to add my vote. The little heart appears under some posts, and on others it’s missing. Strange.
Unfortunately, on my Mac, the add noise function adds visible noise and it looks bad.
Ok, got it. Done!
The difference is subtle in a still image but is quite an improvement in the resulting video-output.
first image: with added noise (much improved)
second image: without added noise (not a good, same result as in 2.6.4)
GTX 3060. It’s basically lost its mind. I only use this machine or bitcoin, Topaz, and editing Insta360 footage, so it was a fairly clean Windows install. Due to seeing some blue screens lately (after this most recent update), I did the Reset PC and discarded all my files and started out from scratch. Now the only thing it has installed is Video AI… And it gives me “Unknown Error”. I think something is borked with this particular version on PC.
Which driver for the gpu did you install?
I have always left everything at defaults. After restarting from a fresh Windows 11, then having to install, uninstall and reinstall Video IA, it’s working again.
On ExtremeTech, there’s a critical comment about TVAI, which I totally agree with. It’s under the Chrome and Edge Browsers to Get Nvidia RTX AI Video Upscaling article.
´Reduce Jittery Motions´ with 2 or more passes is incredibly slow on Macbook Pro M2 max. If it takes too long to processes (10-15 min.) it even freezes the program completely.
I know the settings description points out that each additional pass “significantly increases processing time”, but even so it feels unnaturally sluggish and unstable compared to every other filter.
Can this be a bug, or is it simply many times more resource heavy compared to all other filters?
Latest version being 13.2?
Deleted the app (and its sub folders), installed it new and it still crashes my Intel iMac.
The Mac OS Ventura update changed something
3.1.2 to 3.1.4 do not work
