I think Topaz intentions are that the new module would supersede & eventually replace the older model(s). so no point enhancing something that is eventually going to be obsolete
Chronos and Apollo create dupes when you go x4 on i.e. 15fps
Dont see any new interpolation models in the pipeline. Imo THIS should be fixed before going on developing a fresh upscaling modelā¦
I felt that the effects of iris V2 were wonderful.
We look forward to performance optimization.
I recently tried this latest beta version, and specifically the āIrisā model in its new V2 version⦠it is definitely an improvement over the first version, but there are 2 problems (one of which is the main one):
-
The differences between this V2 version and the V1 present in the stable version of the program are not high (I did a test of a 720x480 MPEG2 video uspcalated by 4 times with the āRelative to autoā setting with the same values for both versions)
-
The performance on my PC (i7 10700, RXT 3070, 32 GB Ram DDR4 3000Mhz, Win 11) of this new version 2 is really impetuous compared to version 1: to convert the same piece of video lasting a few seconds, with V1 the Stable version took 1 Minute and 10 seconds, while with V2 of this Beta version, the conversion took a beauty of 11 minutes and 14 seconds⦠a difference really too pronounced!
Here are two conversion samples below:


BUG:
This release sometimes passes āfps=0ā as the FPS value to the export command when āOriginalā FPS is selected, resulting in an error when you try to export.
When you manually select the original frame rate for the source, it passes the correct original FPS value and export works.
It was mentioned in the release notes that Iris V2 speed is not optimized yet
itās always advisable reading the full release notes before going for the test itself.
That way you know what to and what not to expect.

Well this entire BETA is a BIG FAILā¦
Cant do more than 1 process at the same time. Once you hit an error the entire program becomes unusable. Have to restart.
Random crashes.
Downloading model over and over again (same video previewed with same settings just 2min before)
Please guys. Whats with all these bugs?
Just noticed a minor issue with the preview length selection. If you restart the program, the preview length is shown as just below what was previously selected. So if a 2 second preview was selected, this becomes a 1.966 second preview after a restart.
The new Iris is probably not using tensor cores yet, unlike the first version.
Uh bugs in a BETA? Who would have thoughtā¦
I have the gtx 1660, there are no tensor cores, but iris v2 is still slower, so I donāt think itās linked to the tensor cores ![]()
I feel like Nyx isnāt stable enough across frames. Even with the maximum strength denoising offered by Nyx, there is still flickering through out my test video (presumably coming from the Nyx denoiser operating differently on each frame due to different noise patterns from the camera for each frame). I would personally like to see this area improved in future releases.
Yes Iris v2 is slower for you because itās not speed optimized yet (same for me on a 1060). But JakSpoon has a 3070, so it will be even slower still (10 times) compared to Iris v1, because heās having to use a non tensor core version of the model.
Heās having to slum it with us GTX users.
that is strange, I did not experienced those, but again this is a BETA, so stability is not what we should expect. we should report those but also accept those if it happens and not get all frustrated about it, that is why we are here, on the testing program.
Didnāt think about it that way. now that you mention, it makes sense why I did not see such a huge performance hit, as I am still on a GTX (1080 Ti) series and not an RTX, so i never had the luxury of speed speed speed on daily use, like all the others to actually bite me when going with a none RTX process.
But these bugs are application issues⦠which should not occur in a new build. I get that bugs occur with new features etc. And new models can be buggy. But existing stuff should be stable by now
As you may know from programming, fixing one thing in code can break 3 things elsewhere in a program. They just have to find them all, and we are here to do that. Then they can work on fixing.
Iris has the same bug as with an earlier version, adding lines/jitter/stripes to the output
Topaz 3.4.3.0.b
MacBookAir M2
EDIT: it works on an M1 MacMini
Vast improvement with details for Iris v2. One of my usual tests - Interlaced Progressive input zoomed at 100%. Iris on auto has done well at removing interlace lines while this time retaining good details.
yes, it looks much better then the Iris v1 you tried out last timeā¦
so all your interlaced lines were removed? including those on fast motion scenes?


