Topaz Video 1.0.1 - Patch

[Moebius]

Have you done the obvious thing of uninstalling ALL video ai apps and folders and reinstalling? This usually fixes weird bugs for me.

[jojje]

@Chamberhouse

Despite assurances from Mr Wixom at Topaz that the EULA would be updated regarding use of the CLI, it hasn’t changed. The offending sentence which I have been told is incorrect, is the following:

“Access to or use of the Command Line Interface (“CLI”) is strictly prohibited under a Personal License”.

Apparently, this doesn’t apply to Topaz Video.

Wait, what???
When exactly did they sneak in this change?

I have not accepted and will not accept that change, as I use the CLI almost exclusively. I’d rather be stuck at 4.2.2 without Pro than Not being able to use the CLI. This is insane.

[Chamberhouse]

The change to the EULA crept in with Topaz Video v1. Topaz had the opportunity to correct the wording of the EULA regarding the CLI in v1.0.1, but they didn’t.

Given Topaz have also removed the CLI documentation from the website, I no longer trust anything that Topaz says. This CLI / EULA debacle shows either incompetence or deceit.

I wouldn’t be surprised in the slightest if Topaz did try to move the Video CLI to Pro only.

Let’s wait and see if Topaz updates / corrects the EULA in the next version to say the CLI can be used by personal users. They’ve had plenty of time.

It goes without saying that I’ll be carrying on using the CLI regardless, one way or another.

Andy

[ForSerious]

I remember seeing CLI for pro only being in one of the messages about the changes. I’m pretty sure it’s fully intentional.

[elsch0pi]

I don’t see a reason to do that. Before the switch to this new Studio thing, I had only the beta version installed. Wanted to try the SL sharp, my specs are too bad for local so wanted cloud, no it’s only for Pro license. I do have the Pro license, but never paid attention to the beta title. Installed the normal release, that starts up and recognizes I do have a Pro license, but there is no SL sharp in there.
Switched to the new Studio version, which as far as I understand is a completely different software package, and it does not recognize / acknowledge the license.

[craig.dsouza]

Is anyone else finding that the program hangs on exit? I need to end task to close it.

[Chamberhouse]

That’s very interesting to know, thanks. Do you still have that message, and maybe copy and paste the relevant part please? And was that sent to you as a Pro user? (I was one of those customers who never received any email regarding the Studio release.)

Do I remember correctly that you were upgraded to Pro because you were able to show you were already using multiple GPUs before that became a Pro only feature?

Perhaps Topaz will do the same for CLI users. At least I have plenty of evidence.

For reference, here’s a link to my question regarding the CLI for personal licence users, which does get a response from Dakota Wixom:

Topaz Video 1.0.0 (New Studio Release)

Please, even if not Mr Wixom, will someone from Topaz answer my query regarding use of the CLI for personal licence users. In simple terms, the Topaz Video 1.0 UI says “yes, go ahead”, while the EULA (which hardly anyone reads) says “no - strictly prohibited”. So which is it? Thanks. Andy

However, in his reply, he uses the word “current” (twice), which on 2nd reading doesn’t look very promising…

Thanks.

Andy

[ForSerious]

I spent some good time looking. I didn’t keep any of the emails, and it’s been over a month, so they’re not in the trash folder anymore. I tried all the release and announcement topics too, but didn’t find it. I just remember CLI changing to a pro only feature, being the first thing that stood out when I read about the new Topaz Studio—and no I did not read the EULA all the way, so it would have had to be mentioned in there pretty early on.
Maybe someone else pointed it out not long after the initial announcement. I remember thinking it was heartless since Topaz knows the majority of their users mostly only use the CLI.

[Mayday]

Sometimes i think topaz doesn’t even know what’s valid, even with the simultaneous use of a license on two computers they contradicted themselves. I would just use it if it works otherwise you go crazy

[Chamberhouse]

No problem, and many thanks for checking anyway.

Andy

[steelfatboy]

Found a bug, the “scale=w=X:h=Y,setsar=Z” parameters are not being passed in Topaz Video 1.0.0 or 1.0.1 for Starlight. For example, “scale=w=768:h=576,setsar=1”. Confirmed by showing the Export command. So, output is always 1280x960 or 1280x1024. This is on Windows 11 using a Nvidia rtx5090.

[Nachobro]

I second the app closing issue. It hangs on exit even when after clearing the sources. I have to force close.

[Nachobro]

Same.

[PC100]

I have had a lot of trouble getting Starlight to output at my selected resolution and couldn’t figure out why. I didn’t think to check the command line in task manager.

[Mayday]

I’n not sure what newest Release does (I’m on 7.0.2) but there selected output is soemtime bugy. If you see in the output windows when it renders your source resolution nit set one, then Starlight does always min. Upscale (which is 720p fpr 16:9 conent and 960p for 4:3)

When you see chossen resolution then is no guarantee it does, SLm can also do before selected upscale resolution. You can see what you get wehn you know how fast it normally renders or make a copy of the running grwoing rendering file and import this into Virtualdub.

So shown upscale resolution could be wrong.

In any cases when it does wrong, remove the source video into TVAI and reopen it solves the problem, when you directly after the import set upscale resolution and start again.

[steelfatboy]

In my case it will show the correct resolution in the render queue, but the actual frames are the resolutions I posted. When I check the output with the cli, the scale parameters are missing. For 7.1.4 of TVAI, the cli has those parameters and the correct resolution is produced. But, 7.1.4 will show the wrong resolution in the render queue.

[dianac]

I see the same thing on my 5070Ti. However, if you watch the system memory use, you should see a lot of activity there. I have 32GB of DDR5-6400 and my memory climbs to 95% or more during those “pauses” on the GPU.

[shawn.crossen]

I have the exact situation and the exact same problem. Uninstalling and reinstalling fixes nothing for this either.

[Moebius]

Like I mentioned earlier, something seems off about the processing tims and quality with both models. I think I will just wait until the next patch to see if things improve, or I may downgrade to 1.0. I didn’t do a ton of testing for 1.0 but it did seem like starlight sharp was much faster. If I recall, regular starlight had some weird quality issues for me in 1.0…but at least if starlight sharp works it’s not so bad.

[Harald.De.Luca]

Quick question, is there a speed difference between 7.1.5 and 1.0.1 for the models? And especially for Star Light Mini?
This way I can see if I stay on 7.1.5 with a good speed between 5.60 and 5.80 seconds per image with Star Light Mini. Or if the speed is better or unchanged, I upgrade to the Studio version.