We had a fix ready and discussed as a team and felt this one was important enough to fix now for certain users instead of waiting for the usual Tuesday release.
ahh okay I played a little with 3.5.3, I didnāt have any problem for my part, just a quick question, have you improved the iris mq model? I have the impression that it produces fewer artifacts than before this update.
This is just a minor bug fix for V3.53. V4 will be released next week.
If they donāt publish it now, every user will need to upgrade to V4 to get the bug fix.
Okay I didnāt really understand the changes in v4, the nyx model will allow you to upscale to x2, is that right?? but will the iris model be improved?
Iris is on the edge of glory. But I noticed that it struggles with things with mesh, like mics and clothes, even though my video did not show the mesh on the mic originally due to the lack of pixel information, and temporally Iris made the mic become a messy moving metal ball lol . I really considered making some post-processing to get rid of the artifacts, but that would be very time-consuming, so I kindly ask the developers to take a look at this specific problem, because the rest looks really great to me. Another thing that I noticed is that Proteus generally produces smoother backgrounds with nice texture, while Iris tends to show some compression and color banding on the background.
Hello, I upgraded from 3.5.0 to 3.5.4 this morning.
I work always on the same kind of postproduction improvement:
AVI footage 720x576
upscale 2x
stabilization
detinterlace
Proteus
My system: RTX 4070 + Intel 9 13. generation
In version 3.5.0 I reach in average 21-25 frames per second for that.
In version 3.5.4 it tooks down to 7 frames per second! It starts with around 30 frames and went down step by step to 7 frames per second.
All video output is failing with an āOut of Memoryā error. I have a Mac Studio w 128gb of ram. When it fails, I still have 60-80 gigabytes of ram unused.
Could you send us an email at help@topazlabs.com with the full log files from the app?
To gather logs, please select Help > Logging and make sure that there is a check mark next to File Logging. Next, recreate the issue and then return to the Help menu and select > Get Logs for Support and attach the ālogsForSupportā file to your reply.
I usually go with Apollo as the other models tend to introduce things like blurry patches and have trouble with things like grids, checker patterns, lines etc. I find Apollo is better at handling these types of patterns.
I am using āApollo fastā because i read that it works better than Chronosā¦and i also tested if itĀ“s better than Chronos and it isā¦
Apollo looks better overallā¦
Thank you for this fix - indeed, I had to replace the 0 with 1080 in height field every time I started the program (I use the Iris v1 1080p height upscale mostly). Now, I hope, resaving the preset will fix this.
Is there going to be possibility to fix non-squared (for example squished 16:9 into 4:3 format) videos, too? And Gaia HQ and CG v6, pretty please! I really miss this model.
Thereās a small bug with preview and input seek position - the input position gets changed to the precisely the same position, as preview was at the moment of switching to input video view.
I played a little with 3.5.3, I didnāt have any problem for my part, just a quick question, have you improved the iris mq model? I have the impression that it produces fewer artifacts than before this update.
