Topaz Video Error

[Kusi Bertoldo]

Thiserror appears when a model file needed to process an image is missing or the AI engine is not able to run on the computer. Please go through the sections below sequentially to troubleshoot this error.

If your computer graphics card does not meet the system requirements, you can open Topaz Photo AI and click the Processor menu to try the CPU option. If the CPU can process an image, that indicates the graphics card is does not meet the minimum requirements for Topaz Photo AI.

For situations where neither the CPU or graphics card can process the image, it's very likely that your installation of Topaz Photo AI is missing model files. This can happen if antivirus, firewall, or a VPN blocked the installer from downloading the files.

If that does not fix it, please open Topaz Photo AI and go to the menu bar on the top. Click the Help > Open Log Folder menu option, which will open up a folder with text files. The folder will look like this.

Email he...@topazlabs.com and attach ALL the text files in the folder to the email. Make the email subject "Error Loading Model in Topaz Photo AI" so our support team can quickly review and help you resolve the error.

logsForSupport.tar.gz (199.1 KB)

I have restarted my computer and have not opened any other software.

In my impression, I downloaded the alpha version before, but there was no error for that version.

My computer always shows ERROR when using the official version, so that it did not successfully convert to any video when using the official version.

Please help me! Thanks.

Uninstall completely.

Make sure there is nothing in

C:\ProgramData\Topaz Labs LLC\Topaz Video AI\presets

You will need to go to view, show, hidden items and check that to see this folder in file explorer.

If there is anything in there, delete it.

Reinstall 3.3.4 and try again.

To lower consumption, open Topaz Video AI and select File > Preferences and lower your memory usage to 10% and enable low power mode. This will cause the app to run very slowly, however, if this stabilizes the app, you can raise the memory consumption until you find the sweet spot.

When I attempt to use Topaz Photo AI via Lrc, I can launch fine using File / Plug in Extras / Process Using Topaz Photo AI. When I attemp to save the image back to LRC as a DNG file, I get "Internal Error has occurred: assertion failure".

This will be the last thing I have to say on this thread. I heard back from Topaz, and they said the plugin is designed to place the image back in the original folder. In order for that to work, the file needs to be located directly on the computer, or in a connected drive. Images stored in the cloud will not work.

What version of Topaz Photo AI are you using? I just tried that process (I'm also on MacOS 13.2.1) initially using Photo AI v1.2, which worked correctly. Then I updated to the latest v1.2.2, which also worked correctly.

I think I'm narrowing the scope of the problem. If I launch the plug in (File / Plug-in Extras / Process with Topaz Photo AI) from the Hard drive (I'll try and include a screenshot), then I can also save back to Lrc. If I launch using a photo that is in a Collection, that is when I get the assertion error.

And still more information. I'm still green on my learning curve of Lrc. If a photo is part of a collection SET, then I get the error. But if the photo is in a Collection, with no sub-collections (for lack of a better word), No error and the DNG is saved.

I accidentally discovered that the DNG files were being saved to my hard drive even if I received an assertion error. It's just that the altered image was not being displayed within a collection. How can those altered images be displayed in a collection automatically? I'll include a screen shot. The original image name is PRD_0206.nef. In the screen shot, Lrc is in the background and Finder is in the foreground with copies of the saved files highlighted in blue.

It's quite odd. I've tested some more and can confirm that if operating from either a collection or a collection set, when using the Plug-in Extras route the returned DNG is NOT added to the collection (which is a little bit surprising). However, and helpfully, on return LrC automatically switches the source from the collection/collection set to the actual folder in the Folders Panel so the the returning DNG is automatically stacked with the original file.

So in all cases the DNG is created in Photo AI, and when it is added to LrC I am able to see the returned file stacked with the original, although the initial source is changed if I started from a collection or collection set.

I'm beginning to think there is an issue between Lightroom Web and Lightroom classic. You see, when I first started using the Adobe product, I was importing photos to LrcWeb. I think the interface is better than Lightroom Classic.

So, my troubleshooting steps have been : In Lrc, I found a photo that returned an assertion error when being saved back from Topaz. I then deleted it from a collection, then from the folder within Lrc. I also made sure the file could not be found on my hard drive using Finder. I also went into LrcWeb and removed the photo from there. I exported that file again from Apple Photo and reimported to Lrc, then added it to a collection. With the phote selected in that collection, I launched Topaz through Plug-in Extras. After saving in Topaz, the assertion error did not occur. I seem to be experiencing some inconsistencies on having the saved DNG stacked to the original in the collection, but that could be user fog

I've just discovered the error occurring where Photo AI errors out when ssaving the file back to LR. I think, and this is just a guess, it's because the files being sent to Photo AI are on a network drive. I will test later. Thanks!

Which plugins are you trying to use? Also, we are still working on the plugin side of things so mixed results at the moment are too be expected. If you can let us know which plugin is giving the error, we can at least highlight it for further testing.

People use the phrase "clean install" to mean several different things, some of which do not actually guarantee 100% "clean" results, such as copying or reinstalling apps from local backups that may themselves have become corrupted.

Yes, the Hard drive was clean (All Partitions Without the EFI Partition was deleted). The Fusion drive was rebuilt and OS X was installed from a external bootable drive. Than I installed all Apps and I doesn't use the backups from Time Machine. The Time machine drive was also cleaned before I make the first Backup after installing OS X.

For those who run into this error message (IPC Memory Fail), after updating to Mojave and trying to load my Topaz Labs Star Effects filter, I got the error. Finally figured out I had to go to the v1.7.3 APhoto prefs/Plugins and do the Authorize Global to get it working again. Hope this helps.

I've attempted to replicate this functionality with a T-L462-HSB-R, and have had zero luck with getting anything other than a custom HTML box/buttons staring me in the face using the code from these articles.

Through a customer and myself, we started using SigPlusExtLite and some custom HTML fields to get a working solution. (Code below) Through some trial and error along with some sample code from Topaz, I've got it working and have multiple signature fields all working as expected when viewing the form. Unfortunately, the signature doesn't actually save into Laserfiche when submitted. The field reverts back to the static text of "Click to sign" essentially, and there is no signature to be found (in either a PDF or Tiff).

So now I'm stuck with a solution that I can't get to work, but seems to be working elsewhere, and a solution that half works with the inability to save the signatures that are captured. Any input/direction would be greatly appreciated in getting this integration complete.

I use the JavaScript that you link to with your first link. Quite literally, I paste the code into the JavaScript section. However, one difference is that I don't use any custom HTML fields, but simply one of the signature fields built into forms. (We also do use the SigWeb driver that you link to, while also using the exact same sig pad that you are.)

I've got the sigpad working everywhere else (PDFs, the Topaz test page, etc) but not with the Forms signature. When you navigate to :47289/SigWeb/, is there any response? This may be the cause of my problem. I just get a connection refused response.

Hi..Mainly this issue occurs when the server is not sync with the database. Are you getting this error only on this two pages? hae you tried chnaging any attributes or citypes names from the scripts or configurations files? please check the server log you could identify which CIT is causing this issues. or update us with the recent server logs after you reproduce this error. Regards..

This isn't a bug but an ACTUAL valid error message, it's something related to your client and the applet's need to get to your user path: "C:\Users\psharma090112\Application Data\Sun\Java\Deployment\"

You might want to ask your client's help desk if they've had other java applets report problems working with their corporate standard security. In the interim, if you have RDP and remote server access to a server grade OS, you might get different results there.

I am facing similar situations where in I am getting "Undefined Error Code" when I try to search for "Business Applications" CI in "IT Universe Manager". Below is the error log. Please help with this.

3a8082e126