Thanks for the prompt fix for the “Users with expired licenses login at every startup” issue, this is now fixed for me.
I haven’t checked much else yet but I did notice that when starting a new export process, using Apollo, the “downloading model” message still appears when offline - but the application then finds it in the models folder if it’s already there.
And on my second offline test, on Proteus auto, there was additionally a ‘model failed’ error report but then, the model was found and applied correctly as it had previously been downloaded.
Nothing major there but a bit of tidying up might be needed. I just hope that in fixing the ‘expired licence’ login issue it hasn’t broken something else!
You can revert to 3.0.7 by downloading the appropriate installer from the releases forum. Downgrades work best if the previous version is removed first.
Each of those model files has a different tile size, and the tile size used is determined by the video input and output resolutions. In theory, the selected tile size will be the most efficient in terms of processing speed, but the quality is not affected.
Thanks! It looks like the program is having some trouble reading & writing to some of the files in the same folder as the license is stored. It’s probably having some trouble saving your new login as a result.
Can you please try deleting the %PROGRAMDATA%\Topaz Labs LLC\Topaz Video AI\models\auth.tpz file? It should be recreated the next time you log in, hopefully with the correct license state this time.
I am having a similar problem. Once I updated it wanted me to log in again, but everytime I do it following the browser link-- it says I am logged in and completed it, but when I go to Topaz Video AI it will not let me export without a watermark. When I double-check my license status in the program it displays me as logged in, but still shows the watermark. When I try again, it makes me login yet again and the browser login says I am logged in/confirmed, but I still have the same problem of the update not acknowledging my credentials and still displaying the watermark. (If I had known this problem would occur, I would not have updated… and potentially not even paid for continued updates since I am currently in the middle of a client deadline and now cannot output without a watermark.) I’m going to search below for a way to revert to the prior version.
Is this a command prompt action or is there a particular folder/subfolder I need to locate this in? (only had Topaz for a year up until now and this is my first issue requiring me to delete any authorization files)
it’s a folder structure.
go to your C drive>ProgramData>Topaz Labs LLC>Topaz Video AI>models> and then scroll down till you find the “auth.tpz” file. delete that and open/restart TVAI. It should log you in and get rid of the watermark. Good luck!
Topaz 3.0.9 Clean install will not license - stuck at open browser.
I think Greg Maddra saying to delete the auth.tpz file is a bit of a Band-Aid to address the problem of programming issues/changes in Registry introduced in 3.0.7
The below is also a bit of a Band-Aid until Topaz AI probably fixes the auths in registry.
Here’s what I figured out to do.
When you install 3.0.9 Topaz it installs with the “Run as Administrator” greyed out. You can’t alter it.
After installing 3.0.9. Topaz I then deleted it’s Icon that it automatically created and made a new shortcut to:
C:\Program Files\Topaz Labs LLC\Topaz Video AI\Topaz Video AI.exe
Then I went into advanced properties and checked “Run as Administrator”.
This will allow the program to write to the places it needs to.
This to me indicates that something is not setup properly by Topaz AI in the registry to give administrator rights to a specific process/path that needs it.
Probably a change in 3.0.7 or something overlooked that was in previous versions in the registry.
You could probably also logon as administrator on you P.C. if you have this problem, but you shouldn’t have to.
This just started happening with 3.0.7 - Programmers may need to look at registry programming changes and rights.
Yeah, not a huge fan of running as administrator. If, at some point, an installer set admin privileges on folder, just unstall the program, manually delete its folders, empty the registry entries (if applicable), and run install again, as non-admin.
