can you give me a link to this please ? because i didn’t had this issue with the previous version of topaz Video (the one before 1.1.0).
it’s not what kyle seems to tell there. From i knew before, it was doing a check every month, not every hours, but the last time I asked for Video Ai, not the new version.
Nah, was far too long ago. I only remember it because numerous people at the time said it was unreasonable as they keep their render PCs offline so things like Windows updates and such like don’t interrupt/crash any workflows. The online check on the now retired AI Video software was monthly IIRC.
The interpolation bug is back apparently. MediaInfo shows the output as variable, with minimum and maximum framerate. After muxing it in a .mkv container it shows as constant but weird, just like in the past.
Frame rate : 59.940 (59940/1000) FPS
I didn’t test other intermediary versions since v1.0 of Topaz Video where apparently that was fixed. Quite frustrating that these bugs keep coming back.
EDIT: It looks like v1.0.0 does the same thing while v1.0.1 shows constant frame rate after remuxing.
NOTE: The only reasons why I am tempted to use the new Topaz Video for interpolation is because recently I discovered that the last stable version for interpolation (v5.3.6) creates some blurry artifacts in the video randomly.
I’m curious…what’s everyone’s typical workflow with Starlight Mini? Just as an example, I have a video that I’m upscaling via Starlight Mini but also want to convert it to 60FPS + use Hyperion to take it from SDR > HDR.
What is the proper order of operations here? What I’ve been doing is performing the upscaling via Starlight. After that, I setup Frame Interpolation + SDR > HDR conversion on the 2nd pass (the already upscaled Starlight video).
Is this the proper way to doing things or should I be performing frame rate conversion and SDR > HDR upscaling first and then upscaling via Starlight Mini?
For practical reasons, I would upscale with Starlight first and only then increase the frame rate. For one thing, you would have to run double or multiple times the number of frames through the resource-intensive Starlight model. Also, you would be feeding it altered material as a basis. In my experience, Starlight works best with unprocessed footage.
I kind of had the same mindset with my current workflow. What about SDR > HDR conversion? Should I do that at the same time I’m doing Frame Interpolation or should I run Frame Interpolation first and then run a separate pass of Hyperion for SDR > HDR?
I have to admit that I’ve never used Hyperion SDR-to-HDR before. In general, I’m a big fan of HDR and I even bought an OLED monitor and TV specifically for it. Both of which can reach 1,000 nits in a large window. But somehow I haven’t found a single example of Hyperion anywhere, neither on YouTube nor on Topaz’s website. Could you show me something? I don’t even know what a good result is supposed to look like.
Unfortunately, most of what I’m working on is proprietary so I can’t really share any results. However, most of my results have been positive (it essentially feels like an automated HDR color grading).
I was really looking forward to this update for the new grain removal features, but it’s completely broken for my system. Renders now crash randomly. Crash recovery is a joke now too. Doesn’t matter what model I use, output container, resolution, etc. Can’t share what I’m working on. But I reinstalled version 1.0 of Topaz Video and I get no errors. Renders finish with no errors. Even the legacy app has no issues compared to this update. I’m not sure how this is supposed to be an improvement in performance for AMD, but it’s really irritating since I just paid to renew my license before this update.
I stand corrected on the v1.0.1 being the one where the interpolation is done properly. I left home a couple of days ago with a lot of jobs in queue. When I checked the output it was a variable frame rate that in most of the cases remained variable or with the weird frame rate mentioned prior even after remuxing. Worth to mention that all the inputs had the same frame rate:
Frame rate : 23.976 (24000/1001) FPS
So it’s back to v5.3.6 even with the risk of occasional blurry artifacts. I don’t understand why this keeps being a problem and not addressed even after more than a year since v5.4 was released (November 2024) and it is still perpetuated in the Studio version. Disappointing, to say the least!!!
Not that I’ve seen, but so far Topaz haven’t officially acknowledged removal of the CLI functions. Even their support staff don’t know how to respond as they appear to be in the dark as well as us.
It wouldn’t surprise me at all if this was yet another pathetic attempt to make more money and at some point they will offer the CLI functions as a paid add-on or Pro licence only, or something similar.
I would like to take this opportunity to remind CLI users that although the CLI menu functions have been removed, last time I checked a few days ago existing scripts do still work. (I have a personal licence with founder status.)