The CLI documentation is no longer to be found. This applies when attempting to access it via the Help menu in both Topaz Video 1.0 and TVAI (7.1.4).
Now, let’s see the sequence of events around the CLI:
v1.0 - the EULA - which very few users will read, but is nonetheless a legal agreement, is updated to say, in so many words, the CLI is strictly prohibited for personal license users.
I question this, and eventually get a reply from Dakota Wixom saying the EULA is incorrect and the personal use prohibition is not supposed to apply to Topaz Video, but their other products. He said the EULA will be updated in the next patch. We’re now on v1.0.3 and there is no change in the EULA.
I also discovered that the CLI documentation, linked to in the UI help menu, has been removed from the online help pages.
I now see that Topaz’ “solution” for this is not to reinstate the CLI documentation page, but to remove the UI help menu item linking to it, starting at v1.0.2.
Topaz: do you really think we wouldn’t notice what’s going on here?
Andy
Checking on this for you and trying to get an update.
Hello, Andy! I’ve seen many of your posts in the community about the “device=-2” error. I’ve been struggling with this issue recently, especially when using a multi-GPU system—I want to run TVAI on an idle GPU so it doesn’t interfere with what I’m currently doing. However, no matter how I adjust the preferences, I’ve noticed that the command line stubbornly uses the “device=-2” parameter. The “auto” parameter causes TVAI to always use the active GPU (the one connected to the computer screen). In one of your earlier posts, I saw a solution about manually modifying the preference settings file, but this doesn’t seem to apply to Windows, as I can’t find that preference file. It seems like it might be saved in the registry, but from the registry, everything appears normal. The only issue is that the ffmpeg command line stubbornly uses the “device=-2” parameter. I wonder if you’ve looked into this issue on Windows?
Hi, I’m not so familiar with Windows as I rarely us it these days. Having checked the registry, I only found what I assume you also found:
Computer\HKEY_CURRENT_USER\SOFTWARE\Topaz Labs LLC\Topaz Video AI
gpuDeviceID = 0
gpuDeviceIDDefault = 0
If I changed the setting in the UI to Auto, then the value of gpuDeviceID changed to fffffffe i.e. -2.
So assuming yours is set to 0, I can’t think why the ffmpeg command would be using -2, unfortunately. So probably best to raise this with Topaz support.
Regards, Andy