CLI no longer working in Photo AI 2.0.0

I was eager to test if the CLI would use the newly added autopilot model preferences which were added in 2.0 as a feature. But sadly I can no longer process any file using the CLI.
I did a complete uninstall (with deleting configs and data) and a reinstall, just to be sure. But no change. CLI still completely broken in 2.0 :frowning:

I get the following errors:

C:\Program Files\Topaz Labs LLC\Topaz Photo AI>tpai c:\Windows\Web\4K\Wallpaper\Windows\img0_1024x768.jpg
Checking if log directory should be pruned. Currently have 11 log files.
Number of logs exceeds max number to keep ( 10 ). Cleaning excess logs.
Logger initialized
Application settings:
Overwrite Files: 0
Recurse Directories: 0
Input File Count: 1
Output Folder: Source folder
Output Format: Preserve
Jpeg quality: 95
Png compression level: 2
Tiff compression: none
Tiff bit depth: 16
Autopilot settings:
Face Detection: auto
Face Strength: 20
Face Parts: hair,necks
Sharpen Blurs: medium,high
Auto Upscaling Type: auto
Auto Upscaling Factor: 2
Default Subject Type: Subject
ExifTool loaded!
**Warning: failed to load Config_git.pl, something strange about this perl...**
**[ WARN:0@2,756] global C:\.conan\918058\1\source_subfolder\modules\core\src\matrix_expressions.cpp (1334) cv::MatOp_AddEx::assign OpenCV/MatExpr: processing of multi-channel arrays might be changed in the future: https://github.com/opencv/opencv/issues/16739**
**Error | No matching model info found for "Enhance" - ""**
**Error | Missing model identifier in: "Enhance" - ""**
**Error | No matching model info found for "Enhance" - ""**
**Error | AIEngine setup failed for  ""  on device  -2**
**Error | AI Engine Load Exception: Could not load model**
**Error | [CLI] Engine returned error: "Error loading model"**

With other files I get an even less informative error message:

C:\Program Files\Topaz Labs LLC\Topaz Photo AI>tpai c:\ProgramData\Topaz Labs LLC\Topaz DeNoise AI\tgrc\Demo1.jpg
Checking if log directory should be pruned. Currently have 11 log files.
Number of logs exceeds max number to keep ( 10 ). Cleaning excess logs.
Logger initialized
Application settings:
Overwrite Files: 0
Recurse Directories: 0
Input File Count: 1
Output Folder: Source folder
Output Format: Preserve
Jpeg quality: 95
Png compression level: 2
Tiff compression: none
Tiff bit depth: 16
Autopilot settings:
Face Detection: auto
Face Strength: 20
Face Parts: hair,necks
Sharpen Blurs: medium,high
Auto Upscaling Type: auto
Auto Upscaling Factor: 2
Default Subject Type: Subject
ExifTool loaded!
Warning: failed to load Config_git.pl, something strange about this perl...
[ WARN:0@3,447] global C:\.conan\918058\1\source_subfolder\modules\core\src\matrix_expressions.cpp (1334) cv::MatOp_AddEx::assign OpenCV/MatExpr: processing of multi-channel arrays might be changed in the future: https://github.com/opencv/opencv/issues/16739
**Error | [CLI] Engine canceled processing**

Steps to reproduce issue:

  1. Just open the command prompt (as admin)
  2. go to the install directory C:\Program Files\Topaz Labs LLC\Topaz Photo AI
  3. run the CLI via
    tpai c:\Windows\Web\4K\Wallpaper\Windows\img0_1024x768.jpg
    or
    tpai c:\ProgramData\Topaz Labs LLC\Topaz DeNoise AI\tgrc\Demo1.jpg

P.S. Shouldn’t there be Integration Tests for the CLI (at least a simple test with an input file and an expected output file not of size 0), so a complete failure of the entire module shows up -before- releasing new versions? I’m asking because this is not the first time the CLI is completely broken in a new release.


Topaz Photo AI [v2.0] on [Windows 10]

Sorry about that, we added a fix for this so that CLI works again in the release this Thursday and will use the new Autopilot Preferences.

We are creating an automated test for CLI as well for checking that Autopilot Preferences are applied and that the export.

Hello @Lingyu , thanks for the info.
I suggest you take it one step further, building a vast variety of integration tests, where you can use the CLI as an operating base, see idea: Quality Control: Ensure functionality by means of integration tests

Hello, I’ve also encountered the exact same issue when using CLI. So, if I need to use it now, how can I avoid this problem? Are there any updated versions available? Or do I need to modify any parameters?

From what I understand there is no workaround (with different parameters, etc.) - You will either have to wait for the release of 2.0.1 tomorrow. Or go back to 1.5.4, where the CLI was still working.

1 Like

We fixed the CLI in v2.0.1. Please update and let me know if you see further issues with it.