And I believe when it first came out there was an issue getting it to respect the output resolution. I remember needing to set the output resolution a few different times to get it to stick.
Silent model update must have happenend weeks ago. I have 29.1GB VRam usage for my currently running SD 4x upscale (to 4k), doing 3x to 1440p itâs a bit lower, between 23GB-28GB, mostly i have about 26-27GB by doing 3x
2 Likes
Exactly. And this clearly shows there is a common cause for all stakeholders involved to get some engineering funding for improving the modelâs speed. Enterprise donât like wasting money renting or buying hardware if they can avoid it. We donât. And Topaz doesnât, as their margin for the cloud-offering suffers, and the free word-of-mouth marketing for using the model for various use cases is reduced.
My point was just that I donât think thereâs some conspiracy here where they have some TRT optimized version of the model in-house behind lock and key, and just refusing to deploy it.
Well, actually. Gating such a compiled âProâ version would make some sense, when youâre seeking to artificially create market segments. Provided youâre Goo⊠Micro⊠A monopoly I mean, where a brand hit doesnât matter. 
Finally got me an RTX 5090. Just wonder, is 7.1 as stable as my good, old trusted 5.3.6 version? Like, is the VFR issue truly solved? (not masked; Preview working? Etc.
For sure CFR when you do no Frame Interpolation. At least one user reported VFR by doing frame interpolation and having a 23.976fps source, I did short test interpolation not 23.976 but 25fps and 30fps source, this gives me CFRâŠso VFR is not clear because of condition and not all combination are tested. For me the latest works stable and gives me CFR, I do anyway no frame interpolation.
2 Likes
Thanks. I donât generally do frame interpolation either.
Congratulations and welcome to the club 
Which brand did you buy?
I recommend strongly undervolting itâs easy and relatively quickly to do.
My 5090 runs at 850mV on SLm for almost two weeks now, and so far, not one single crash.
850mV is very low also means you lose about 7-8% performance compared to the factory card default, because gpu clock drops from 2500 to 2200Mhz. On the other hand the power savings is more than 30%, and thatâs huge! Power consumption on the 600W connector is constantly below 400W
If you limit/flaten the voltage curve at 875mV, then you reach about 2500Mhz (maybe 2600Mhz max) so the performance is simillar to the factory, but the power consumption also drops here, by about 15-20%.
3 Likes
Thanks. I got the GIGABYTE AORUS GeForce RTX 5090 MASTER 32G
Those undervolting values sound great. Thanks for the tip!
nice one, I have the Gigabyte 5090 Windforce, my choice was simply the cheaper price and the AORUS didnât fit into my case
I havenât experienced that.
I had the only bug that long videos in MP4 container have to be re-wrapped in FFMPEG after finishing in TVAI.
Thereâs something wrong with a MP4 structure that players could not read the whole length of video.
Fort example, MPC-HC could only see 26 minutes of a 1h42m file. Adobe Premiere took minutes to read the whole file.
The solution was to either ffmpeg -i <result.mp4> -c:v copy <result_good.mp4> every time, or switch the output container to MOV.
The 7.1 version doesnât produce the same output as the 7.0.2 (or earlier) even when using the exact same parameters on the same video. The result seems more ânoisyâ with the 7.1 (the image seems to âflickerâ more). And the resulting file size is more than the double than with the 7.0.2 version.
I am using âregularâ models like Proteus and Rhea.
This is with the 7.1:
videoai : Enhanced using rhea-1; mode: manual; revert compression at 20.3174; recover details at 15.143999999999998; sharpen at 15.936300000000001; reduce noise at 1.7844200000000001; dehalo at 12.6842; anti-alias/deblur at 0.48966699999999996; focus fix Off; add noise at 5; and recover original detail at 20. Enhanced using prob-4; mode: manual; revert compression at 20.3174; recover details at 15.143999999999998; sharpen at 15.936300000000001; reduce noise at 1.7844200000000001; dehalo at 12.6842; anti-alias/deblur at 0.48966699999999996; focus fix Off; add noise at 5; and recover original detail at 40. Changed resolution to 1920x1080
Duration : 1 min 5 s
Bit rate : 20.6 Mb/s
Width : 1 920 pixels
Height : 1 080 pixels
Frame rate mode : Constant
Frame rate : 59.940 FPS
Bits/(Pixel*Frame) : 0.166
Stream size : 162 MiB (99%)
And with the 7.0.2:
videoai : Enhanced using rhea-1; mode: manual; revert compression at 20.3174; recover details at 15.143999999999998; sharpen at 15.936300000000001; reduce noise at 1.7844200000000001; dehalo at 12.6842; anti-alias/deblur at 0.48966699999999996; focus fix Off; add noise at 5; and recover original detail at 20. Enhanced using prob-4; mode: relative to auto; revert compression at 20.3174; recover details at 15.143999999999998; sharpen at 15.936300000000001; reduce noise at 1.7844200000000001; dehalo at 12.6842; anti-alias/deblur at 0.48966699999999996; focus fix Off; add noise at 5; and recover original detail at 40. Changed resolution to 1920x1080
Duration : 1 min 5 s
Bit rate : 8 393 kb/s
Width : 1 920 pixels
Height : 1 080 pixels
Frame rate mode : Constant
Frame rate : 59.940 FPS
Bits/(Pixel*Frame) : 0.068
Stream size : 66.0 MiB (98%)
Did anyone noticed something similar?
VFR is still not fixed when it comes to converting 29.97 â 60, 25 â 50 is fine. I use 7.1 beta to enhance without frame interpolation and do the frame interpolation in 5.3.6.
2 Likes
so interpolation vfr or not pends also on choosen fps you go to? Thatâs strange. and in the beta notes they wrote the new scene detection generates vfr, would be interesting if 7.1 final also does
Are you converting 29.97 to 60fps?
I donât think thatâs even possible with CFR.
You cannot insert partial frames, hence the VFR.
Have you tried converting 29.97 â 59.94fps?
If you need/want 60fps, you first will need to speed-up the original to 30fps.
Well, 5.3.6 does it with a CFR output.
2 Likes
I was looking for the source of this image flickering, and it turns out it only occurs after version 7.1. Then you need to downgrade to version 7.0.2.
yes because its always possible with any input fps becaue they could add as many interpolated frames as the wish until it machts output fps an film length. from V5.3.6 when mplayer came out, the VFR thing started, and there must be still fault in the code somewhere
Version 7.0.2 is older than version 7.1
Currently I downgraded to the 7.0.2
PS: I made several upgrade/downgrade, keeping the same project, to make sure that it was not a glitch. The problem was really introduced in the latest 7.1 version.
4 Likes
Yes, you are right, please forgive the typo.
Why does TVAI always corrupt text? Even simple apps like AI Video Enhancer preserve text very well. They need to add additional settings for text.
1 Like
